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

CCS/LAUNCHXL-CC1310: CCS/LAUNCHXL-CC1310

Peter Kostadinov
Prodigy 230 points
Part Number: LAUNCHXL-CC1310

Tool/software: Code Composer Studio

Hi All,

I'm working with CCS7 and "simplelink_cc13x0_sdk_1_60_00_21". For test purposes I'm trying to create a library project, which should be included in an application project. Library project contains only one simple function, it is compiled without problems and output is "xxx.lib". In order to connect this library to the application project, I'm trying to use approach used in examples from "simplelink_cc13x0_sdk_1_60_00_21", where TI-RTOS is included as "dependent" project to the example projects - Properties/Build/Dependencies... . With this approach, when one project is imported to the workspace, dependency project automatically is imported and building of the project automatically build dependency project. In my test building of both is ok, but when linking starts, there are errors:
#10234-D: unresolved symbols remain
#10010: errors encountered during linking

If I add "xxx.lib" as linked file to the application project, there is no errors, but in this case setting of library project as "dependant" project is not necessary at all.
My question is why this approach work well with ti-rtos examples, but do not in my attempt.

Regards,
Peter

  • 0
    TI__Guru**** 173310 points

    Peter,

    For an ordinary static library project, you would need to add the library xxx.lib to the project or to the linker's --library option for it to be included in the link. Setting the library project as a dependency merely tells CCS to build the dependent project first before building the main project. It does not automatically pull the generated library into the main project. So it is a two-step process.

    For the TI-RTOS project, the dependent project is set up a bit differently. It is a RTSC Configuration project (you can see it under Project Properties->General->Output Type) rather than a regular Static Library. In this case, the files generated by the RTSC configuration project are passed to the main project internally by the tool itself. 

  • 0 in reply to AartiG
    Prodigy 230 points
    Thank you very much!
    Regards,
    Peter