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

CCS4 - .project file always changes when it gets imported into a new workspace - PING PONGing between two versions of contents!

vincent groarke
Prodigy 70 points

Hi,

When I import a CCS4 file into a workspace I see that the .project file for that project changes. If I import it again into a new workspace, it changes again! Then if I import it into a new workspace a third time it changes back to the original version. If I import it into a new workspace again then it reverts to the second contents.

Naturally this is bad because I want to be able to share the project among differen enginners, each with their own workspace without having the project file change!

I've attached a copy of the difference between the two project files that seem to PING PONG as the project gets imported into a new workspace. (this post doesn't allow me to attach the .project file itself - file type not allowed!?)

All help gratefully received,

Vincent Groarke, Senior SW Engineer, Moog Ltd

 

 

 

  • 0
    TI__Guru**** 161500 points

    Vincent,

    Just to confirm this is the same CCS version just creating new workspaces and importing the project right?

    John

  • 0 in reply to JohnS
    Prodigy 70 points

    Hi John,

    It sure is.  

     

    Code Composer Studio

    Version: 4.2.1.00004

    The project itself was originally a CCS3 project but this was successfully imported some time ago into CCS4 and it builds fine, etc.

    [ Aside: Originally, when it used to be a CCS3 project, it used its own makefile but this caused no problem on import to CCS4.]

    In case it helps, I've attached a file containing the the "Configuration Details" I get from my installation. I had updated all features recently.

    Many Thanks,

    Vincent

    0451.configforccs4.txt

     

  • 0 in reply to vincent groarke
    Prodigy 70 points

    Hello,

     

    Any update on this problem?

     

    Thanks,

     

    Vincent

  • 0 in reply to vincent groarke
    TI__Guru**** 161500 points

    Vincent,

    We had one similar problem that we have fixed but it impacts a different part of the .project file.  We haven't had any luck reproducing this particular problem.  based on the screen shots you sent it seems to be happening with standard make projects where Eclipse/CDT is rearranging the parameters on import.  However I can't see this on my install.  Any chance you could send me a sample project that shows this for you?  I may not be setting enough parameters perhaps, although the screen shot looks like it is pretty simple.

    If you could click on my name and send me a private message with a sample I can get it to our build system lead to try to resolve the issue.  I could also try it out in v5.

    Regards,

    John

     

     

     

  • 0 in reply to JohnS
    TI__Guru**** 161500 points

    Vincent,

    With the example project you sent I was able to reproduce the issue.  We should be able to use this to figure out what is going on.  I have filed SDSCM00039848 to track this issue.

    Regards,

    John


  • 0 in reply to JohnS
    Prodigy 70 points

    Hi John,

    I got a notification this morning:"Ki-Soo Lee verified a post as an answer to Re: CCS4 - .project file always changes when it gets imported into a new workspace - PING PONGing between two versions of contents!  in Code Composer Forum. "

    What exactly does this mean?

    Many Thanks,


    Vincent

     

  • 0 in reply to vincent groarke
    TI__Guru**** 161500 points

    Vincent,

    It means that the moderate has verified that the question posed has been answered.  In this case that the issue you reported had been reproduced and a defect has been filed with the engineering team to resolve.

    The defect ID is in the thread and you can use the link in my signature to track its status.  If I check the status in our internal system I can see that it is fixed and slated to be released in 4.2.4.

     

    Regards,

    John

  • 0 in reply to JohnS
    Prodigy 70 points

    Thanks John.

     

    When is 4.2.4 due to be released?

     

    Vincent