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

Problem Building Legacy C28xx Library Project with CCS4

Aron
Prodigy 90 points

I've imported a CCS3 project producing a library (*.lib) into CCS 4.0.0.14000 . The legacy import function worked quite fine, however, when building the project ar2000 is invoked with a syntax error in the makefile. The makefile is generated automatically, thus, there seems to be an error in the makefile generator.

The wrong line reads:

"C:/Programme/Texas Instruments/ccsv4/tools/compiler/c2000/bin/ar2000" -r"hal_flash.lib" "hal_flash.lib" $(GEN_CMDS_QUOTED) $(ORDERED_OBJS)

There should be one space between the -r option and the following argument. Another error is that the name of the output file (hal_flash.lib) is listed twice. Running the makefile manually with that line changed to

"C:/Programme/Texas Instruments/ccsv4/tools/compiler/c2000/bin/ar2000" -r "hal_flash.lib" $(GEN_CMDS_QUOTED) $(ORDERED_OBJS)

works.

The problem seems to be related to the settings dialog of the Librarian:

The filed "All options" contains

-r "hal_flash.lib"

which is fine but the space between -r and "hal_flash.lib" doesn't make it to the makefile. And the command line pattern should not list ${output} because this ceates a second instance of "hal_flash.lib" on the command line.

Unfortunately, the "All options" field is read-only. Is there a way to modify the code that is put into the makefile?

 

Thanks,

Aron

  • 0
    TI__Guru**** 169894 points

    Aron,

    Thanks for reporting this. Unfortunately you hit two bugs on the import process and a request for a fix was filed today (reference SDSCM00032318) - usually these are fixed in a (not so distant) future release.

    As far as I know, the first issue has no easy workaround other than re-creating the library project from scratch. The second issue, as you may have noticed, is fixed by removing the ${output} variable from the Command Line Pattern. The final fix, however, will probably keep the ${output} variable and remove the library filename from the ${flags} variable (where -r is placed).

    Thank you again for reporting this issue.

    Best regards,

    Rafael