Using SoftBench with SQL
Using SQL with SoftBench Tools
Editing and Rebuilding with SQL for SoftBench DebuggerThe make program does not follow dependencies beyond the source code (that is, the .c) level. So when using external build, you may need to remove the generated source code file after an edit to correctly rebuild.
Project build | 1. Select Edit in the SoftBench |
| Debugger Edit Area or choose |
| "File: Edit" to start your |
| configured editor. |
| 2. Make the source code change in |
| the embedded SQL file. |
| 3. Save the changes. |
| 4. Choose "File: Build". |
Old SoftBench Makefile | Follow the steps for project build. If |
| you have changed your Makefile or |
| your original source code (for |
| example, the .ec or .pc file), you may |
| need to delete the generated source |
| code file (for example, the .c file). If |
| the generated source code file exists, |
| SoftBench does not recompile the |
| original source code file. |
Other Makefiles and build scripts | This situation may require the same |
| actions as an old SoftBench Makefile. |
| What you need to do depends on how |
| your build process handles |
| dependencies. |
In all cases, SoftBench takes care of unloading and reloading the executable when SoftBench Debugger is running.
Using SoftBench CodeAdvisor and SoftBench Static Analyzer with SQLBoth SoftBench CodeAdvisor and SoftBench Static Analyzer rely on analysis data generated during the build process. SoftBench uses the preprocessor wrapper to provide line number information based on the embedded SQL files rather than the generated source files.
Chapter 13 | 321 |