• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 100 subscribers
  • Views 2086 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

#include <xdc/std.h> not found in project with separate config project

Mark Piontek
Prodigy 190 points


I created a new CCS6 project using GNU v4.7.4 (Linaro) compiler and template Sys/Bios->Gnu Target Examples->Typical (with separate config project).

The new project does not build, it ends with "fatal error: xdc/std.h: No such file or directory"

It seems there is something missing in the project template. From the error message I'd expect there is an include path missing, but when I add the path to xdc/std.h I get even more errors.


When I create a new CCS6 project with template Sys/Bios->Gnu Target Examples->Typical, without separate config project, this works as I expect it. This project uses the same include paths as the one before.


Any help is greatly appreciated.

  • 0
    TI__Genius 10260 points
    Hi Mark,

    What software products/versions are you using (TI-RTOS, CCS, XDCTools, etc)? What device are you developing for? Can you elaborate on what you mean by "separate config project"? Do you have some screenshots you can provide?

    Regards,
    -- Emmanuel
  • 0
    TI__Mastermind 37985 points
    Mark,
    I can replicate the problem. There is a workaround that should lead you through the compile step, at least. I have found some problems with the link step too but they might not exist for you.
    So, go to the Project Properties->CCS Build->GNU Compiler->Set Additional Flags. Add the following to the end of the command line:
    @<path to the _configuration project>\Default\configPkg\compiler.opt
    Let me know if that works.
  • 0 in reply to Sasha Slijepcevic
    Prodigy 190 points

    Hi Sasha,


    the compile step works now, but the link step fails.

    I get the following linker error:

    cannot find -lC:/Projekte/TI/SeparateConfig_configuration/Default/configPkg/linker.cmd

    The file linker.cmd exists in the location the linker complains about not finding it.

    I checked the build log of a project without separate configuration project, here the file linker.cmd is used like this:

    -T"./configPkg/linker.cmd"

    This made me check the linker settings.

    Even when linker.cmd is added under "Linker command files (-T, --script)"


    it shows up in the summary with -l:

    Even when I remove the first two entries in the CCS Builds->GNU Linker->Libraries settings,

    -lC:/Projekte/TI/SeparateConfig_configuration/Default/configPkg/linker.cmd

    still shows up in the summary of flags set.

    Best regards,

    Mark

  • 0 in reply to Mark Piontek
    TI__Mastermind 37985 points
    Mark,
    I tried to find a workaround for a link step too so you can proceed with your build, but I couldn't. I think at this point you should move this thread to the CCS forum (e2e.ti.com/.../code_composer_studio) because CCS controls both of these command lines, and that's where the actual fix for the problem would be implemented.