• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 825 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/CC1310: Directory Automatically Excluded from Build on CCS Startup

Michael O'Brien1
Prodigy 90 points
Part Number: CC1310
Other Parts Discussed in Thread: SYSBIOS

Tool/software: Code Composer Studio

My project's source code is located in a src/ directory beneath my project. When I import the project, src/ is not excluded. However, when I start the build, the project file is modified, a .exclude file is created, and the src/ directory is excluded from the build. This of course makes the build fail. If I manually un-exclude the directory, the build will succeed. However, when I close CCS and start it up again, the directory is once again excluded.

My original project is on CCS 6.1.2.00015. I have upgraded to CCS 7.0.0.00043 and see the same issue. I have also tried re-creating the project by selecting the TI-RTOS minimal empty project for CC1310 and copying in all of my source files. This produces the same situation.

I can provide the project files upon request. The issue is consistently reproducible on my system.

What do I need to do to keep the src/ directory permanently un-excluded?

  • 0
    TI__Guru**** 173310 points

    Michael O'Brien1 said:
    When I import the project, src/ is not excluded. However, when I start the build, the project file is modified, a .exclude file is created, and the src/ directory is excluded from the build.

    For TI-RTOS projects, a /src directory is created at build time to hold SYSBIOS generated files, and this folder is typically excluded from the main project build. Try putting your project's source code into a folder with a different name instead, like "source" so it doesn't conflict with the BIOS generated folder.

  • 0 in reply to AartiG
    TI__Prodigy 90 points
    This solved my issue.