![]() ![]() On the next page specify the command line used to build the project.Even if the project uses files from other directories, they will still participate in build (as VisualGDB will be reusing your build system) an the debugger will be able to open them (as the ELF file records all the built source files): Note that it will only affect the contents of Solution Explorer. On the “Import Source” page specify the location of the source files of the project.In this example we will select MKL25Z128VLH4: On the next page select the ARM toolchain and pick device that the project is targeting.Select “Import a project built with command-line tools -> Specify a build command line manually”:.Start Visual Studio and launch the VisualGDB Embedded Project Wizard:.Before you begin, install VisualGDB 5.0 or later and download/unpack Kinetis KSDK. ![]() In this example we will show how to import the USB Mouse example from the Kinetis KSDK 1.3 that is built with CMake. ![]() This approach has the advantage of fully reusing the build system used to build the project, however is requires manually synchronizing the list of include directories and preprocessor macros between the build and IntelliSense, as VisualGDB won’t be able to automatically detect those settings for the build systems that are out of its control. This tutorial shows how to import an embedded project build with a third-party command-line to VisualGDB. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |