- This topic has 13 replies, 3 voices, and was last updated 2 years, 10 months ago by
.
-
Posts
-
I get an error ‘MSB8020: The build tools for Visual Studio 2010 (Platform Toolset = ‘v100’) cannot be found. To build using the v100 build tools, please install Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting “Retarget solution”’ if I try to MSBuild <my project name>.vcxproj on a machine without VisualGDB. The goal is to build the project with MSBuild in a docker container. The project is a VisualGDB project, but technically I should be able to build the project without VisualGDB. Shouldn’t I? The error is strange to me because the project was not setup to use VS built tools 2010. Neither in an Visual Studio with VisualGDB extension nor in Visual Studio without the extension I have an option to set platform toolset to a newer version.
Hi,
Building MSBuild-based VisualGDB projects does require VisualGDB, since it provides the actual build rules for them (see this page). However, you can easily dump the build steps for your project into a batch file (see this page), check it into the source control, and run it on the build server. You will need to patch the batch file and the .rsp files it to replace the absolute paths with proper variables, but it should be a good starting point anyway.
If generating the .bat files is not an option, you would nee to make sure that the build server has the same Visual Studio configuration as the development machine (including MSBuild toolsets, etc.). You may also be able to get it working with a smaller MSBuild installation, although you would need to manually track down the error messages (they usually show the .props/.targets file where the error happens) and adjust the project accordingly (e.g. define some variables that the stand-alone installation expects). Generally, this is something to do at your own risk – using the batch files or getting a full VS installation should work much more reliably.
Hi,
i have the same issues but i’m not able to set the local build.
I got this configurations window at the latest visual studio 2019 and visualgdb.
Where is now the option hidden? Has dies changes with the lastet cmake Changes? I would also build the project from a build server (in my case gitlab) with a local runner.
Best regards
Holger
Using build with visualgdb /build
will result in a
“Your Makefile will nbot be auto-updated. Please go to VisualGDOProject Properties and click ‘repair command lines”
Currently is it really not possible to checkout by server and build is automatically?! also to generate the make files by cmake by itself? That would be a big pain.
Best regards
Holger
Hi,
It looks like your support period has expired a while ago. Please kindly renew it here and update to the latest VisualGDB build (VisualGDB-5.6.1.4153.msi). If the option still doesn’t show, please send us a screenshot of the settings window where you would expect the option to be, and we will help you troubleshoot it.
Hi,
we updated the support subscription. 😉
I have the problem, that i still not see the window, to activate the .bat generation.
Something missing?
Thanks for renewing your license.
The page on the screenshot you attached is a completely different window from the Visual Studio project properties, and it indeed does not contain the project properties. Please see our MSBuild Documentation page for an explanation how to open the Visual Studio project properties and this section for a specific location of the “Generate a .bat file” setting.
Hi Support,
i really followed this.
I will attach the screenshots. My Properties Windows looks different to yours in the ESP32 Project with cmake.
Best regards
Holger
Hi,
Based on the screenshots you attached, this is an advanced ESP-IDF project. It is completely different from the MSBuild projects mentioned by the original poster in this thread, and indeed has different settings.
Please refer to the following page for detailed instructions on building it outside Visual Studio: https://visualgdb.com/documentation/espidf/#buildproblems
Hi,
thanks the missing dialog is cleared.
But not fully solved 😉 If i right click, the context menu will show up “Dump command line to Batch File”
What should then happen? A Save Dialog for the Batch File? Or to which folder is the Batchfile written? I get no feedback when i click on the Menuitem.
Sorry for still not solved.
Best regards
Holger
Yes, clicking on “Dump command line to Batch File” should open a dialog asking for the location of the .bat file. If this doesn’t happen, please try attaching a screenshot of the build window showing the context menu with the “Dump command line to Batch File” option.
ah…. stupid! i got it. I need to be on the blue command line. And exact this line can export to bat file.
- You must be logged in to reply to this topic.