Forum Replies Created
-
Posts
-
I think VisualGDB for macOS would be a great addition to an already amazing product. Thank you for all you do.
After a little bit of effort and thinking through it I have found a solution.
I combined both idea from the previous links in my post above. I first followed all of the steps in creating the bootloader project as defined here. There were a few changes I had to make to the project to make everything work correctly.
First, I built the bootloader project separately, and added the output binary file to the main app project as a resource file. The Properties (not VisualGDB properties) for that file were setup as an “Embedded Binary File” and set to go into the section name “.bootldr” for the configuration that was building the entire app + bootloader. All other configs, I just exclude from build.
I then changed the Output Directory, found in Project Properties (not VisualGDB properties), to “$(SolutionDir)$(Platform)\$(ProjectName)\$(Configuration)\“. This was because the main application project was deleting my .bin file that was generated by the bootloader project.
After those two changes, I was able to build and link the projects properly. I also now have them store in locations that are independent and not overwritten by each other.
Hope that helps.
Do you have another example on how to do the bootloader without the Makefile? That is the main reason for specifying the TARGETTYPE. We were using the Makefile for linking the boot loader to the application.
With the previous GCC build there was an area for additional Make arguments.
<MakeFilePathRelativeToSourceDir>Makefile</MakeFilePathRelativeToSourceDir> <MakeConfigurationName>Debug_AppOnly</MakeConfigurationName> <AdditionalMakeArguments>$(LocalMultiThreadedBuildFlags) TARGETTYPE=APP</AdditionalMakeArguments>
