• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 954 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/LAUNCHXL-CC1350: Renaming an EasyLink Project example creates a build warning:

Rob Hepler
Prodigy 225 points

Part Number: LAUNCHXL-CC1350

Tool/software: Code Composer Studio

When I renamed the rfEasyLinkTx and rfEasyLinkRx project examples in CCS Version: 7.1.0.00016, the following build warning was generated:

Description Resource Path Location Type
This project contains 1 unresolved buildable linked resource(s). The project may not build as expected. 

The code executed fine however I warning concerned me.  I did find a work around but one would think the rename function of the project should work unless there was an oversight on my part.

Here is the work around:

1. I copied my workspace example to a new directory and changed the name of the directory to the one I wanted.

2. Found the example name in the .project, .cproject and .ccsproject files and replaced with my new name.

3. Imported into CCS.

I just built this and I did not see the warning anymore so hope this helps.  Anyway, I don't believe the project rename function is working correctly unless as I mentioned earlier, that I overlooked something.

Thanks,

Rob

  • 0
    TI__Guru**** 173310 points

    I have also seen some issues with renaming projects in the SDK, and as per this post, it is not recommended to rename the project in the CCS GUI, but rather do it in the .projectspec file. You can make a copy of the .projectspec file, change the "name" of the project and import using menu Project->Import CCS Project.

    Sorry about the inconvenience.

  • 0
    Prodigy 225 points
    Thank you. I did notice the project was pointing to the .projectspec file and thought about that so thank you for the information! I just wasn't quite sure if I needed to copy the .projectspec file to another directory and how that would work.

    Thanks so much!
    Rob