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

Avoid migrating to CCSv4 of the same project in a different workspace.

Girish Srinivasa
Prodigy 480 points

Hi,

  I have migrated the CCSv3.3 projects on to CCSv4.0.2. I have used the import legacy ccsv3.3 project command & followed the wizard.

Now after I do this, in another workspace I need to open the projects again, I try to use import existing ccs/cce eclipse project. But though I give the top level folder [ where the files created when I migrated to CCSv4 are present, it does not find the migrated project??

 

What could be the reason? How do I make sure the next time somebody does not need to import the legacy project again to CCSv4?

 

Rgds,

Girish

 

  • 0
    TI__Guru**** 483551 points

    Hi Girish,

    Your use case sounds fine, it should detect an existing v4 project if you specify the project folder. When you imported the original 3.3 project to v4, did you copy the files into your workspace or left it alone?

    ki

     

  • 0 in reply to Ki
    TI__Prodigy 480 points

    Ki,

    After I migrate to CCSv4, the follwoing four files get created

    .ccsproject
    .cdtbuild
    .cdtproject
    .project

    I have them in the build folder. But when I give the build folder to find project files, it does not. What could be wrong??

     

     

  • 0 in reply to Girish Srinivasa
    TI__Guru**** 483551 points

    But where is your project folder? In the original location or inside one of your workspace folders?

  • 0 in reply to Ki
    TI__Genius 15870 points

    Girish, 

    Import existing CCE/CCS project tool will not show you projects that already exist in your workspace. i.e. it does not allow duplicate projects. Could it be that your 3.3 imported project is still in the workspace when you try to import a v4 converted project? 

     

    fyi... newer version of eclipse and future version of CCS will handle this a bit better by showing you that a project has been discovered, but it will be grayed out to indicate that project can not be imported. 

    martin