[bbr]

Hi,

the specific setting which breaks the template functionality is the project type. It is only not working for embedded projects.

[bbr]

Hi,

thanks for the explanation. I managed to come up with a solution using multiple statements which looks feasible for us.

To make our life even more convenient I tried to create a target template. Here is what I have tried:

1. Create a new embedded project using CMake
2. Copy the TargetDefinitions directory from this tutorial into the project directory
3. In the VisualGDB project properties set the custom target definitions directory to the copied directory
4. Add a new item to the project
5. In the “Add New Project Item” dialogue the “Sample Custom Target Template” is not listed

When using a different project type (e.g. MinGW) the “Sample Custom Target Template” is listed in the “Add New Project Item” dialogue.

Any idea what is going on?

[bbr]

Hi,

thank you, the new build solved the issue.

[bbr]

Hi,

 

attached is the call stack of the main thread and the mentioned lock owning Thread 9948.

Attachments:

You must be logged in to view attached files.

[bbr]

Thanks, the new build works as expected.

As the command line build is mainly used for continuous integration I doubt that the batch file is a suitable solution. Wouldn’t it require to manually regenerate the batch file when certain project changes are made? Also is there an option to force a rebuild with the batch file?

• This reply was modified 2 years, 9 months ago by bbr.

[bbr]

Hi,

in my first post I have attached a sample project based on a basic example containing code which should have a build error when compiled with -O3 and -Wall with GCC.

To reproduce the problem following steps should be used:

1. Download and extract the ZIP file
2. Open the solution inside Visual Studio
3. Select Release as Configuration
4. Rebuild the solution
5. Note that the build fails due to build errors. This is correct and expected behaviour.
6. Switch to a command line and navigate inside the extracted directory.
7. Build the project from command line with "C:\Program Files (x86)\Sysprogs\VisualGDB\VisualGDB.exe" /rebuild .\VisualGDBRebuildBug\VisualGDBRebuildBug.vgdbcmake /platform:VisualGDB /config:Release
8. Note that the build succeeds which is neither expected nor correct.

 

[bbr]

Hi,

of course this explains my second observation that when a build with /rebuild once succeeded on the command line it will succeed again with only /build.

But this does not explain why the command line build with /rebuild does not have a build error at all.

[bbr]

Hi,

 

thank you, the new build solved the issue.

[bbr]

Hi,

thanks, the build solves the problem with publishing the unit tests results and they are now showing up inside TFS.

I was following the Creating Simulation Platforms to Test Embedded Code without Hardware tutorial which recommends to run /listtests using .<span class=”crayon-i”>vgdbcmake. I have attached a sample project with the issue including the used command line and output. The only difference between “listtests fail.txt” and “listtests success.txt” is that add_bsp_based_executable(…) in CMakeLists.txt was commented out.</span>

Thanks!

Attachments:

You must be logged in to view attached files.

[bbr]

Thanks, this build solves the issue.

[bbr]

Hi,

I am using Visual Studio Professional 2019 version 16.8.2.

I did the steps you recommend but unfortunately the View->Output->Tests keeps empty after clearing it.

 

Regards,

Bernhard

[bbr]

Hi,

Thank you for your explanations. I will try them out and test if they could work for us.

Regarding the test explorer: The progress indicator is shown when the build starts and disappears before the build is finished. The Output->Test view does only show the test discovery after opening the solution. During or after the build Output->Test is not updated. Please let me know if I can provide any further information on this.

 

Thanks,

Bernhard

[Author]

Posts