• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 54 subscribers
  • Views 3577 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.

CCS3.3 to CCS5.1 project migration

David Boles
Intellectual 850 points

Migrating an existing project from CCS3.3 to CCS 5.1 I get the following message:

!WARNING: Reference to the legacy 'Install_dir' macro detected.  This reference has been replaced with new macro 'CCSv3_INSTALL_ROOT', resolving to a local CCSv3.x installation which has been found at 'C:/CCSTUD~1.3' [Window > Preferences > C/C++ > Managed Build > Macros].  It is recommended, however, that you do not reference any resources from the legacy CCSv3.x installation - consider copying these resources into a product-independent location, and referencing them using a new user-defined macro.

When I build my project I get the following errors

Description    Resource    Path    Location    Type
Build variable 'CCSv3_INSTALL_ROOT' cannot be resolved.     TransactionObjectId.cpp    /CommonDSP    properties    TI Problem Marker (actually many of these)
Invalid project path: Include path not found (\bios_5_21\packages).    CommonDSP        pathentry    Path Entry Problem
Invalid project path: Include path not found (\csl_c6455\inc).    CommonDSP        pathentry    Path Entry Problem
Invalid project path: Include path not found (\csl_c64xplus_intc\inc).    CommonDSP        pathentry    Path Entry Problem

So, where do I modify the CCSv3_INSTALL_ROOT macro/definition to fix these errors?  I do not see  Window > Preferences > C/C++ > Managed Build to change it.

  • 0
    TI__Guru**** 450031 points

    Hi David,

    David Boles said:
    So, where do I modify the CCSv3_INSTALL_ROOT macro/definition to fix these errors?  I do not see  Window > Preferences > C/C++ > Managed Build to change it.

    That message is out of date (it applies to CCSv4). Macros have been replaced with build variables in CCSv5.1 and [Window > Preferences > C/C++ > Managed Build > Macros] has been replaced with [Window > Preferences > C/C++ > Build > Build Variables]. This message needs to be updated for v5.1, I filed a bug for this: SDSCM00043553

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 850 points

    Thanks. 

    Also the log message needs updated.  I thought it had already done this.  But I had to add it.

  • 0 in reply to David Boles
    Intellectual 850 points

    I also have a linked project to the one in my first post.  I'm getting the following error:

    **** Build Finished ****
    Buildfile generation error occurred..
    Build-configuration 'Release' does not exist in the referenced project 'CommonDSP'. Use the 'Properties > CCS Build > Dependencies' page to select an existing build-configuration.
    Build stopped..

    Again, I do not see this option in CCS5.1



  • 0 in reply to David Boles
    TI__Guru**** 450031 points

    David Boles said:
    I also have a linked project to the one in my first post.  I'm getting the following error:

    Did the original v3 project have dependent projects or is this a dependency you created after the import?

    David Boles said:
    Use the 'Properties > CCS Build > Dependencies' page to select an existing build-configuration.

    The actual link is 'Properties > Build > Dependencies'. right-click on the project first.

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 850 points

    The dependency was in the V3.3 project

  • 0 in reply to David Boles
    TI__Guru**** 450031 points

    CCSv5 does not automatically import any dependent projects when importing a v3 project. You will have to import them manually (if you have not done already) and then setup the dependency again.

  • 0 in reply to Ki
    Intellectual 850 points

    Is there a document describing how to do this?

  • 0 in reply to David Boles
    TI__Guru**** 450031 points

    Yes, but too bad it is out of date <bangs head on wall>

    The steps to do it in v5.1 is to right-click on your project and under Build -> Dependencies tab, press the 'Add...' button to bring up a list of all the projects in your workspace and select the project you wish to create a dependency with. Then your will see the dependent project added to the list of 'Referenced Project'. From there you can select which build configuration to create the dependency with. <active> will use the currently active configuration for the dependent project.

    ki

  • 0 in reply to Ki
    Prodigy 230 points

    Ki, 

    This is how I do set the dependency. However somehow it is delete by the editor somehow after multiple build. 

    Could you tell me how to avoid this behavior? 

    Best regards,

    Keli

  • 0 in reply to Ki
    Expert 1960 points

    Ki-Soo Lee said:

    The steps to do it in v5.1 is to right-click on your project and under Build -> Dependencies tab, press the 'Add...' button to bring up a list of all the projects in your workspace and select the project you wish to create a dependency with. Then your will see the dependent project added to the list of 'Referenced Project'. From there you can select which build configuration to create the dependency with. <active> will use the currently active configuration for the dependent project.

    I am too having the same problem when importing a v3.3. project in v5.1 but i am not even able to  see my projects in workspace  when i press add button why?