Command line eclipsec.exe usage

Hi,

I've read this wiki link http://processors.wiki.ti.com/index.php/Projects_-_Command_Line_Build/Create for getting information about building a project from the command line. Using this command:

eclipsec -nosplash -data v:\CCSv5_Workspaces\mainLine -application com.ti.ccstudio.apps.projectBuild -ccs.projects DTecSensorDsp -ccs.buildType full

It works well until a first warning message is displayed from the compiler, then the process hangs and it won't continue. For example, this is the last message displayed after having several files successfully compiled:

'Building file: V:/Perforce/software/embed/mainLine/M_EMB0006_drivers/src/dm6437/i2c.c'
'Invoking: C6000 Compiler'
"C:/CCSv5/ccsv5/tools/compiler/c6000/bin/cl6x" --cmd_file="V:/Perforce/software/embed/mainLine/M_EMB0003_dtec/proj/CCSv5/dtecMain/Cfg/includePaths.opt"  -mv64+ -g -O2 --gcc --define=_NO_IR_CUT_FILTER
--define=PN_53A0010 --define=TRACKING_ALGO_TEST_VECTOR_ENABLE --define=DEVICE_TYPE_DTEC --define=USE_CUSTOM_DATA_SERVER --define=LEGACY_EEPROM_SUPPORT --include_path="C:/CCSv5/ccsv5/tools/compiler/c60
00/include" --include_path="C:/CCSv5/ccsv5/../bios_5_41_11_38/packages/ti/bios/include" --display_error_number --diag_warning=225 --abi=coffabi --preproc_with_compile --preproc_dependency="src/M_EMB00
06_drivers/dm6437/i2c.pp" --obj_directory="src/M_EMB0006_drivers/dm6437" --cmd_file="./configPkg/compiler.opt"  "V:/Perforce/software/embed/mainLine/M_EMB0006_drivers/src/dm6437/i2c.c"
"V:/Perforce/software/embed/mainLine/M_EMB0006_drivers/src/dm6437/i2c.c", line 529: warning #179-D: function "I2C_EnableFreeMode" was declared but never referenced

How can I make the process finish? Also, is there some documentation about additional options that we can specify on the command line (for example, if I want to send the output in a log file, etc.)

Thanks

Franck

  • Franck,

    Franck
    It works well until a first warning message is displayed from the compiler, then the process hangs and it won't continue.

    Can you run the same command successfully from a command prompt? You can simply copy and paste that whole command as displayed in the console. What about from within CCS? That would help narrow it down to whether it is the compiler that is hanging or CCS.

    Looks like the source files are on a network drive. As a test, does the build finish successfully if the source files are copied over to a local c:\ drive?

    Franck
    Also, is there some documentation about additional options that we can specify on the command line (for example, if I want to send the output in a log file, etc.)

    Not sure if there is an option to redirect the build output, but you could simply redirect the output of the command to a file
    (eclipsec -noSplash -data "C:\workspace" -application com.ti.ccstudio.apps.projectBuild -ccs.projects testproject > c:\buildlog)

    Also if buiding using CCS, the logging is automatically enabled. You can take a look at where the log file is saved by going to Proejct Properties->C/C++ Build->Logging.

  • In reply to AartiG:

    Thanks for the response.

    I have done what you suggested and was able to nailed the source of the issue. Actually, creating a brand new CCS workspace and importing my project in it made the problem disappeared. Unfortunately, if I use the "Export/Import  Team Set File" to reload all my projects in the new workspace, the same issue reappears. On the other hand, in that specific case, the build will work fine the very first time executed, but will fail on any other try.

    So I will re-import manually the projects in the new workspace for now.

    Would you like me to try anything else before I destroy my defective workspace?

    Franck

  • In reply to Franck:

    Franck,

    Good to hear that importing the project into a new workspace allows it to build properly. It is odd that if you import all projects, that the build works the first time but fails after that. I don't really have a good explanation for that or another suggestion to try. I will try to see if I can reproduce similar behavior at my end and keep you posted if I do, but go ahead and import the projects manually for now and let us know if you run into other problems.