• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 877 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: Best Practices for building on multiple platforms?

Paul Shepherd17
Intellectual 595 points

Tool/software: Code Composer Studio

I'm hoping you can point me to a good resource for setting up CCS for multiple developers on multiple OSes. We are trying to transition from me building code on my workstation, to a real infrastructure. We are using a git repository as the common codebase that information either gets checked into (if it's needed on all workstations) or ignored (if it is specific to a particular workstation).

Current situation: I build code on my workstation, and I push and pull changes to github. If I have a problem with my build settings (such as having to add an include directory which is a subdirectory of my project root), I do it, and it gets saved to the .cproject file.

Where we want to go: Me and another developer working on Windows, able to create and compile code for testing. Release builds and SQA being built on a Jenkins/linux server with automated tasks. Where I run into trouble is that parts of the .cproject file need to be very different on Linux. I can add the include directories to .cproject through CCS, but then I also pull in lots of other things that linux doesn't have, and it gets upset at those things.

Thanks in advance,

Paul

  • 0
    TI__Guru**** 173310 points

    When a project is to be shared among multiple users, it is best to make it portable. Please see this article on Portable Projects.
    Also take a look at this article for general best practices for creating and sharing projects within teams.

    Paul Shepherd17 said:
    Where I run into trouble is that parts of the .cproject file need to be very different on Linux. I can add the include directories to .cproject through CCS, but then I also pull in lots of other things that linux doesn't have, and it gets upset at those things.

    Could you elaborate a bit on what you mean here? Which parts of the .cproject file do you find needs to be different on Linux?

  • 0 in reply to AartiG
    Intellectual 595 points

    Thanks Aarti!

    I expect these documents will help me improve our setup.

    I have been learning as I go, which may be part of the problem. The project I am working on right now uses MSP430 DriverLib and SMBusLib. Both of these have the code included in the project, as opposed to referencing code that is maintained external to the project. My CCS installation defines some environment variables related to the compiler version, as well as the installation path and version of DriverLib and SMBusLib, and these environment variables are referenced in .cproject file. The Jenkins server could have a different version of the compiler, and should NOT have things like DriverLib and SMBusLib installed separately... It will only use the code which is included in the project that it is building.

    Thanks,

    Paul

  • 0 in reply to Paul Shepherd17
    TI__Guru**** 173310 points

    Paul,

    If the Jenkins server is not going to have the Driverlib and other libraries installed separately then yes the project has to be created in such a way that all sources/includes are part of the project and not referenced from elsewhere using environment variables. Certain variables such as the CCS and compiler install directories will get set automatically so those can be referenced easily. You could also consider sharing a variables file along with the project - there is information on this in the document I linked earlier.

    If you need the project to use a specific version of the compiler though (one that matches with your build), then that version of the compiler would need to be installed on the Linux server and CCS should be set to use that version.

    Hope this helps and feel free to contact us if you have questions in the future as you move forward with your set up and development.