• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 566 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.

CCS4.x workspace

Steven Duckworth
Prodigy 50 points

I have had my mydocoments/workspace folder mapped to a 'H' drive on my new server. I have rediected CCS4.x to point to the mydocuments on my mapped 'H' drive.

Project build works fine however I am receiving a "Filesyatem out of sync" message when I invoke the debugger. This seems to refer ta a .launch file.

 

Do you have any suggestions as to how I can remedy the situation.

Steve

  • 0
    Prodigy 50 points

    So my current fis is to create a "workspace1" folder. and export all the existing projects from my workspace folder into an archive file. Unzip into the workspace1 folder.Redirect CCS workspace to this nwe folder and import the projects one at a time.

     

    Steve

  • 0 in reply to Steven Duckworth
    TI__Guru**** 162975 points

    Steve,

    A couple things you could try.

    Clean the workspace: change the CCS shortcut to use a -clean parameter (this will remove meta data)

    Delete the "launch": The launch is an eclipse debug launch which contains the settings used to create a debug session.  We try to abstract this in CCS.  As you are using projects you could delete the launch and it would be regenerated when you click the bug button.  To delete the launch click on the down arrow beside the bug button and select "Debug...".  Under "Project Debug Session" there should be an item that has the same name as your project.  Select it and then click the red X at the top of the dialog.  Now you can hit close and then try launching the debugger.

     

    Regards,

    John

  • 0 in reply to JohnS
    Prodigy 50 points

    HI John,

    cheers for the tip. Although I have exported all my CCS projects to a new workspace folder and imported the projects into a new workspace, which works, I will test the -clean parameter and let you know if it cured the original issue.

     

    Steve