• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 52 subscribers
  • Views 302 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.

CCS/CCSTUDIO: Opening a project IN PLACE

Christopher Weber
Genius 4995 points
Part Number: CCSTUDIO

Tool/software: Code Composer Studio

Hello,

As best as I can determine, CCS doesn't let you check out and open a project in the workspace folder...   How can I do that?

I checked a massive project out of our source control directly into the workspace.  First time it's been on my drive. 

Then I try to import, and it tells me:

See details below. 
  Invalid project description.
    C:\Source\dir1\dir1\dir3\projects\ProjectName overlaps the location of another project: 'ProjectName'

Of course it does...  IT'S THE SAME PROJECT

An hour of searches, all I come up with is just a suggestion that tells me All you gotta do it "import" example projects.

I have a massive project I have to enhance.  Am I supposed to:

  1. check it out of the source control to another location,
  2. use the IMPORT to copy the ENTIRE tree into the workspace folder
  3. update the code
  4. copy the ENTIRE project back to the other location where source checked it out
  5. Check it back in to source control

??

I can't believe no one ever thought about how to check out a project directly into a workspace.  But if they did, it's not easy to find.

Any advice?

  • 0
    TI__Guru**** 173310 points

    You can set the CCS workspace directory to be the folder that contains your source controlled project. For instance, if C:\Source\dir1\dir1\dir3\projects\ProjectName is the name of your project directory, then set the CCS workspace directory to be C:\Source\dir1\dir1\dir3\projects. Then go to the Project Import menu and set the search-directory to be the same directory. Make sure to uncheck "Copy projects into workspace". That should allow you to import the project.

    Also, I don't know which source control software you use, but there is an article on using Git with CCS.
    http://software-dl.ti.com/ccs/esd/documents/sdto_ccs_git-with-ccs.html
    Although it talks specifically to the Git integration in CCS, the general concepts and usage would apply to other source control software as well.

  • 0 in reply to AartiG
    Genius 4995 points

    Thank you, but this does not work.

    (By the way, I forgot to mention, I am using CCS7.  And the source control is MS VSS, which I cannot find a plugin that works)

    I should also add that is is a "Branch" where the folder name is NOT the same as the project name 

    i..e. project  BigProject  is in a folder called BigProject-branch2-3) 

    I Manually created a folder of the example "dir1/dir2/dir3/project/ " names, so I can redact company info...

    (I manually moved the entire project folder out of my existing folder, to this one.  So it is in there all alone.)

    And here is it...

    I open it, and naturally, it's empty

    Next up, do the "Import" as instructed:

    And it shows up as expected:

    (note, although redacted, the "Project" is the actual name of the project, the folder is the one that has the -Branch suffix )

    Press FINISH, and it fails.

    So, as I said.  This doesn't work.

    (I suppose I could go digging through those "hidden" files (leading dots in the name) and try to change the project name to be a "branch"...  but since it's all completely undocumented, changes are I would just break something and make it worse.   And may not work anyway...)

  • 0 in reply to Christopher Weber
    TI__Guru**** 173310 points

    I think the problem may be caused by how the project was originally cloned to your local directory. Eclipse expects the project to be in a sub-directory of the workspace, not the root workspace directory.

    As a test, could you try opening CCS in a new/different workspace (at a location completely outside of your current workspace directory), then try importing the project without copying it to workspace. Does that work?

    I think your issue might be related to this thread. Please see if the recommendations there are helpful.
    https://e2e.ti.com/support/tools/ccs/f/81/t/615348

  • 0 in reply to AartiG
    Genius 4995 points

    AartiG said:

    I think the problem may be caused by how the project was originally cloned to your local directory. Eclipse expects the project to be in a sub-directory of the workspace, not the root workspace directory.

    It is in a subdirectory in the workspace.  It is NOT just a collection of the files dropped into the root folder of the workspace.

    AartiG said:

    As a test, could you try opening CCS in a new/different workspace (at a location completely outside of your current workspace directory), then try importing the project without copying it to workspace. Does that work?

    "Without copying it...??

    Already did that test, and copy the entire project into the workspace...  Which is useless when you think about it...  It essentially means you are checking out code to one location, manually copying it to another location, editing it, manually copying it back to the first location, and checking it back in from there.

    Doesn't that sound really pointless and stupid?

    AartiG said:

    I think your issue might be related to this thread. Please see if the recommendations there are helpful.

    https://e2e.ti.com/support/tools/ccs/f/81/t/615348

    That link say the same as your first statement.

    Try cloning the GibHub project into a sub-directory in the workspace, where the sub-directory name matches the name of the project.

    If you actually look at the folders in question, (I know it's difficult since I blurred them out), "Projects" is the workspace, and the blurred out folder name is the one I'm trying to bring in.  It is a subfolder.

    This has something to do with the fact that the thing I am working on is in a folder named "bigproject-branch"... but the original project is just "bigproject"... So the subdirectory name does NOT match the name of the project.  Even through the original is NOT in the workspace at this time.

    And did no one ever consider that there could be a project where the name of the folder it is in doesn't match the project name?

  • 0 in reply to Christopher Weber
    TI__Guru**** 173310 points

    Christopher Weber said:
    Already did that test, and copy the entire project into the workspace...  Which is useless when you think about it...  It essentially means you are checking out code to one location, manually copying it to another location, editing it, manually copying it back to the first location, and checking it back in from there.

    Actually what I meant was to try the following:

    Leave the project in the directory where you checked it out. When starting up CCS specify a completely different workspace directory, something simple like c:\workspace. Use the Project import wizard to import the project and in the wizard do not check the box "Copy projects into workspace". This will essentially leave the project in its original directory, so any changes made to it will be saved in the original location.

    Christopher Weber said:
    This has something to do with the fact that the thing I am working on is in a folder named "bigproject-branch"... but the original project is just "bigproject"... So the subdirectory name does NOT match the name of the project.

    I think this could issues. Let me try to recreate this scenario and see if I can reproduce the error, and will get back as soon as I have more information.

  • 0 in reply to AartiG
    TI__Guru**** 173310 points

    We don't use MS VSS but I tried to do something similar with CCS projects version controlled to Git. I get a similar error (not exact but close) if I physically rename a project directory (so the project directory name is different from the project name) using Windows Explorer, (ie) outside of the CCS environment.

    Since project details are stored in the workspace, I believe a directory name change that happens under the hood is throwing it off. If a project were instead renamed from inside CCS then the project directory is also correspondingly renamed and CCS/Eclipse would manage it all.

    I think in your case if the project folder name is already different from project name during your version control checkout, using a different CCS workspace as I suggested earlier should help. Did you have a chance to give that a try?

  • 0 in reply to AartiG
    Genius 4995 points

    AartiG said:

    I think in your case if the project folder name is already different from project name during your version control checkout, using a different CCS workspace as I suggested earlier should help. Did you have a chance to give that a try?

    Yes, I had tried that, since (as my screen shot showed) I had created a completely empty workspace.  Still failure.  it can't import...  Because the folder name isn't the same as the project name.
    What I did instead, inside my completely empty workspace, was to change the folder name from "bigproject-branch"  to just "bigproject", because that is the main trunk name.  Then CCS could import it.
    So, the problem is you can't have a "branch" where the folder name differs from the project.  Meaning you can't have a "branch". The actual project name is buried somewhere in the CCS files.
    Why??  Why is it MANDATORY that the name of the folder match the name of the project that is buried is one of those hidden "settings" files?

    (it's only "hidden" because it has a leading dot in the name, but windows doesn't treat such a filename as "hidden" - something else that someone just presumed for their own Linux environment without knowing or appreciating that there are other OS's out there...  but I digress)
    My rather sloppy solution was to:
    • Download the "bigproject-branch" into a folder named "bigproject-branch" (since it's a branch...)
    • Rename the original "bigproject" folder to some arbitrary name
    • Rename the "bigproject-branch" folder to just "bigproject"  (now source control breaks)
    • Launch CCS and do the import.
    • Right click in CCS and rename the project to "bigproject-branch"  (now source control can find it again)
    • Rename the original back to normal.
    Now the source control environment can find the stuff it checked in/out.  I just have to remember not to merge whatever files are used to dictate the name of the project (which is, of course, hidden from the user... because this use-case was clearly not thought through)
    Now I imagine I am supposed to click "This Resolved..."  when it really didn't.  It just helped me find a hacky work-around.
    Isn't there a "This is a flaw, can you please consider solving it" button?  LOL!
  • 0 in reply to Christopher Weber
    TI__Guru**** 173310 points

    Christopher Weber said:
    So, the problem is you can't have a "branch" where the folder name differs from the project.  Meaning you can't have a "branch". The actual project name is buried somewhere in the CCS files.

    I'm not familiar with your source control software but in the Git integration with CCS, creating a branch does not rename the actual project directory name. Git just tracks information on which branch is checked out, etc. So it seems to be work a bit differently from your source control software.

    I tried to simulate your environment in one of my Git projects by doing the following:

    1) I used Git to rename one of the source controlled project directories. After this, the directory name was msp432p401x_1_MSP_EXP432P401R_nortos_ccs-branch, while the project name was still msp432p401x_1_MSP_EXP432P401R_nortos_ccs (as indicated by the  .project file below).

    2) Opened a CCS workspace in a directory different from the location of project 

    3) Imported the project. Import completed without errors.


    4) Project still physically resides in the "branch" directory so any changes made to the sources will be saved there.


    Unfortunately I am unable to duplicate the behavior you see, so there isn't anything specific I can request to be fixed. I know that doesn't help your immediate situation or alleviate the issues you are facing, but I will continue to be on the look out for such issues and will report back if I have any additional information. Thank you for your patience and sorry for the inconvenience.