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

The error when I migrate CCS3.3 project for CCS4.0 (C6455)

Renaissance
Intellectual 925 points
Other Parts Discussed in Thread: CCSTUDIO

In the following is the error saved in the migration.log when I migrate CCS3.3 project for CCS4.0 (C6455)

 

!ERROR: Unresolved source file: src/sc/sc2d.h

!CONFIGURATION: 'com.ti.ccstudio.buildDefinitions.C6000.Debug.736263119' [Fri Sep 18 14:37:20 PDT 2009]

 !TOOL: 'com.ti.ccstudio.buildDefinitions.C6000_6.1.exe.linkerDebug.569871090./B_Flow_3/c6455.cmd'

  !WARNING: Unresolved option: com.ti.ccstudio.buildDefinitions.C6000_6.1.exe.linkerDebug.569871090./B_Flow_3/c6455.cmd::-q

in fact, I can see the sc2d.h file is included in the new project. Why is it unresolved?

I do not quite understand the rest of the log file.

can any one give me some hints?

Thank you very much

 

  • 0
    TI__Genius 9345 points

    You can safely ignore both the error and the warning above.

    The error is logged unnecessarily in this case - normally, in CCSv3, only buildable files are qualified as "source files" (i.e. are listed in the [Source Files] block in the PJT file).  Header files aren't considered as "buildable" files, because they aren't directly built by the compiler.  Thus, it is not neccessary to explicitly include header files in a v3 project using the "Add Files to Project..." dialog.  The PJT migration utility should simply ignore such files, and not log the error.  I've opened an internal defect entry to fix this scenario for a future version of CCS (SDSCM00033692 PJT migration: non-buildable source-files cause unneccessary error messages).

    The warning should no longer be printed - it has been fixed as of CCSv4.0 RTM version.  Which version of CCS are you using?

    Does your project build and behave as expected, aside from these migration log entries?

    Thanks,

    - Baltasar.

  • 0 in reply to Baltasar Belyavsky
    Intellectual 925 points

    Thank you, Baltasar.

    Actually, since I failed to get the migrae method working. I choose to create a new project and then added all the source files from my CCS3.3 project. This method works well, except that I have to manually make some configurations using this method. In fact, I have some other issues even I can build my CCS3.3 project in CCS4.0. The issues are related to the running time of the project. Prevously, my project built by CCS3.3 was running much faster than the one built by CCS4.0. Here is a link of the thread in TI forum regarding this issue. I hope you can also give me some suggestion of this issue.

    http://e2e.ti.com/forums/p/10383/40620.aspx#40620

    BTW, here is the CCS information I am using right now. Verion:  4.0.1.01001 CGT 6.1.11

    Thank you,

    Renaissance