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.

Check tool versions when importing a project or compile time.

I was wondering if there is any way to check tool versions, like XDC Tools, Code Geneneration tools, SYS/BIOS, etc. when importing a project or at compile time.

The reason I ask is we use subversion to keep track of changes to our projects and I would like to ensure it will always build the same. If it is possible to check tool versions I would like to be able to throw some sort of error so the developer knows to change the tool version.

Thanks,

Mike

  • Mike,

    CCS does store the compiler, BIOS and XDC Tools versions as part of the project.  CCS will display a warning or error if the version is not present but it depends on how different the version is.

    i.e. if you have the 7.0.2 compiler and the project wants to use 7.0.1 then it doesn't display any error or warning as they are considered to be equivalent.  However if you have 7.0.2 and it wants to use 7.1.0 then it will tell you.  On a major version difference it will even stop you from building.  Below is an example error that I receive when trying to build an older project.

    This project was created using a version of Code Generation tools that is not currently installed: 6.1.12 [C6000]. Please install the Code Generation tools of this version, or migrate the project to one of the supported versions. BIOS6_configuration properties

    In v5.1 you get the error right after importing instead of having to wait until you build.
    Will that work for you?
    Regards,
    John

  • Thanks John, that's what I was looking for.

  • Where does CCS store this information? I am trying to move over to CCS 6.1 vs CCS 5.5 and everything compiles fine, but I get this stupid error of the compiler version being different. I don't want to go back to the older compiler - I have no reason to. How can I delete, disable or edit this such that I eliminate this error? Everything is compiling fine otherwise...
  • Alex,

    The version of the compiler that the project is configured to use is stored in one of the project files. It is pretty easy to change. Right click on your project and select properties. Select General in the tree on the left. The high level properties for the project are shown on the right. including the compiler version. You can change it there.

    Regards,
    John
  • I don't think that is it.  I right click the project and go into properties, go into General and the right/new compiler is showing.  Nevertheless, I still get the error message of not having the right compiler.

    Maybe this is important...here is the exact error message:

    This project was created using a version of compiler that is not currently installed: null [ARM]. Please go to <a href="liveaction:OpenAppCenter">CCS App Center</a> to install the compiler of this version, or migrate the project

    Notice that the previous compiler is listed as null.  Could that mean there is some missing parameter in the project file that perhaps I can update to the current compiler???

  • Hi Alex,

    Could you please attach the .cproject file from the root of your project?  I'll have a look.

    Thanks,

    - Baltasar

  • Search for:  [Src code deleted for privacy]  - which is the configuration I'm having trouble with:

    It's a bit long...

    ___________________________________________________________________________________________

    [Src code deleted for privacy]
  • Hi Alex,

    The project seems to be a hybrid that has both CCS Project and plain CDT project elements. I am not sure how this project was constructed, but CCS does not support this type of project structure. I would recommend splitting this project into separate CCS and CDT projects.

    - Baltasar
  • Ok, thanks. It was created before my time so I don't have info on how/when it was created. I'll look into creating new project files to replace the current ones. Thanks for looking into.

    On a side note, my source files build fine, so I kinda don't like the idea of CCS emitting this as an error to the build. At the very least, it should be configurable such that we can turn this "feature" off if we wanted to. I would submit this into TI's Suggestion Box for the future...