• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 1207 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.

CCS: CCSV6 : Compiler version selection via relative path

Andy Castle
Prodigy 150 points

Tool/software: Code Composer Studio

I am trying to construct a project footprint that includes the compiler version used in that build / release.  So everything used within the project is installed from a "MyProject" folder, including the compiler.  This would allow me to have multiple versions in different locations and they would all use the version of the compiler specific to them.   This means all paths must be relative to ${WORKSPACE_LOC}, which seems to work ... except :-

I setup the compiler version appropriately to a sub folder within my project area ( Project->Properties->CCS General->Compiler Version ) and it works fine.  BUT if I then move the project under a new top level project folder the compiler version is lost and it refuses to build saying the compiler version doesn't match that used to previously build the project. This suggests the path used by CCS is absolute rather than relative, even though I gave manually gone through ALL build and environment path variables and made them relative to ${WORKSPACE_LOC}.

Is there a solution to this ? Is this information stored within a config file somewhere that I can modify ? I will upgrade to CCSV7 soon but it seems this feature is unchanged so my problem will still exist ?

  • 0
    TI__Guru**** 162255 points

    Andy,

    The project itself does not store the location to the compiler it just stores the version of the compiler it is set to use.  You will see include paths like "${CG_TOOL_ROOT}/include" in the project.  At build time CCS populates the CG_TOOL_ROOT macro (and a number of other similar ones) with the location of the compiler that the project is selected to use.  Thus team members are not required to have the compiler installed in the same location.

    In the preferences dialog in CCS you specify where it should look for compilers.  This is where you ended up from the project properties.  It just redirects to this dialog.

    I am assuming you are putting the compiler in the project in an attempt to ensure that people use the correct compiler to build the project.

    If you are checking the compilers into version control you could potentially put them in a common top level folder and then have your team members add that folder (where ever it is located on their machine) in the preferences dialog.

    Regards,

    John

  • 0 in reply to JohnS
    Prodigy 150 points
    Thanks John,

    Your assumptions are correct regarding my project / version control structure. We will have several projects on different MSP430 variants so I would like the compiler within each individual project if possible.
    You are also correct in that CCS doesn't 'forget' the compiler location, I checked the respective environment / path variables and they are still correct. But it does forget the compiler version, it has a red flag on the general properties page, and the select compiler version dialog has a blank field where the compiler version used to be.

    Is the compiler version stored within a config file under the /.metadata folder anywhere ? If you could tell me which file I could check it.

    Andy
  • 0 in reply to Andy Castle
    TI__Guru**** 162255 points

    Andy,

    The version of the compiler used for a project is stored inside the project files.  Specifically in the .cproject file.

    CCS should not be forgetting the versions.  It stores that information here:

    <ccs install dir>/ccsv7/eclipse/configuration/ccs.properties   

    Can you show me a screen capture of what you mean by the red flag?  CCS will show little indicators beside the version number if the project is set to use a version but CCS cannot find that version and instead is using another one.

    In this case it will show the version selected along with the version that will be used.  This is what it looks like in CCSv7.4.  In CCSv6.x it might have been bit different.

    If those versions are very different then it will show an error.