|
#1
|
|||
|
|||
That was happening in our tests (attached) as well before the fix (when building all configurations, it correctly identified the x86 executable target filenames but not the x64). Please post the project files.
|
#2
|
|||
|
|||
Hello;
Which files do you need in detail? Only the .vcxproj files or the .sln? In addition, do you need the VBP build file too? TIA Martin |
#3
|
|||
|
|||
The .bld file, the .vxcproj file, the .sln (if that is what you're building), and the .rc files in the project.
|
#4
|
|||
|
|||
Find enclosed the requested files.
Currently we build only the Release|x64 configurations. |
#5
|
|||
|
|||
Your projects are referencing
$(DefaultPlatformToolset) which the Make VS action doesn't know about. Code:
<OutDir>..\..\bin\$(DefaultPlatformToolset)\$(Configuration)\</OutDir> What you can do is add a Set Macro step before the Make VS action to set DefaultPlatformToolset = v143 with 'Add to environment variables...' checked, and the Make VS action will do the replacement on the VS variable from the environment variable. If the executable is created in that path, the action will be able to detect the change for incrementing. |
#6
|
|||
|
|||
I will try to change the build script but will you support $(DefaultPlatformToolset) in a future release?
All our libraries are using this macro, because they are built with/for different compiler versions. TIA Martin |
#7
|
|||
|
|||
Supported in the latest download (VisBuildDotNET.dll 10.9.0.3).
|
|
|