• Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 733 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.

Best practice for multiple libraries and executables in ccs4.2

Patrik Svensson
Prodigy 50 points

Hi. I am struggling with creating a good development environment using the latest ccs4.
I am trying to build one boot and one application that uses the same code base.
The code consists of rather many source files in a number of directories, this code is ported to other platforms than our C64x processor so I don't want to move the code around and mess up our subversion repository.
The project system seems to be a little different from Visual-Studio,GreenHill and other systems I have trie in that it seems to be flat so it does not use sub-projects.
Seems the only way to build a multi lib,executable project is to build several projects?
Or is there a way to create several outputs from one project, would be nice to only declare defines and include paths once and all projects uses the same?
And when releasing software it should be nice to only have to flick the release build in one project or globally so the effect is that all projects build with release compiler options.

For now I use the old makefile but that does not feel much like 2011!!

Regards
Patrik Svensson

  • TI__Guru**** 171519 points

    Patrik,

    Although I am not quite familiar with the sub-projects concept, CCSv4 has the concept of Referenced Projects. These projects are usually created to build libraries and its project options can be controlled by another project (usually the one that builds the executable) using the Active Build Configuration - Debug, Release, etc. To set referenced projects and its settings, right-click on an existing project and select Build Properties --> CCS Build --> tab Dependencies.

    Also, you don't need to change the location of your source files. Please check the references below that can definitely help you use the CCS features to efficiently create projects:

    http://processors.wiki.ti.com/index.php/Portable_Projects

    http://processors.wiki.ti.com/index.php/Linking_folders_to_a_project

    Hope this helps,

    Rafael

  • in reply to desouza
    Prodigy 50 points

    OK, I have tried that and it kind of work but I feel that I have not got a good manageble solution.
    My project consists of maybe 15 libraries containing 10 - 20 files each, but all uses more or less the same include paths.
    So is there a practical solution for inherit or get the same include path and defines spread into all library projects without having to manually enter the projects and set the paths.

    (For future development maybe you should consider compacting all project files into one instead of 4 + 2 directories per project)

    // Patrik