Using SDK in current Visual Studio?

[robcat2075]

If I download the SDK and load the .sln (Solution) file for one of the sample plugins into Visual Studio, the various code files do appear to load and can be examined. The files look like c++ that I could work my way through.

However, it seems I am not able to compile them. Upon loading a .sln several warnings talk about missing toolsets and/or the need to "retarget".

What more do I need to do to be able to hit "build" and get a successful compile from one of these existing sample plugins?

@yoda64 @nemyax

[robcat2075]

Here is the first decision point... when I load one of the sample .sln files

This dialog has multiple options...

 

I haven't found any combination of these options that gets me a working result. Should there be one?

 

Visual studio also offers this error...

Quote

warning  : The build tools for Visual Studio 2015 (v140) cannot be found. To build using the Visual Studio 2019 (v142) build tools, either click the Project menu or right-click the solution, and then select "Retarget Solution". Install Visual Studio 2015 (v140) to build using the Visual Studio 2015 (v140) build tools.

• Choosing to "Retarget Solution" did not get me a working result.
• I can't install Visual Studio 2015. I tried that. The installer doesn't seem to work on Windows 10.
• I downloaded the "Visual Build Tools for Visual Studio 2015 with Update 3" but VS 2019 doesn't seem to be able to use them... I get the same error message as above.

 

What do i need to change to successfully compile in modern Visual Studio?

Would upgrading to VS 2022 solve this?

 

 

 

[robcat2075]

I tried installing VS 2015 again.

It finishes with these errors...

 

If I "launch" Visual Studio 2015 and try to load the "Dust" .sln I get this error...

 

 

What do i need to change to properly open and compile the samples from the A:M SDK? 

 

[Wildsided]

Hi Robert,

I downloaded Visual Studio 2022 to see if I could figure out how to get around the errors and after some faffing I seem to have go it to build.

First it told me I needed Windows 8.1sdk which I downloaded and installed from here https://developer.microsoft.com/en-us/windows/downloads/sdk-archive/ (Because you can't download it directly from the Visual Studio installer.

Next it told me I didn't have the correct Visual Build tools like it did for you. To fix this I went into Tools -> Get tools and Features -> Individual components -> typed 140 in the search bar -> downloaded MSVS v140 - VS 2015 C++ build tools (v14.00)

Now when I select Build it doesn't fail and seems to complete the process. 

[robcat2075]

@WildsidedWas it the "Community" edition of 2022 that you downloaded?

 

And what options did you select? You didn't select "Desktop development with C++" or "C++ MFC for latest v143 build tools"

[Wildsided]

I did download community edition and desktop development and then downloaded the two mfcs below when it said I needed them as I didn't know which one I needed and wanted to cover all the bases. Sorry forgot to mention that.

[robcat2075]

Spectre mitigations

[Wildsided]

Well it's always best to mitigate specters 👻

[robcat2075]

Dan are you accepting these defaults when you load a .sln?

[robcat2075]

Here is an error I recall seeing previously in VS 2019

Build started...
1>------ Build started: Project: GridTurb, Configuration: Release x64 ------
1>LINK : fatal error LNK1181: cannot open input file 'plugin_64.lib'
1>Done building project "GridTurb.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

 

I know that lib exists, it's in the SDK, but for some reason it's not getting found?

[Wildsided]

Now I've come to load it up again I think I might have been mistaking "Not failing immediately" for "Working" as I am getting the same plugin_64.lib error as you are.

[robcat2075]

It's some sort of directory "paths" problem I presume but the .sln file or the project file should have that all defined already. 

[Wildsided]

 

just a question @robcat2075 is yours looking for plugin_64.lib or plugin_64d.lib? Mine is looking for the latter. I searched my drive and can't even find either one in order to point Visual studio to where it's supposed to be looking.

 

[Wildsided]

Holy moly I might have figured it out! K first go into the project properties -> general -> additional library directories and add the lib/pc folder from the AM sdk

then go into that folder, copy plugin_64.lib and rename it plugin_64d.lib and do the same for matrix_64 and IO_64 then try building.

[robcat2075]

55 minutes ago, Wildsided said:

 first go into the project properties -> general -> additional library directories

I don't find "additional libraries" under General.

 

Do you get an hxt file in the release folder?

I presumed that the "d" was the difference between "debug" and "release".

If I have VS set to "Debug" it fails to find the 'plugin_64d.lib' which is missing from the SDK

If I have VS set to "Release" it fails to find the 'plugin_64.lib' which does exist in the SDK

[Wildsided]

Sorry it's the Properties - Linker - General - additional library directories.

I got an .HXTd in the AM190SDK\V19\Lib\PC\HXT folder.

<edit>

When I changed configuration to 'Release' it was looking for the none 'd' version of the libraries. and completed successfully.

[robcat2075]

It's real close.

I didn't have to do any renaming if I do your library path thing and stick to "release".

I get a grid_64.hxt file in the 64/release folder. But if I put it in v19.0 I get this error...

 

 

If I put it in v19.5 I don't get the error but it doesn't show up in the   menu where it should show up.

 

 

[Wildsided]

Bugger

I think that's as far as I'll be of any help. I'm not much cop when it comes to code. 

[robcat2075]

ooohhh... look at this.

It didn't work in v19.5, it didn't work in v19.0, but it did work in v18.0...

 

 

[robcat2075]

@Wildsided Dan, thank you so much for your investigating, it has helped immensely!

I'm going to buy you a beer! And I'm even going to drink it for you!