• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 955 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/CODECOMPOSER: Automatic adding of include path

Dominik Lorenz
Intellectual 255 points
Part Number: CODECOMPOSER


Tool/software: Code Composer Studio

Hello there!

I've spend some hours troubleshooting and want to ask what I've done wrong/ share my experience:

I tried to share some files between projects and therefore wanted to move files from the project-folder to another location. Then i added the files back in as a linked resource. When i added header files, CSS convenitently asked me if it should adjust the build path to incude the file i was about to add.

Here comes the problem: when clicking yes, my project got messed up and cannot be built anymore.

"No rule to make Target"

"Target not supported: devkit.target.Generic"

In contrary, if i add the include path myself, no error occurs.

Cheers,

Dominik

  • 0
    TI__Guru**** 173310 points

    Dominik,

    Could you please provide some more details to help us reproduce this issue?

    - Which device family are you working with?
    - Do you have a project you could share with us that would help us reproduce this error?
    - I wonder if the error is triggered by something else other than the automatically added include_path. Did anything else change in the project other than changing the header files to linked resources?
    - What does the automatically added included path resolve to when you hover over the three dots at the end of the path (in the Include Options screen)? Is it pointing to the correct path?

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

    Since I haven’t heard back from you, I’m assuming you were able to resolve this issue and will be closing this thread. If you require further support on this issue, please post a reply with the additional details requested above. Thanks!
  • 0 in reply to AartiG
    Intellectual 255 points

    Aarti,

    Sorry for me not-replying. It was a busy time and then I forgot.

    • Anyhow, here the infos:
    • Im working with the F28377s
    • I will send you a project privatly, if you tell me your email.
    • I just reproduced the error again, and from my point of view, nothing else changed.
    • The automatically build path resolves to the right location.

    Maybe the issue is the place of the shared files: The Project is in the workspace-folder and the folder with the linked resources is in the same workspace-folder as well.

    For me, i solved the problem with deleting the whole project (without that it wouldnt work anymore, even if i deleted the linked resources(there were errors that shouldn't come from missing files)), importing it again and then adding the incude path myself.

    Dominik

  • 0 in reply to Dominik Lorenz
    TI__Guru**** 173310 points

    Dominik Lorenz said:
    I will send you a project privatly, if you tell me your email.

    You can share it via E2E private message. I will send you a friend request and initiate a private conversation.

  • 0
    TI__Guru**** 173310 points

    This issue was continued offline. 

    Dominik Lorenz said:

    I tried to share some files between projects and therefore wanted to move files from the project-folder to another location. Then i added the files back in as a linked resource. When i added header files, CSS convenitently asked me if it should adjust the build path to incude the file i was about to add.

    Here comes the problem: when clicking yes, my project got messed up and cannot be built anymore.

    "No rule to make Target"

    "Target not supported: devkit.target.Generic"

    In the OP's project, the action of adding files as linked resources somehow changed the RTSC "Target" field from ti.targets.C28_float to devkits.target.Generic. This resulted in the error: "Target not supported: devkit.target.Generic"

    If the user manually changed the Target field (under Project Properties->General->Products tab) back to the original value ti.targets.C28_float, then there are no errors.

    Unfortunately the issue was not reproducible at our end, so we have been unable to zero in on the root cause. Since the OP has a couple of usable workarounds we are closing this thread, but will continue to watch out for future occurrence of this issue.