• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 53 subscribers
  • Views 1002 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.

CCS/am3359: CCS 7.2 on Linux: New Project bug

David79
Intellectual 420 points
Part Number: AM3359


Tool/software: Code Composer Studio

Hello,

I'm using CCS 7.2 on Ubuntu 16.04.  I created a new CCS project, chose GCC 6.4...  The project created with an invalid path name:


Invalid project path: Include path not found (/home/david79/workspace_v7/tst/Debug/home/david79/ti/bios_6_51_00_15/packages/gnu/targets/arm/libs/install-native/arm-none-eabi/include/newlib-nano). 

Obviously, two include paths mistakenly became concatenated.  How do we fix this?

Regards,

-david

  • 0
    TI__Guru**** 173310 points

    David,

    I have not been able to reproduce this yet. Were these paths automatically added when you created the new project?
    If so, could you provide additional details on how you created the project, (ie) what selections you made in the New project wizard? 

    It might also help for us to see the project build output. If you can copy that to a text file and attach it here, that would be helpful.

  • 0 in reply to AartiG
    TI__Guru**** 173310 points

    David,

    I can reproduce this now. It appears to be specific to BIOS 6.51.0.15 as there was no such warning when I tried earlier with BIOS 6.50.1.12.

    The issue is reproducible on both Linux and Windows. I will file a bug report for it. 

    To get rid of the warning, you can go into Project Properties->Build->GNU Compiler->Directories and delete the entry:

    "${xdc_find:gnu/targets/arm/libs/install-native/arm-none-eabi/include/newlib-nano:${ProjName}}"

  • 0 in reply to AartiG
    TI__Guru**** 173310 points
    The tracking # for this issue is CCSIDE-3200. You may track its status using the SDOWP link in my signature.

    Although the warning is generated, the include paths seem to passed correctly to the compiler, so the build itself should not be impacted.