• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 2188 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.

path name definitions in CCSv4

E2E_display_name_Mike
Expert 1700 points

I am currently in the process of migrating our CCSv3.3 projects to CCSv4.  I tried to read a lot of info on the wikis and forum to prepare and have had some success but I've been stuck on linking files into the project.  Like other developers, I want these links to be relative so other users can check out the projects from source control and not have issues.

I read the wiki posting regarding portable projects:

http://tiexpressdsp.com/index.php/Portable_Projects

I liked the suggestion of using the macros.ini file to define my own relative paths as they show in the example.  But I can't get this feature to work.  When I imported the legacy v3.3 project, a macros.ini file was created.  I tried to add path variables to that but they never worked.  I also discovered the path variable name that the CCS import wizard placed in that file was bogus.  In other words, it wasn't used for anything.  I could remove that path variable name and still rebuild the project.  Does the macros.ini feature still work?  I followed the instructions as per the wiki but nothing works.  It seems like CCSv4 doesn't read in this file or know it exists.  Can anyone help with this?

So now I'm using the first method, which is to use the CCSv4 settings (e.g. Preferences - General - Workspace - Linked Resources) to create a series of path variable names.  But this is not ideal because these are absolute names and it will need to be done for each user checkout of the project.  The nice thing about the macros.ini is that the wiki claims it accepts relative path names AND it is a file I can store in source control and just keep using that.  Also for new projects I can use that file as a template for any new paths.

So really I need advice on how to upgrade our projects in a way that paths to linked files can be relative.  I'd also like to enter these paths once and have them be imported/used for multiple users and different checkout locations.

thanks,

Mike

  • 0
    Genius 4925 points

    Hi Mike,

    I was trying for a while with the same feature. I noticed that the macros.ini file is only processed the moment you import a project into CCS4 (see chapter "Automated definition of Linked Path Variables " in the "Portable Projects" Wiki). So if you have now a macros.ini file that you think is OK, delete your project from the project browser an re-import it. This should end up in a working configuration with macros.

    Hope this helps

    Best

    Andreas

  • 0 in reply to andreas von kaenel
    Expert 1700 points

    Andreas,

    ok - got it!  I tried doing a project refresh and even restarting CCS but those didn't work.  Didn't think of trying the delete and re-import.  After all this I decided the import wizard for legacy v3.3 projects isn't very good.  I just create new projects and add my own path names for linked files and use only relative paths for compile/link include paths.  It ends up being faster and cleaner than using the import wizard and then cleaning up the absolute paths and macro variables created by the wizard.

     

    thanks,

    Mike