Thanks - worked pretty well with QorIQ SDK U-Boot. A couple minor comments:
- I also added BUILD_DIR on Step 5 (personal preference)
- For some reason I saw no addr2line and c++filt on Step 6 (not sure I care)
- For better indexing (eg, picking up correct config.h), added C/C++ Paths and Symbols, includes (all languages):
${BUILD_DIR}/include2
${BUILD_DIR}/include
${ProjDirPath}/include
/opt/fsl/.../include
(assuming BUILD_DIR is used)
1 thing that's not working well is indexing of assembly code, which is annoying since I'm digging through start.S at the moment. Any idea if/how to get indexing to work on assembler (.S) files?
Not sure how to index .S files.
In CodeWarrior (which is based on Eclipse), there is a check box in Properties-->C/C++ Build-->Discovery Options. This allows you to automate discovery of the C Compiler or Assembler.
But I'm not sure if this option is available in the Eclipse running in Linux. Will need to check.