Skip to main content
E
ED_KSRIF_KSIT5-Regular Member
5-Regular Member
November 4, 2024
Solved

protoolkit_NU.lib(srcstdstream.obj) : error LNK2019: unresolved external symbol __std_find_trivial_1

  • November 4, 2024
  • 2 replies
  • 1166 views

Hello,

 

I'm trying to build a Project, wherein i get the below compilation error: Not sure where exactly is going wrong.

 

>protoolkit_NU.lib(srcstdstream.obj) : error LNK2019: unresolved external symbol __std_find_trivial_1 referenced in function "unsigned __int64 __cdecl std::_Find_elem<char,27>(char const (&)[27],char)" (??$_Find_elem@D$0BL@@std@@YA_KAEAY0BL@$$CBDD@Z)

 

Settings Done on Visual Studio 2019:

1. Added protoolkit_NU.lib in Linker->Input->AdditionalDependencies

2. Added "$(CREO_INSTALL)/otk/otk_cpp/x86e_win64/obj;$(CREO_INSTALL)/protoolkit/x86e_win64/obj;" under Linker->General->AdditionalLibraryDirectories

Best answer by RobrechtSavaco

Can you DM or attach your *.vcxproj file?

I have already developed a couple of Toolkit projects and if you want, I can check your Visual Studio Project file with one of mine to see if all necessary properties are present in the *.vcxproj file (because in the beginning I was also struggling with compilation/library errors)

2 replies

V
24-Ruby III
VladimirN24-Ruby III
24-Ruby III
November 5, 2024

Some solution can be found here: https://community.ptc.com/t5/Customization/link-error/td-p/207384 

    R
    RobrechtSavaco13-AquamarineAnswer
    13-Aquamarine
    November 5, 2024

    Can you DM or attach your *.vcxproj file?

    I have already developed a couple of Toolkit projects and if you want, I can check your Visual Studio Project file with one of mine to see if all necessary properties are present in the *.vcxproj file (because in the beginning I was also struggling with compilation/library errors)

      E
      ED_KSRIF_KSIT5-Regular MemberAuthor
      5-Regular Member
      November 5, 2024

      I solved the issue. It was related with new version of VS2022 to be used for building the solution, as it was dependent on V143 toolset.

       

      Thanks much for the reply.

        Terms & ConditionsAccessibility statement