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/TM4C1294NCPDT: Managing resources

Part Number: TM4C1294NCPDT

Tool/software: Code Composer Studio

Hi Folks,

I have a 2 distinct questions regarding managing relative large projects:

  1. If I want to add third party library to my project,  I add the header folder as linked resource let the developer to browse the headers: check the API. Is it possible to add linked resource depending on the build configuration? To see the right folders built to release or debug configuration?
  2. I think, quite often developer needs to use common resources, like string pieces, or compile time constant that are not belongs to a small area of the code. Is there any solution in Code Composer Studio to dedicated file to keep track such resources?
    An analog would be string resource / localization in Visual Studio & C# area, where resx files are used to store commonly used string resources

Regards,

Toth, Norbert

  • Norbert Toth said:
    If I want to add third party library to my project,  I add the header folder as linked resource let the developer to browse the headers: check the API. Is it possible to add linked resource depending on the build configuration? To see the right folders built to release or debug configuration?

    Yes it is possible to add/link resources per build configuration. 
    http://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_project-management.html#build-configurations

    Or you may simply provide the path to header files via the compiler's include path options, and this can be done per build configuration as well.

    Norbert Toth said:
    I think, quite often developer needs to use common resources, like string pieces, or compile time constant that are not belongs to a small area of the code. Is there any solution in Code Composer Studio to dedicated file to keep track such resources?

    I'm not sure if I'm clear on what you are looking for, but the linker supports symbol localization as described in section 8.4.19 of the Assembly Language Tools Users Guide: http://www.ti.com/lit/spnu118

    Hope this helps.

  • Hi,

    this is a snippet from my .project file:

    	<linkedResources>
    		<link>
    			<name>thidparty</name>
    			<type>2</type>
    			<locationURI>PARENT-1-PROJECT_LOC/thidparty_debug_build_headers</locationURI>
    		</link>
    

    In this file I don't know how to set linked resource that is only visible in debug configuration and another one that is visible only in release. This should be only for the developers, because compiler include path is set in .cproject file

    About resources:I am looking for a solution where you can collect project wide used strings (const char*) or other constants instead of putting them into header files.

  • Norbert Toth said:
    In this file I don't know how to set linked resource that is only visible in debug configuration and another one that is visible only in release.

    Linked resources are set at the project level, hence those lines in the .project file will be added whenever a linked resource is added to a project. Typically the build configuration specific setting allows you to "exclude files from build", and that setting will be passed on to the build tools. So both resources would be linked to the project but you could exclude a linked resource from one build configuration but leave it included in another build configuration: 
    http://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_project-management.html#exclude-files-from-build

    On the other hand, if you are looking for a way to show/hide a resource, you could look into whether working sets will achieve that for you. You can create multiple working set that show/hide specific resources and then view a particular working set in the Project Explorer view. More on working sets here: 
    http://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_project-management.html#working-sets