• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 829 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.

Import project with macros.ini does not work

Franck
Intellectual 685 points

Hello,

I am used to import my projects with a macros.ini file for getting projects with relative paths. But strangely, I am now getting an error message I have never encountered before. Here are my setup:

- I have a project with a macros.ini file defining the path variable SRC_ROOT.
- The project contains several linked files and folders
- The linked files and folders are not under the project root folder
- The project root folder is not inside the workspace root folder
- My workspace already has a path variable SRC_ROOT defined with the correct path (because other projects use this same variable).

If I import my project with the "Project -> Import existing CCS... project", I get the following error window:

The project looks being imported anyway in the workspace, but any linked folder/files does not appear.

On the other hand, if I first delete the path variable SRC_ROOT in the workspace and repeat exactly the same procedure, the project is successfully imported with no error message.

Is there something I am doing wrong or is this a bug with the import feature?

Thanks

Franck

  • 0
    Intellectual 685 points

    Missing the error message image in my original post. Here it is:

  • 0 in reply to Franck
    TI__Intellectual 1490 points

    hi,

    I faced same issue .

    Are you using ccsv4.2? Sometimes  I need to click on File -> Import -> Code composer Studio -> Managed Build Macro and select the macro.ini file.

    You need to overwrite the value if already existing.

    I thought it was better in ccsv5.1, but sometime  Istill need to do this.

    And if it still not ok, you can close and reopen the project

    rgds

  • 0 in reply to Claudio06
    Intellectual 685 points

    Hello,

    Yes I am using CCS v4.2.4. The steps you suggest actually appears to be another valid workaround for this issue.

    So I understand that this is a known issue/limitation for the import feature of CCS that is not caused by any specific misuse? If so, I will just apply the workaround when the problem shows up.

    Thanks

    Franck