Forum Replies Created
-
Posts
-
I spent some time figuring this out. I found that what worked for me was adding the following anywhere in the *.vcxproj file under the main Project XML section:
<Target Name="BeforeBuild" BeforeTargets="PrepareForBuild">
<Exec Command="<<Exe call with command line>>" />
</Target>What’s important with the Exec command is that all XML unsafe characters are escaped (< becomes “>”, ” becomes “"”, & becomes “&”, etc.)
I found out what my issue is. I had selected “Cross-Platform MSBuild” in the build step “MSBuild Version” setting rather than “MSBuild 2019”. Switching that fixed my issue.
Is there also a tutorial on how to configure VisualGDB projects to build through TeamCity? I have a setup where I can envoke the build of a VisualGDB project with msbuild.exe, however when I try to set up the same command with TeamCity, I find:
- TeamCity needs to be set up with env.VCTargetsPath (set to C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Microsoft\VC\v160\)
- Need to set env.TOOLCHAIN_ROOT to “C:\sysgcc”
However, my next challenge is to figure out what to do about this same FastUpToDateCheck.targets error MSB4062:
[dotnet msbuild] C:\Program Files (x86)\Sysprogs\VisualGDB\MSBuild\Targets\FastUpToDateCheck.targets(5,2): error MSB4062: The “InitializeFastUpToDateCheckFile” task could not be loaded from the assembly C:\Program Files (x86)\Sysprogs\VisualGDB\\Sysprogs.Build.Tasks.dll. Could not load file or assembly ‘Microsoft.Build.Utilities.v4.0, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.
I even set up TeamCity service to use the same user account which I’m using to successfully build my VisualGDB projects with TeamCity, but I can’t seem to get it to compile.
