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

CCS4.2 PATH environment variable?

David R.
Expert 1295 points

Hello-

I'm trying to use CCS 4.2.1.00004 to build an existing (successfully-imported) C project that targets a TMS570 controller. However, it seems that the IDE cannot find many of the build tools; here is the console output:

'cl470' is not recognized as an internal or external command, operable program or batch file.

On my system, cl470 resides in c:\Program Files\Texas Instruments\ccsv4\tools\compiler\tms470\bin, but I don't see this directory on the PATH environment variable. This was a fresh CCS install on a shiny new Windows XP installation.

I can add this path to the PATH env var, but I don't want to get into a game of whack-a-mole trying to piecemeal the environment together. If the installation is for some reason incomplete, I would like to get it right before continuing development.

Thanks,
Dave 

  • 0
    TI__Guru**** 480861 points

    Hi Dave,

    Do you see the path to the ARM compiler (c:\Program Files\Texas Instruments\ccsv4\tools\compiler\tms470) in your CGT discovery path?

    ki

  • 0 in reply to Ki
    Expert 1295 points

    Hi Ki-Soo-

    Thanks for the reply. I do the see correct paths in Window->Preferences->CCS->Code Generation Tools, and the "Discovered tools" lists the tms470 directory.

    However, I am using a custom Makefile, and the CLCOMPILER_ROOT is undefined when I select "Build Project". If I define this as an environment variable in Windows, the build works.

    Is there a way that I can have CCS define this variable when building outside the managed make system?

    Thanks,
    Dave