July 6, 2020 at 14:13 #28684
On a Windows 10 machine using Visual Studio 2019 and VisualGDB 18.104.22.16840 I am able to successfully build our project from Visual Studio in both release and debug mode. Furthermore, using msbuild, I am able to successfully build the release build from the command line on the same machine. However when I go to integrate it with Jenkins (using the exact same machine that worked), I am experiencing the following error using the same command line arguments:
<pre class=”console-output”><proj-name>.vcxproj” on node 1 (rebuild target(s)).
<span class=”error-inline”>C:\Program Files (x86)\Sysprogs\VisualGDB\MSBuild\SysprogsPlatform.targets(96,2): error : No toolchain found. Please configure the toolchain via VisualGDB Project Properties. [c:\jenkins\workspace\tito-trunk\products\jackson\tito\blimage\visualgdb\bl_tito_iMXRT1064.vcxproj]
</span>Done Building Project “c:\<path>\<proj-name>.vcxproj” (rebuild target(s)) — FAILED.
I’ve attempted the following same command line arguments that worked fine on the command line:
The build is based on msbuild just like Visual Studio projects for Windows.
To build from the command line, the following steps must be executed:
1) Open a cmd.exe window (console)
2) Execute VsDevCmd.bat to establish environment variables which msbuild needs:
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\Tools\VsDevCmd.bat
3) Run msbuild:
For the bootloader image:
msbuild -nologo -verbosity:minimal -target:rebuild -property:Configuration=Release;Platform=VisualGDB <your-path>\<proj-name>.vcxproj
For the application image:
<p class=”console-output”>msbuild -nologo -verbosity:minimal -target:rebuild -property:Configuration=Release;Platform=VisualGDB <your-path>\<proj-name>.vcxproj</p>
I’ve got to be overlooking something very subtle and appreciate any thoughts in advance!
July 6, 2020 at 14:16 #28686
- This topic was modified 1 month, 1 week ago by brillo372.
Looks like the Jenkins machine is missing VisualGDB toolchain definitions. This is very similar to the issue discussed in this thread, so the workarounds described there should work.
If not, please let us know more details and we will help.July 8, 2020 at 15:03 #28714
Thanks for this! It turned out that I needed to make some ENV variables known to the Windows Jenkins Node. Specifically (and for the sake of others who might experience something similar):
VISUALGDB_DIRJuly 9, 2020 at 09:29 #28722
No problem and thanks for the update. Just a quick clarification from our side: normally the ID/Version variables would be set inside the project file and the _ROOT and _DIR variables would be computed inside the %LOCALAPPDATA%\VisualGDB\FindXXX.props files that are managed by VisualGDB. So deploying these files to the build machine should get the variables working automatically.
You can find more details on this in our TFS tutorials here: https://visualgdb.com/w/tutorials/tag/tfs/
You must be logged in to reply to this topic.