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.

Problems running compiler from command line

Other Parts Discussed in Thread: CODECOMPOSER, CCSTUDIO

I can successfully build my project using either CodeComposer Studio or timake.exe. Current versions are:

Integrated Development 5.98.0.393

BIOS 5.33.02

Code Generation Tools v6.0.8

The project build consists of first compiling a number of .c files to produce .obj files, creating an archive of those obj files, and then doing other compilations and links. Using the make file created by the IDE I wanted to get a working makefile to use. The problem I've run into is that the most simple step - that of compiling a single .c file produces a different .obj file when run from my makefile vs run from either the IDE or timake. I've verified that the options match (both from the log file shown when running in the IDE as well as looking at the projects build options). Its's nothing to do with the make script as if I create a single line batch file to do one compilation I get an obj file that matches that produced by my makefile but different from that produced by the IDE or timake. So there must be some option or configuration step that both the IDE and timake do but my makefile isn't? Running dosrun.bat before my make script doesn't change things. Although I can get by with timake I'd like to understand what I'm not doing correctly.


Anyone have any suggestions?

Thanks!

 

  • When you saythe object files are different, how are they different, just different sizes or do they not work?

  • The object files differ both in size and contents. If I build the code using the IDE, then again using timake and compare the two resultant .bin files they are exactly the same (in size and contents). I want to do the same comparison with the results from my make script.

  • Building with timake should be the same as building with the IDE (same project manager used in both cases).

    There must be some option that is different or different versions of the compiler is being used. Can you attach your project file and make file?

    Thanks

    ki

  • Just adding to Ki's and Bernie's replies, make sure that:

    - Dosrun.bat points to the desired compiler and DSP/BIOS tools used, as well as the default library search path (variables C6X_C_DIR, C6X_A_DIR, etc.). This file is not updated when new compiler and DSP/BIOS tools are installed and usually points to the default ones provided with CCSv3.3;

    - The compiler in the path is the same as the one used inside the IDE. Run cl6x --compiler_revision from the command line and check its version;

    - Do the same with DSP/BIOS tool: run tconf -h and see if the first line points to the correct directory under DSP/BIOS install directory: typically C:\CCStudio_v3.3\bios_5_xx_xx\xdctools\tconf.exe

    - Make sure all the options on the project and the *.lkf files (under the project directory) are included in the command line options passed to the compiler and DSP/BIOS.

    - Be aware of environment variables (like BIOS_INSTALL_DIR) that could be misleading the command-line build process.

    Hope this helps,

    Rafael