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: Right way to clone project from GitHub to CCS

Tool/software: Code Composer Studio

Hi!

What is the correct sequence in order to successfully clone GitHub project to CCS? I have followed this step-by-step guide

  1. I create an empty workspace in CCS.
  2. Clone a GitHub project to this workspace (here is a sample project that I use for testing).
  3. Then I'm trying to import it in CCS by "Import CCS Project" and Browsing to my workspace. It is successfully discovered, but when I try to finish error pops-up saying: "Invalid project description path\...\myProjectName overlaps the location of another project: myProjectName"

I was able to import the project by firstly cloning it to another folder and then Importing it with CCS to my workspace by ticking "Copy project into workspace", but it is dodgy and loses synchronization with GitHub Desktop app.

  • Andrei Gasilovs said:
    It is successfully discovered, but when I try to finish error pops-up saying: "Invalid project description path\...\myProjectName overlaps the location of another project: myProjectName"

    Eclipse doesn't allow a project to be in the root directory of the workspace.

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

  • Hi,

    Thank you! That resolved my issue. However, this still made things little dirty as the result was Workspace/ProjectName/ProjectName/<Project Files>

    I've ended up with creating an empty workspace in CCS -> opening the Git perspective -> adding remote repository (GitHub) -> cloning the project to the workspace. In this case I have standard directory tree: Workspace/ProjectName/<Project Files>
    I then added this project (repository) to GitHub desktop app.
  • Andrei Gasilovs said:
    However, this still made things little dirty as the result was Workspace/ProjectName/ProjectName/<Project Files>

    My approach is to set up a structure as:

    Workspace/ProjectName/<Project Files>

    And set the Workspace directory as the folder which is cloned in GitHub. The Workspace folder has a .gitignore file to ignore the Eclipse artefacts (e.g. the .metadata directory). There is an example GibHub repository structure at https://github.com/Chester-Gillon/CC3100BOOST

    This approach can expand to have multiple projects stored in the GibHub repository, each in their own sub-directory.

  • Well, this indeed what I wanted to. As rarely I have a single project in the workspace. Thank you for sharing an example repository and .gitignore, really nice!