• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 1608 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.

make issue with CGT 7.3.0

gbl
Intellectual 400 points

Testing the new CGT 7.3.0 I ran into a make problem for command line builds (I have CCS5.1.0.05000 installed).

With CGT 7.2.4 the build command is properly resolved:

00:24:15  **** Build of configuration Release for project NC_common ****
00:24:15  
00:24:15  D:\Program Files\Texas Instruments\CCStudio_v5.1\ccsv5\utils\bin\gmake -k -j12 all

With CGT 7.3.0 this becomes

14:44:34  **** Build of configuration Release for project NC_common ****
14:44:34  
14:44:34  make -k -j12 all 
14:44:34  
14:44:34  Cannot run program "make": Launching failed
14:44:34  Error: Program "make" is not found in PATH

What is wrong with the translation of the make program and path in CGT7.3.0? (Eclipse builds work fine and the GUI settings also show nothing abnormal).
  • 0
    TI__Guru**** 169874 points

    Hi,

    The project build behaviour will obey the valid Windows rules with regards to PATH and executables, therefore your project must point to a valid make/gmake utility or simply call the one that is in the system's PATH.

    Check the project build behaviour at: Project Properties --> C/C++ Build --> tab Builder Settings. For each Active Build configuration used (check the drop-down menu close to the button Manage Configurations) you should have a valid utility in the Build Command text box. By default CCS leaves the check box Use default build command enabled, which usually is populated with ${CCS_UTILS_DIR}/bin/gmake -k

    I suspect the change in the Code Generation Tools versions opened a misconfigured Active Build Configuration of your project that pointed to the make utility. Unless the project manager has a bug, the simple update of the CGT does not cause this.

    Hope this helps,

    Rafael