• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 276 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/TM4C129ENCPDT: Set up TivaWare as referenced project in CCS?

twelve12pm
Genius 4455 points

Part Number: TM4C129ENCPDT

Tool/software: Code Composer Studio

Once upon a time I recall seeing an explanation how to set up TivaWare as a referenced subproject in CCS. But I can't find it. Does anyone know where it is?

What I'm trying to achieve: I have customized some parts of TivaWare. Rather than referencing all its source files from my firmware project directly (which implies that it gets cleaned and built each time, taking a long time), I think putting it in a separate project and referencing the project will allow me to clean and build just my project (without rebuilding TivaWare) or to clean and build the whole workspace. Does that sound correct?

  • 0
    TI__Guru*** 135355 points

    Hello Twelve12pm,

    If by TivaWare you mean the driverlib portion, then you should just be able to import the driverlib project directly into your CCS so you can recompile that way. Then you could just use the .lib file. But it sounds like you don't want to re-build TivaWare each time, so if that's the case then this wouldn't work as well.

    The other method we often talk about is for debugging with being able to go into driverlib calls, then you would need to make links to all the relevant files into your project and unlink the library. This method would let you build all the files you linked without needing to rebuild driverlib. The idea here is you only include relevant files this way and not all of driverlib so it doesn't take time to build unused files.

    I think these are along the lines of what you are looking for, but I'm not quite sure about the 'subproject' portion of your post as I've not heard something like that before so maybe I am missing a key detail.

  • 0 in reply to Ralph Jacobi
    Genius 4455 points

    Hello Ralph,

    Thank you for your reply.

    I am not sure if "subproject" is the right term but when importing a CCS project into the workspace, there is a checkbox in that window to the effect of including referenced projects in the import. I'm not sure what that means but it sounds like a feature that some IDEs have when a project can have another project as a dependency, and then each project is only built when its files change, but the output of one project is used as an input to another (e.g., a firmware project having one or more libraries as nested projects). Not sure if this makes any sense.

  • 0 in reply to twelve12pm
    TI__Guru*** 135355 points

    Hello Twelve12pm,

    Hmm I see, I can't say I ever used that feature which is why I was a bit confused by the description. Make sense now.

    Based on that, if you are wanting to reduce the amount of builds you need to do, then I'd just recommend doing to direct link of the driverlib files into your project, that way you don't have to re-build the library or drag in additional projects with your own project. Honestly I wouldn't see any advantage to pulling in driverlib with your project like you are describing. If you make a change to a file in driverlib, you will need to re-build that file, so either you need to rebuild all of driverlib, or you can rebuild the files associated in your project.

    Hope that explanation helps more :)

  • 0 in reply to Ralph Jacobi
    Genius 4455 points

    Fair enough. Thanks for your help.