Post Go back to editing

issues with additional include directories on Core0


We using CrossCore 2.9.4 on an ADSP SC587

we having issues with "additional include directories" when we include anything for CORE0 but on the other DSP cores it works fine.

Now when i look in the output console for core 0 and we look how crosscore compile this:

arm-none-eabi-gcc -g -gdwarf-2 -ffunction-sections -fdata-sections -DCORE0 -D_DEBUG -DADI_DEBUG -DADI_MCAPI -DDEBUG @includes-1c4accfa32bc0540630b9a10b97b4ed1.txt -Wall -Werror -c -mproc=ADSP-SC587 -msi-revision=1.0 -MMD -MP -MF"src/user/comm_core0.d" -o "src/user/comm_core0.o" "../src/user/comm_core0.c"

The include directories are in the Includes-1c4accfa32bc0540630b9a10b97b4ed1.txt.

When we open this file we cannot not find our addition included files:


So what we doing wrong here or is this a bug in the CrossCore?
How we can resolve this issue?

  • Hi,

    We’re trying to reproduce the issue that you are facing for the additional include directories option. So we have created a project as per your screenshot with the same project name and included the file in the project using the "Additional include directories" option. After building the project, we can view all included directories that are updated in the ***.txt file from the debug folder Please refer the attached screenshot (image1).

    Also, could you please confirm all the added folder directory in additional include directory which should be available in the correct folder name and correct path. For eg: ( D:/gitlabProjects/Firmware_SHARC_DSP_FS/FW_SHARC_DSP_Core0/src/config) etc.

    You can also include the file in project using "Additional include directories" option.
    To do the same go to project > Properties > C/C++ Build > Settings > CrossCore sharc C/C++ Compiler > Preprocessor > Additional Include Directories(I). In that add the location of the file which you want to include using add(+) button and click apply and close.You should now able to see the added file/folder in your project under includes folder.

    For example location: "${workspace_loc:/${ProjName}/src/config}" "${workspace_loc:/${ProjName}/src/modules}" "${workspace_loc:/${ProjName}/src/utilities}" etc.

    We understand that you want to include something like -I"${MY_FILE_PATH}". You can also do this by adding a Build Variable in Project Properties->C/C++ Build->Build Variables->Add, and set the variable value to the library directory, for example, set Variable name = "common", type = "path" and Value = "D:\gitlabProjects\Firmware_SHARC_DSP_FS\FW_SHARC_DSP_Core0\src". Then you can refer to this variable in the compiler pre-processor, like adding an entry "${common}/config" , "${common}/modules", ${common}/user, "${common}/utilities", "${common}/bsp/debug" in "Additional include directories (-I)".

    Also, CCES can recognize system path variables, so you can set a system variable and use it in build settings. Please check "Show system variables" to view the hidden system variables in the Build Variables page.

    After building the project, you can view in ***.txt file from the debug folder, which will update all the included directory. Please refer the attached screenshot(image2).

    You can refer the below help path which might be helpful to you.
    CrossCore® Embedded Studio 2.9.4 > Integrated Development Environment > Managing CCES Projects > Working with Resource Properties > C/C++ Project Properties Dialog Box > C/C++ Build Properties Page > Build Variables Properties Page

    If you are still facing the same issue, please share us the exact scenario that you are doing along with sample project to replicate the issue here. This will help us to assist you further.