• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 363 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.

CCS: default library licenses

user5841294
Expert 1120 points

Tool/software: Code Composer Studio

Hi,

I'm using the CCS 8.2.

What are the licenses of the default - c libraries, for example stdio.h/c? Are that GNU... (Version?) licenses?

/*****************************************************************************/
/* STDIO.H                                                                   */
/*                                                                           */
/* Copyright (c) 1993 Texas Instruments Incorporated                         */

Thanks

  • 0
    TI__Guru**** 161500 points

    I am not sure which device you are using so I can only provide an example of where you can get this information.

    If you are using a device that is ARM based and using the TI ARM compiler that comes with CCS you can get the details on the licensing for each file in the C runtime support library by going to <install dir>/ccsv8/tools/compiler/ti-cgt-arm_18.1.3.LTS

    The details are in the file ARM_RTS_18.1.0.LTS.html

    Regards,

    John

  • 0 in reply to JohnS
    Expert 1120 points
    Hi John,

    thats great.
    I use ti-cgt-arm_18.1.4.LTS, i found the flag --include_path="C:/ti/ccsv8/tools/compiler/ti-cgt-arm_18.1.4.LTS/include".

    Another short question: Is there a file when I compile my project which lists all used librarys? I have to mention all used licenses.
  • 0 in reply to user5841294
    TI__Guru**** 161500 points

    There is a build option that you can use for that.

    In the options below change the top from "Automatic" to "Manual".  Then fill in a file for the preproc_includes option

    This will then generate the file in the build configuration directory.  In my case this was /Debug

    The build stops at this point and does not compete. So you really just want to do this periodically to generate the list and then switch it back to automatic.

    Regards,

    John

  • 0 in reply to JohnS
    Expert 1120 points
    Thank you very much for your great help. Bye