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

TMS320F28335 and CCSv6.1.1: Runtime support library keeps going back to default

stevenh
Guru 20035 points

Hello,

Once in a while CCSv6.1.1 will decide to change the Runtime support library from rts2800_fpu32.lib (the one I selected) to automatic (libc.a).

What is libc.a and why does CCSv6.1.1 want to change back to the automatic?

Stephen

  • 0
    TI__Guru**** 449991 points
    Hello Stephen,
    libc.a is described in the thread below:
    e2e.ti.com/.../295916

    As for the second question - it shouldn't. But I can see it potentially happening if you change some other project properties. Is that when you see the RTS lib get changed - when you modify some other project property?

    Thanks
    ki
  • 0 in reply to Ki
    Guru 20035 points

    I might of changed some properties.  I can't remember.  What properties would make the runtime library change to automatic?

    What is libc.a?  How is it different from rts2800_fpu32.lib?

    Stephen

  • 0 in reply to stevenh
    TI__Guru**** 449991 points

    stevenh said:
    What properties would make the runtime library change to automatic?

    Changing the Device Variant would definitely reset it to default. But I can't think of any others for now

    stevenh said:
    What is libc.a?  How is it different from rts2800_fpu32.lib?

    In the thread mentioned in my prior post, Archaeologist describes it as:

    It is an "index" library.  If you link against it instead of rts<whatever>.lib, the linker will automatically figure out the most appropriate version of the RTS library to use.


    ...

    There is no source code for libc.a; it is generated from other libraries.  It relies on build attribute checking in the linker.  The documentation for libc.a has been sourced, and should be in the compiler user's guide.  Yes, this is intended to work with any set of otherwise-identical libraries which have distinct sets of build attributes.  The linker will only pick one library from each index file. 

    Thanks

    ki