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.

unable to build rtsv7R4_A_le_n_v3_eabi.lib

i am having a problem trying to build rtsv7R4_A_le_n_v3_eabi.lib using the TI 5.2.1 compiler on a 3352 project. i am using windows 7 64bit

i also tried to build it out of CCS using the mklib with errors on that front

i saw the wiki that explains the troubleshooting portion processors.wiki.ti.com/.../Mklib

here is my path:

C:\ProgramData\Oracle\Java\javapath;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;

here is my build log

5775.buildlog.txt

  • cobsonchael said:
    i saw the wiki that explains the troubleshooting portion processors.wiki.ti.com/.../Mklib

    I presume this means that none of those troubleshooting suggestions were helpful.  Is that correct?

    Thanks and regards,

    -George

  • cobsonchael said:
    i am having a problem trying to build rtsv7R4_A_le_n_v3_eabi.lib using the TI 5.2.1 compiler on a 3352 projec

    The build log shows that the compiler version in use is 5.2.7.

    Based upon the thread Problem with Compiler TI 5.2.7 I think the automatic library generation is broken in TI ARM compiler v5.2.7 for Windows.

    Can you try changing to a different compiler version? 

  • so i switched to the 15.12.3.LTS compiler and it built just fine so it would appear that 5.2.7 just doesn't work

    so now i have to ask: what is the difference between the 15, the 5, and the GNU compilers and which one should i use for my project? i had trouble finding this information

  • I have updated information regarding ...

    Chester Gillon said:
    Based upon the thread Problem with Compiler TI 5.2.7 I think the automatic library generation is broken in TI ARM compiler v5.2.7 for Windows.

    We recently changed the system used to track bugs.  The ID for this issue became CODEGEN-1270.  The system used to display these bugs to customers remains SDOWP, and you can lookup that ID in the SDOWP system just as before.  I can confirm there is a problem with automatic library builds in version 5.2.7.  It is fixed in version 5.2.8, which is not released yet.  In the meantime, there is a workaround for those who have CCS installed on their system.  Add these directories to your system path:

    • path to CCS installation/utils/bin
    • path to CCS installation/utils/cygwin

    The automatic library build process uses executables (like sh and gmake) in these directories to do the job.

    Thanks and regards,

    -George

  • cobsonchael said:
    what is the difference between the 15, the 5, and the GNU compilers and which one should i use for my project?

    For the difference between TI ARM compiler versions, please see this wiki article.  As to the choice between that TI ARM compiler and the GNU ARM compiler, I don't have much guidance to offer.  A common case for using the GNU compiler is that you are porting code from some other system that also built with a GNU compiler.  If it is practical, try them both and see.

    Thanks and regards,

    -George

  • so according to the wiki it seems that i should be using the v15 LTS library since it is a "new" compiler with long term support and the 5.2.1 is considered an "older" compiler. do i have that right?
  • That's mostly correct.  Both the 15.12.x.LTS and 5.2.x series of releases are active, which means any reported bugs are fixed in both of them.  In this sense, they both have long term support.  If you are starting a new project, then choosing the more recent 15.12.x.LTS compiler is likely to prove a better choice in the long run.

    Thanks and regards,

    -George