Data

SDK supports Prepar3D’s philosophy of an open development architecture and encourages third parties to bring new innovations with improved add-ons and training content.
Post Reply
BostonFusionCorp
Posts: 1
Joined: Tue Oct 26, 2021 5:16 pm

Data

Post by BostonFusionCorp »

Hello, we are trying to build the PDK General Sample for the Data Harvester using Visual Studio 2017, and we are running into the following error on build:

Code: Select all

1>------ Build started: Project: DataHarvester (PDK General Samples\DataHarvester), Configuration: Release x64 ------
1>DataHarvester.cpp
1>StartStopHandler.cpp
1>DLLMain.cpp
1>   Creating library C:\Users\Alex Boch\Desktop\Prepar3D v5 SDK 5.1.12.26829\Output\Release\PDK General Samples\DataHarvester\DataHarvester.lib and object C:\Users\Alex Boch\Desktop\Prepar3D v5 SDK 5.1.12.26829\Output\Release\PDK General Samples\DataHarvester\DataHarvester.exp
1>SimConnect.lib(commClient.obj) : error LNK2001: unresolved external symbol __CxxFrameHandler4
1>SimConnect.lib(client.obj) : error LNK2001: unresolved external symbol __CxxFrameHandler4
1>SimConnect.lib(commClient.obj) : error LNK2001: unresolved external symbol __GSHandlerCheck_EH4
1>C:\Users\Alex Boch\Desktop\Prepar3D v5 SDK 5.1.12.26829\Output\Release\PDK General Samples\DataHarvester\DataHarvester.dll : fatal error LNK1120: 2 unresolved externals
1>Done building project "DataHarvester.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========


According to other solutions on the internet, this has to do with Visual Studio 2017 using the Visual Studio 2019 build tools. Has anyone experienced a similar issue, if so, how can we fix it and/or force Visual Studio 2017 to use the 2017 build tools?

Thank you!
shouvik1984
Posts: 17
Joined: Mon Apr 20, 2020 8:46 am

Re: Data

Post by shouvik1984 »

I am also facing this issue. Any solutions Please let me know
My project settings still use VS2017 v141 toolset
Best Regards
Shouvik Das

P3Dv5.3 Windows 10 x64 i7-10850H Quadro RTX3000 32GB DDR 2933MHz
fformulaa
Posts: 10
Joined: Fri Dec 04, 2015 8:02 pm

Re: Data

Post by fformulaa »

It's looking for toolset v142 which is in 2019, not in vs2017 which comes with toolset v141.

Just tested it and it compiled successfully on vs2019 ver.16.11.5 Community Edition.

You can try right clicking on the project, properties, the changing the Platform Toolset to v141 but you might run into Win10 SDK issues. Not sure if you can install Toolset v142 on a vs2017 instance.

In vs2019 I tried compiling it with toolset v141 and it was not happy at all. It was asking for a new Win10 SDK and that I should retarget the solution.
User avatar
Rob McCarthy
Lockheed Martin
Posts: 3703
Joined: Wed Aug 24, 2011 1:37 pm

Re: Data

Post by Rob McCarthy »

Hello,

Visual Studio 2017/v141 is not supported in the v5 SDK. You will need to use Visual Studio 2019/v142.

Regards,
Rob McCarthy
Rob McCarthy
Prepar3D® Core Lead
Post Reply