cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Need help navigating or using the PTC Community? Contact the community team. X

Please advise on VS2017 build failure

CHASEONHO
18-Opal

Please advise on VS2017 build failure

hi,

We need to upgrade the project implemented with CP3.0&VS2012 to CP6.0&VS2017.

 

For migration, the VS2017 project was configured and built in the same way as the existing VS2012 project properties.
At first, an error stating that protk_dll.lib could not be found occurred, so the input value of the linker was changed to protk_dll_NU.lib.
Numerous LNK2019s occur after the change.

 

I am attaching the project file, thank you for your help.

 

P.S.
Create a project by moving the protoolkit folder that comes with the CP6.0 installation to D:\Users\header\C6.0.
For the difference, the project built in VS2012 is also attached.
The difference between the two projects is the referenced linker and C/C++ paths (C6.0 and C3.0), and the input protk_dll and protk_dll_NU of the linker properties.

1 ACCEPTED SOLUTION

Accepted Solutions

Add "protoolkit_NU.lib, ucore.lib, udata.lib, protk_dll_NU.lib" to the linker input.

View solution in original post

1 REPLY 1

Add "protoolkit_NU.lib, ucore.lib, udata.lib, protk_dll_NU.lib" to the linker input.

Top Tags