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.

how to get full build system on target device

I want to build apps/utilites on target rootfs (via SDMMC ext3 or nfs filesystem etc.), this is critical for me.

I've downloaded AM335xSDK 05_04_00_00 from http://software-dl.ti.com/dsps/dsps_public_sw/am_bu/sdk/AM335xSDK/latest/index_FDS.html. I found that arm-arago-linux-gnueabi-gcc/-cpp is missed in the target rootfs - tisdk-rootfs-am335x-evm.tar.gz 

only the following files in target rootfs /usr/bin/ (I know that /usr/arm-arago-linux-gnueabi/bin/ has symbolic links of ar  as  ld  nm  objcopy  objdump  ranlib  strip to /usr/bin/arm-arago-linux-gnueabi-*):

arm-arago-linux-gnueabi-addr2line  arm-arago-linux-gnueabi-gprof    arm-arago-linux-gnueabi-objdump  arm-arago-linux-gnueabi-strings
arm-arago-linux-gnueabi-ar         arm-arago-linux-gnueabi-ld       arm-arago-linux-gnueabi-ranlib   arm-arago-linux-gnueabi-strip
arm-arago-linux-gnueabi-as         arm-arago-linux-gnueabi-nm       arm-arago-linux-gnueabi-readelf
arm-arago-linux-gnueabi-c++filt    arm-arago-linux-gnueabi-objcopy  arm-arago-linux-gnueabi-size

How can I get full build system on/for target rootfs? Thank you very much!

  • The cross-compile build system is ok. But I need build system on/for target rootfs too.

    The following files are in <SDK install dir>/linux-devkit/bin/ for cross-compile build system (they are ok):

    --------------------------------------------------------------------------------------------------

    arm-arago-linux-gnueabi-addr2line  arm-arago-linux-gnueabi-ld       libtoolize     qdbusxml2cpp
    arm-arago-linux-gnueabi-ar         arm-arago-linux-gnueabi-nm       lrelease       qdbusxml2cpp4
    arm-arago-linux-gnueabi-as         arm-arago-linux-gnueabi-objcopy  lrelease4      qmake
    arm-arago-linux-gnueabi-c++filt    arm-arago-linux-gnueabi-objdump  lupdate        qmake2
    arm-arago-linux-gnueabi-cpp        arm-arago-linux-gnueabi-ranlib   lupdate4       rcc
    arm-arago-linux-gnueabi-g++        arm-arago-linux-gnueabi-readelf  moc            rcc4
    arm-arago-linux-gnueabi-gcc        arm-arago-linux-gnueabi-run      moc4           signGP
    arm-arago-linux-gnueabi-gccbug     arm-arago-linux-gnueabi-size     opkg-cl        uic
    arm-arago-linux-gnueabi-gcov       arm-arago-linux-gnueabi-strings  opkg-key       uic3
    arm-arago-linux-gnueabi-gdb        arm-arago-linux-gnueabi-strip    pkg-config     uic34
    arm-arago-linux-gnueabi-gdbtui     i686-linux-libtool               qdbuscpp2xml   uic4
    arm-arago-linux-gnueabi-gprof      libtool                          qdbuscpp2xml4  update-alternatives

  • Frisky,

    Unfortunately we do not include an ARM side compiler in the SDK.  If you want an ARM compiler you will need to build it yourself using Arago or Angstrom, or you could try a prebuilt toolchain from the Angstrom package feeds, but you need to be careful about compatibility between the SDK toolchain and the toolchain you build.  You can probably look to the Angstrom distribution for beaglebone to find a target side GCC toolchain.

    Chase

  • Could you please tell me or give me the steps/guide for building target side build system? Considering using Arago or Angstrom, a prebuilt toolchain from the Angstrom package feeds.

    Is http://www.angstrom-distribution.org/toolchains/ a right place?

    Thank you.

  • The toolchains you pointed to above are cross-compile toolchains.  You can try the narcissus tool at http://narcissus.angstrom-distribution.org/ to build an image.  You can also use the Angstrom image for beaglebone since that image has a GCC toolchain already installed.  If you have questions about using these images or tools you should ask on the beagleboard@googlegroups.com mailing list since these are both community tools and distributions.

    Chase

  • Sorry for the late reply. Thank you Chase, I will try.