- This topic has 7 replies, 2 voices, and was last updated 4 years, 1 month ago by
.
-
Posts
-
A coworker noted my repo checkins after compiling are missing the post build steps. Since it is working on their machine and our project folders are identical, I am not sure what to check next.
Investigating, everything appears to be setup correctly. I am using MSBuild and the following is in my configuration .vgdbsettings file.
<PostBuildActions>
<CustomActionBase xsi:type="FileTransferAction">
<SkipWhenRunningCommandList>false</SkipWhenRunningCommandList>
<SourceHost>
<HostName>BuildMachine</HostName>
<Transport>BuiltinShortcut</Transport>
</SourceHost>
<SourceFilePath>$(TargetPath).bin</SourceFilePath>
<DestinationFilePath>$(SolutionDir)\release.bin</DestinationFilePath>
<OverwriteTrigger>Always</OverwriteTrigger>
</CustomActionBase>
</PostBuildActions>Comparing the build output window to my coworker, mine is missing the copy file step.
What makes me think it is a VisualGDB issue is the VisualGDB Project Properties page. My list is half as long as my coworkers and is missing any mention of Custom Build Steps. I found a related post here, but it was a dead end.
I am running the same version of VisualStudio 2019 (16.7.4) and VisualGDB (5.4R12 build 3309) as my coworker. Uninstalled, rebooted, changing the order that I open VisualStudio then the solution. No change. The post build step does not execute and VisualGDB Project Properties is missing a large number of options.
I am able to duplicate this on new projects, I created a new embedded project for LEDBlink and opened VisualGDB Project Properties.
Why is my properties page neutered?
Hi,
The custom build/debug steps are supported starting from the Custom edition of VisualGDB (see our feature matrix). Most likely, you are using a lower edition that does not support them.
You can find out more about VisualGDB Custom Edition features here or upgrade your edition using the following page: https://sysprogs.com/splm/mykey
Confirmed. The license is different. I have the Embedded Edition and others have Custom Edition.
The Embedded Edition is both missing VisualGDB menu entries to configure post build scripts AND ignores the post build tags in the configuration .vgdbsettings file. No error messages during compile. The build output window shows no warning or message that anything is wrong. Yet, my build is incomplete without the post build steps.
To prevent future confusion, I suggest updating the support pages and tutorials for “more premium” features to include a link to the feature matrix page. For example, there is no mention of licenses or different editions on the official tutorial. The only prerequisite is “ensure that VisualGDB 4.0 or later is installed”.
Thanks for the input. Normally, VisualGDB would show the “this feature requires Custom edition” overlay on most Custom-only property pages during the trial. However, once the trial runs out, the extra pages will indeed be just hidden.
We will mention the Custom edition next time we update the custom step tutorial.
I still have an issue. I purchased the license upgrade and Custom Build Steps are still not executing.
After re-entering my upgraded product key, I can now see the custom build steps option under VisualGDB Project Properties.
However, when I Build I do not see the build step in the output window, and I don’t see the file created in the project folder.
I closed and re-opened Visual Studio, rebooted my pc, installed latest VisualGDB (5.5R3 build 3898), and am doing clean builds. My PostBuildActions are still being ignored.
No problem, we can help you. Please double-check that you are building the correct configuration, since custom build steps are defined for debug/release configurations separately.
If it doesn’t help, please try enabling the verbose build mode and share the build log (from the regular VS Output window, not the VisualGDB Build window) and also the name of the .vgdbsettings file that contains the custom step.
Thanks for the direction.
Selecting Release from the Solution Configuration dropdown was compiling the Debug configuration. Checking on the Configuration Manager, I found the Release solution was linked to the Debug configuration.
Fixed that, and everything appears working. Hurrah!
———
Easy to spot in the repo diff. The config link is stored in the .sln file. Was most likely inadvertently changed while trying to search for fixes to the previous issues with the build steps and configurations.
Thanks again!
Good to know it works. BTW, feel free to try out the new Advanced CMake Embedded Project Subsystem. It was specifically designed to address the shortcomings of MSBuild (including the duplication of settings between targets, platforms and configurations) and provides much more streamlined experience.
- You must be logged in to reply to this topic.