Skip to main content
ED_KSRIF_KSIT5-Regular Member
5-Regular Member
Nov 4, 2024 8:45 PM UTC
Solved

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

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

RobrechtSavacoAnswer
13-Aquamarine
Nov 5, 2024 10:08 AM UTC

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)

View in thread

3 replies

VladimirN24-Ruby IV
24-Ruby IV
Nov 5, 2024 8:29 AM UTC

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

Translate
    RobrechtSavaco13-AquamarineAnswer
    13-Aquamarine
    Nov 5, 2024 10:08 AM UTC

    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)

    Translate
      ED_KSRIF_KSIT5-Regular MemberAuthor
      5-Regular Member
      Nov 5, 2024 8:05 PM UTC

      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.

      Translate
        Terms & ConditionsAccessibility statement