RiscFree v25.1.1 no longer finds BSP and compiler headers files when editing
A fresh project imported into RiscFree v25.1.1 never resolves the header from the BSP or compiler while editing. For example: This means that autocomplete of functions does not work. It works in...
The suggested approach of linking the projects provides a workaround for linking the headers to the BSP project. However, it does not solve the problem of linking to the compiler headers.
Still not linked.
Additionally, it also triggers a build of the BSP before the APP. This is not necessary. The CMake scripts in the APP will build the BSP automatically when the APP is compiled. But now under this configuration we have:
BSP compiled in bsp/build.
BSP compiled in app/build/bsp.
APP compiled in app/build and linked against app/build/bsp.
Step 1 is not necessary. Note that in the version where 23 where this works we don't have to link the projects. In version 23 only steps 2 and 3 are performed as the projects are not linked.
CMake is told to dump all the compile commands it used in a JSON file in the build directory. These compile commands contain the location of the headers etc used to perform the build.
The CMake plugin in Eclipse parses out the JSON file and works out where all the headers are located.
The CMake plugin tells Eclipse about these include paths via CMAKE_EXPORT_COMPILE_COMMANDS parser pre-processor option in the project configuration.
The problem is that the CMake plugin is getting an exception while trying to parse the JSON file and as such is unable to find the include headers. I noted the cause of the exception is some bad OSGi configuration.
New Contributor
