Kinook Software Forum

Go Back   Kinook Software Forum > Visual Build Professional > [VBP] Third Party Tools
Register FAQ Community Calendar Today's Posts Search

Reply
 
Thread Tools Rate Thread Display Modes
  #1  
Old 05-08-2024, 07:06 AM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 6,031
The .bld file, the .vxcproj file, the .sln (if that is what you're building), and the .rc files in the project.
Reply With Quote
  #2  
Old 05-13-2024, 03:58 AM
mgampi mgampi is online now
Registered User
 
Join Date: 05-19-2011
Posts: 7
Find enclosed the requested files.
Currently we build only the Release|x64 configurations.
Attached Files
File Type: zip SampleProject.zip (83.8 KB, 87 views)
Reply With Quote
  #3  
Old 05-13-2024, 02:21 PM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 6,031
Your projects are referencing

$(DefaultPlatformToolset)

which the Make VS action doesn't know about.
Code:
<OutDir>..\..\bin\$(DefaultPlatformToolset)\$(Configuration)\</OutDir>
The value would vary depending on the version of Visual Studio that is performing the build. It looks like the default for VS 2022 is v143.

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.
Reply With Quote
  #4  
Old 05-14-2024, 07:11 AM
mgampi mgampi is online now
Registered User
 
Join Date: 05-19-2011
Posts: 7
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
Reply With Quote
  #5  
Old 05-14-2024, 08:06 AM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 6,031
Supported in the latest download (VisBuildDotNET.dll 10.9.0.3).
Reply With Quote
  #6  
Old Today, 07:59 AM
mgampi mgampi is online now
Registered User
 
Join Date: 05-19-2011
Posts: 7
Hi;

Sorry for the delayed reply.
I tried both - new DLL and the macro workaround - but both of them do not work! What I found out so far is: When compiling any of the 32-bit configuration ithe version number is increased, but as soon as we create a 64-bit configuration, the increment is not performed.
As I mentioned before, we exclusively build only 64-bit configurations.
Attached Images
   
Attached Files
File Type: zip Project1.zip (241.9 KB, 2 views)

Last edited by mgampi; Today at 08:16 AM.
Reply With Quote
  #7  
Old Today, 09:56 PM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 6,031
Try the latest download (VisBuildDotNET.dll 10.9.0.4).
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



All times are GMT -5. The time now is 10:38 PM.


Copyright © 1999-2023 Kinook Software, Inc.