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

CCSv5 issues importing projects that use minGW?

Brad L
Intellectual 1245 points
Other Parts Discussed in Thread: CCSTUDIO

Are their known issues or limitation in CCSv5 properly importing projects that include minGW?

There are a few other posts in e2e that seem to indicate issues with the import, but they don't directly address the question if this is a supported feature in CCv5. (http://e2e.ti.com/search/default.aspx#q=mingw)

We are seeing the following issue:

One of the things I've done is rather than having separate projects for the target (running on a Tiva) and the simulation environment (using MinGW), I just added the MinGW build configurations to the existing Tiva CCS projects (which CCS allows you to do via "Build Configurations->Manage...")

 

The builds for both platforms using the unified project seem to work OK. The problem comes when some else tries to import the CCS project. They get the following message:

 

Error: Import failed for project '<proj name>' because its compiler definition is not available. The projects does not appear to be a 'CCS Project'. Please try importing it through the 'General > Existing Projects into Workspace' wizard.

 

If the user tries that, they get an error about using the Code Composer import wizard for the project.

 

Is there any way to do what I'm trying to do? Unfortunately I've spent a lot of time getting the projects to this state. As CCS didn't complain when I created these hybrid projects, it didn't occur to me that there might be a problem.

Any advise on a workaround or confirmation of CCS support would be helpful.

Brad

  • 0
    TI__Guru**** 171309 points

    Just for reporting, this issue is being worked offline.

    Basically the project contains three build configurations: two that use TI's compilers and one that uses GCC via MinGW. The project works fine until it needs to be imported to a different PC.

    We are not sure the details on how such project was created, but this is something our CCS Project import tool does not support. The best suggestion so far is to split the project in two.

    --Rafael

  • 0 in reply to desouza
    Prodigy 120 points

    I am having exactly the same problem (with C2000 and MinGW rather than Tiva and MinGW). It is then impossible to import, as either CCS import or General.

    If the solution is to split the project in two where should the two projects be? I have the problem that the project files have the same name so cannot be in the same directory, but they both need access to all the same files.

    The current layout is:

    .ccsproject
    .cproject
    .project
    source
    include
    tests
  • 0
    Prodigy 170 points

    Here is how I solved this issue for me.  Summary: In the project I have an extra build configuration with MinGW (for the test code with CppUTest).  Importing this project to another workspace would always fail.


    I was able to get it to import by editing the .cproject file in notepad++ (great for XML) and temporarily removing the <cconfiguration...> tag associated with the "foreign" build tools.

    Details:  In note Notepad++ the first cconfiguration is on about line 4 in the .cproject file.  Collapse it, and also the following configurations.  Delete the non-ti section. (I found that selecting the whole line would remove the collapsed selection)

    <cconfiguration id="com.ti.ccstudio.buildDefinitions.MSP430.Debug.xxxxxxxxxx">

    <cconfiguration id="com.ti.ccstudio.buildDefinitions.MSP430.Release.xxxxxxxxxx">

    <cconfiguration id="cdt.managedbuild.config.gnu.mingw.exe.release.xxxxxxxx">

    Save the file (don't close it though).   Import the project in CCS.  Close only the project (No need to close CCS).  Undo the changes to the .cproject file.  Reopen the project and you're all set.