70 April 2014
read arm-linux-gnueabi-g++. We will also have to manually
alter the commands for the GCC C compiler, the GCC
C++ linker, and the GCC assembler as well. I’ve done just
that in Screenshot 6.
Now that the commands are ARMed, the next step is
to make sure the correct ARM includes and ARM libraries
will be accessed during the cross compilation and linking
processes. Note that PC include paths are present in the
project properties window I’ve captured in Screenshot 7.
Our job is to add an include directory path for the
BeagleBone. The path /usr/arm-linux-gnueabi/include will
be added at the top of the list. We will do the same for
ARMed the includes, we do the same for the ARM
libraries. Screenshot 9 holds the directory path entry for
the ARM libraries.
Pulling the Trigger
If we have done everything correctly, clicking on the
; Screenshot 5. There are lots of knobs to twist and buttons to
push here. However, right now we only have to worry about the
compiler, linker, and assembler ARM command strings.
; Screenshot 6. In the end, all we must do is
add the prefix arm-linux-gnueabi- to all of the
compilers, linkers, and assemblers that are
represented in this screen capture. The
assembler command is missing here, however.
It reads as arm-linux-gnueabi-as.
; Screenshot 7. The BeagleBone Black includes are
located in the path /usr/arm-linux-gnueabi/include.
This directory path happens to exist on the ThinkPad.
; Screenshot 8. To use both of the C and C++ ARM cross
compilers, we must perform the same directory pathing
process for each compiler we wish to use. In the case of
C++, the include path is /usr/arm-linux-