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

Proper Way to Import Project Macros from Command Line

jsobota
Intellectual 995 points
Other Parts Discussed in Thread: CCSTUDIO

I can’t get CCS to properly import project macros, contained in the macros.ini file, and use them when importing and building the project from the command line.  What’s the proper way to do this?

 

Currently, I’m trying to import a project called qmssIpcBenchmark.  This project has a macros.ini file in which there is the following macro definition:

 

IPC_TRANS_PDK_INSTALL_PATH    = ..\..\..\..\..

 

 

I try to import this project from the command line with the following, specifying the macro as –ccs.definePathVariable.

 

eclipsec.exe -noSplash  -data "C:\myWorkspace" -application com.ti.ccstudio.apps.projectImport -ccs.definePathVariable IPC_TRANS_PDK_INSTALL_PATH "..\..\..\..\.." -ccs.location "C:\Program Files\Texas Instruments\pdk_C6678_1_0_0_11\packages\ti\transport\ipc\examples\qmssIpcBenchmark"

 

I’ve noticed that doing it this way only works once.  If I import and build the 6678 qmssIpcBenchmark project the IPC_TRANS_PADK_INSTALL_PATH macro will resolve to the c6678 PDK package directory.  Next, if I try to import the 6670 qmssIpcBenchmark, which uses the same macro, it will not reevaluate IPC_TRANS_PADK_INSTALL_PATH.  This then causes a failure in the 6670 project because IPC_TRANS_PADK_INSTALL_PATH points to the 6678 pdk.

 

Justin