Forum Replies Created
-
Posts
-
Hi, thanks for your response.
“test project will have to be separate from the main project”, Having the test project separate from the main project doesn’t seem like a reliable or maintainable solution.
I believe it would be much easier if we migrate our project from Make to CMake? This would simplify the integration of TinyEmbeddedTest and allow us to keep both the source and test code within the same project structure. What’s your take on this?
Thank You!Update:
After going though the git history. I found out that someone from my team has added a “PreDebugAction” in the vgdbcmake. I disabled it for now by removing that section from vgdbcmake. Can you please guide me, how can I disable it from GUI and why It was causing issues with flashing code in debug mode?
</CustomBuild>
<CustomDebug>
<PreDebugActions>
<CustomActionBase xsi:type="CommandLineAction">
<SkipWhenRunningCommandList>false</SkipWhenRunningCommandList>
<RemoteHost>
<HostName>BuildMachine</HostName>
<Transport>BuiltinShortcut</Transport>
</RemoteHost>
<Command>PATH-TO-EXE</Command>
<Arguments>Arguments-to-EXE</Arguments>
<WorkingDirectory>EXE-WorkingDir</WorkingDirectory>
<BackgroundMode>false</BackgroundMode>
</CustomActionBase>
</PreDebugActions>
<PostDebugActions />
<DebugStopActions />
<BreakMode>Default</BreakMode>
<CustomBreakCommand>
<SkipWhenRunningCommandList>false</SkipWhenRunningCommandList>
<RemoteHost>
<HostName>BuildMachine</HostName>
<Transport>BuiltinShortcut</Transport>
</RemoteHost>
<BackgroundMode xsi:nil="true" />
</CustomBreakCommand>
</CustomDebug>
