• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 1453 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.

Angstrom gcc/g++ and Code Sourcery gcc/g++ difference

RV
Expert 2030 points

From http://narcissus.angstrom-distribution.org/ I set Machine: c6a816x-evm to build a root file system with python, boost-dev, opencv library.

However on the linux x86 ubuntu host side, I am using CodeSourcey cross-complier to develop arm linux applications.

What is the difference between arm-angstrom-linux-gnueabi-g++ and Code Sourcery  arm-none-linux-gnueabi-g++, other than that the Code Sourcery  is a cross compiler and the angstrom compiler is native?

Both are gcc 4.3.3.

Will the C/C++ application binaries cross-complied with arm-none-linux-gnueabi-g++,  work with shared libs built by narcissus [or with native arm-angstrom-linux-gnueabi-g++ compiler], with no compatibility issues?

Can I copy the libs from angstrom filesystem into EZSDK root filesystem?

 

RV

  • 0
    TI__Expert 5450 points

    RV,

    The Angstrom toolchain is the creation of the Angstrom developers and maintainers.  It may or may not be EABI compatible with the CodeSourcery toolchain.  The Angstrom developers strive for EABI compatibility but this combination has not been well tested. The Angstrom toolchain is created by taking base GCC and applying additional patches (from various sources including the Linaro project).  CodeSourcery is made in a similar fashion, but the patch sets may be different resulting in different toolchains.  Another difference can be the additional libraries that are packaged into the toolchain aside from just glibc and the compiler.  For example the Angstrom toolchain ships with Qt and other libraries while the CodeSourcery toolchain does not. 

    Generally I would not recommend mixing and matching toolchains.  So the two main options you have are:


    1.  use the CodeSourcery toolchain and build your own distribution with the additional packages you desire above and beyond the EZSDK

    2.  If you want to use the Angstrom toolchain there are host side toolchains available from Angstrom at http://www.angstrom-distribution.org/toolchains/archive/.  The 2010.4 versions should be gcc 4.3.3 and be compatible with the image you created from Narcissus.  However, these toolchains are not supported by TI just as the Narcissus image is not supported so please use these at your own risk.

    Chase