• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 3322 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS5.1: Path variables vs Build variables

David Aldrich
Expert 1345 points

Hi

Being quite new to CCS 5, we have found it rather confusing that there are 'Path variables' and 'Build variables', many of which may have the same value for a project  (e.g. PDK_INSTALL_PATH when using MCSDK on C66x).

What is the difference please?

David

  • 0
    TI__Guru*** 130875 points

    Hi David,

    perhaps someone a bit more expert will pipe up here as well but basically my understanding is the folloiwng

    Path Variables - these are only for paths.  Ie a path gets replaced by a variable for ease of use linking resources and using relative paths to link files etc. 

    Build Variable - these are like environment variables for the build of the project.  These are not restricted to paths. These can also be a value (like a normal variable), a file, etc.  If you try to add one you will see the options you have. 

    So where path variables are strictly to replace a path, build variables are actual variables.


    Please let us know whether my explanation is of any help.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Expert 1345 points

    Hi Lisa

    Thanks for replying. I think it is more complicated than your explanation. When specificying an Include Path (CCS Build > C6000 Compiler > Include options) my experience is that I can only use a 'Build variable' not a 'Path Variable' in the include path.

    That is why I think there is a difference in their use, even for paths.

    David

  • 0 in reply to David Aldrich
    TI__Guru**** 173310 points

    David Aldrich said:
    When specificying an Include Path (CCS Build > C6000 Compiler > Include options) my experience is that I can only use a 'Build variable' not a 'Path Variable' in the include path.

    David,

    You are correct. Build variables are to be used  in options related to the build environment, while, as Lisa mentioned, the Path variables are for specifying paths to source files linked to the project.

    In TI software examples that were originally created for CCSv4, they commonly created a macros.ini file that defined macros which when imported into CCSv4 (or v5) will set up that variable as a path variable as well as a build macro. One big difference between v4 and v5 is that in v4 when the project is imported the macros are set at a workspace level, while in v5 they can be set at the project level. So if the example was created for CCSv5, macros.ini is not needed and the variables will be set as path variable and build variable.

    More details are in this page: http://processors.wiki.ti.com/index.php/Portable_Projects#Portable_Projects_in_CCSv5

  • 0 in reply to AartiG
    Intellectual 470 points

    Product improvement suggestion:

    The PATH variables don't seem to be accessible via: project-right-click -> Build Options  (which seems the obvious place for it, and where I keep looking for it),

    but instead users are required to right-click -> Properties -> Resource -> Linked Resource (which brings up a window nearly identical to Build Options)

    I suggest removing "Right-click -> properties", or make it identical to the "build options" window.  PATH variables should definitely be accessible in the "Build Options" window.

    Thanks.