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

CCSv3.3 -> CCSv4 legacy import MAKE fails

SteveM
Prodigy 220 points

We just upgraded to CCSv4 so I am in the process of converting my project. The import function seemed to work well except for minor details such as library and include paths. I think a Debug build should work, but it doesn't. Tconf and pre-build steps work, but gmake chokes on every compiler rule. An example error message is as follows:

C:\Program Files (x86)\Texas Instruments\ccsv4\utils\gmake\gmake: *** No rule to make target `aes.obj', needed by `ApMax6455.out'.

Actually, there is a rule to make that object in subdir.mk. However, I don't think gmake will recognize it due to all of the included path info:

Z:/src/ap2_rel_4.0/dsp/src/Debug/aes.obj: ../aes.cpp $(GEN_SRCS) $(GEN_OPTS)
    @echo 'Building file: $<'
    @echo 'Invoking: C6000 Compiler'
    "C:/Program Files (x86)/Texas Instruments/CGT 7.0.4/bin/cl6x (...)
    @echo 'Finished building: $<'
    @echo ' '

Anyone know what is going on here? My guess is that it is because I didn't move the source files into the workspace. The workspace is local while the source files reside on a file server. Is there some way I can modify rule generation in the makefile?

  • 0
    TI__Guru**** 171074 points

    Hi,

    I just did a test here and I did not have any trouble with both the migration process or the build. I imported a very simple CCS3.3 project from a Z: drive, checked both Keep original location for each project  and Create a subfolder for each Eclipse project (recommended). I send attached the imported project and below follows the build output for you to compare. As you can see, the <subdir.mk> file has the complete file path information for both the target and the dependency.

    What version of CCS are you using? The reason for my question is that a few project migration issues were being fixed in the more recent CCS versions and that may be the case.

    Also, can you open a DOS window and try to build the project from the command prompt? This may rule out any possible issues caused by the IDE.

    As a last resource we would need a simple test case that shows the problem. In the meantime I will keep trying to "break" the import tool.

    Hope this helps,

    Rafael

    Output said:


    **** Build of configuration Debug for project mcbsp1 ****

    C:\CCS_4_2_0_10018\ccsv4\utils\gmake\gmake -k all
    'Building file: Z:/examples/dsk6713/csl/mcbsp/mcbsp1/main_mcbsp1.c'
    'Invoking: Compiler'
    "C:/CCS_4_1_3_00038/ccsv4/tools/compiler/C6000 Code Generation Tools 7.0.4/bin/cl6x" -g -O3 --define="CHIP_6713" --include_path="C:/CCS_4_1_3_00038/ccsv4/tools/compiler/C6000 Code Generation Tools 7.0.4/include" --include_path="C:/CCS_4_2_0_10018/xdais_7_10_00_06/packages/ti/xdais" --include_path="c:/CCSTUD~1.3/C6000/csl/include" --quiet --diag_warning=225 --obj_directory="Z:/examples/dsk6713/csl/mcbsp/mcbsp1/Debug" --preproc_with_compile --preproc_dependency="main_mcbsp1.pp"  "Z:/examples/dsk6713/csl/mcbsp/mcbsp1/main_mcbsp1.c"
    'Finished building: Z:/examples/dsk6713/csl/mcbsp/mcbsp1/main_mcbsp1.c'
    ' '
    'Building target: Z:/examples/dsk6713/csl/mcbsp/mcbsp1/Debug/mcbsp1.out'
    'Invoking: Linker'
    "C:/CCS_4_1_3_00038/ccsv4/tools/compiler/C6000 Code Generation Tools 7.0.4/bin/cl6x" -g -O3 --define="CHIP_6713" --quiet --diag_warning=225 --obj_directory="Z:/examples/dsk6713/csl/mcbsp/mcbsp1/Debug" -z -m"mcbsp1.map" --warn_sections -i"C:/CCS_4_1_3_00038/ccsv4/tools/compiler/C6000 Code Generation Tools 7.0.4/lib" -i"C:/CCS_4_1_3_00038/ccsv4/tools/compiler/C6000 Code Generation Tools 7.0.4/include" -i"Z:/examples/dsk6713/csl/mcbsp/mcbsp1/mcbsp1" -i"Z:/examples/dsk6713/csl/mcbsp/mcbsp1" -i"c:/CCSTUD~1.3/C6000/csl/lib" --reread_libs --rom_model -o "Z:/examples/dsk6713/csl/mcbsp/mcbsp1/Debug/mcbsp1.out"  "Z:/examples/dsk6713/csl/mcbsp/mcbsp1/Debug/main_mcbsp1.obj" -l"csl6713.lib" -l"rts6700.lib" "Z:/examples/dsk6713/csl/mcbsp/mcbsp1/mcbsp1.cmd"
    warning: creating ".stack" section with default size of 0x400; use the -stack
       option to change the default size
    warning: creating ".sysmem" section with default size of 0x400; use the -heap
       option to change the default size
    'Finished building target: Z:/examples/dsk6713/csl/mcbsp/mcbsp1/Debug/mcbsp1.out'
    ' '
    Build complete for project mcbsp1

    mcbsp.zip
  • 0 in reply to desouza
    Prodigy 220 points

    Thanks for the response, Raphael.

    I was at CCS v4.0.1.01001. That was the problem. I've been scanning updates routinely and thought installation of CCS updates were automatically occuring. I didn't realize I needed to "manage" the installation. Now I'm at CCS v4.2.1 and the project builds just fine.

    Regards,

    Steve