Chapter 24. Compiler and Linker Options
Prev Part IV.  eCos Programming Concepts and Techniques Next

Chapter 24. Compiler and Linker Options

Table of Contents

24.1. Compiling a C Application
24.2. Compiling a C++ Application

eCos is built using the GNU C and C++ compilers. eCos relies on certain features of these tools such as constructor priority ordering and selective linking which are not part of other toolchains.

Some GCC options are required for eCos, and others can be useful. This chapter gives a brief description of the required options as well as some recommended eCos-specific options. All other GCC options (described in the GCC manuals) are available.

24.1. Compiling a C Application

The following command lines demonstrate the minimum set of options required to compile and link an eCos program written in C.

[Note]Note

Remember that when this manual shows TARGET-gcc you should use the full name of the cross compiler, e.g. i386-elf-gcc, arm-eabi-gcc, or sh-elf-gcc. When compiling for the synthetic Linux target, use the native gcc which must have the features required by eCos.

$ TARGET-gcc -c  -IECOS_INSTALL_DIR/include file.c
$ TARGET-gcc -o program file.o -LECOS_INSTALL_DIR/lib -Ttarget.ld -nostdlib
[Note]Note

Certain targets may require extra options, for example the SPARClite architectures require the option -mcpu=sparclite. Examine the BASE_DIR/examples/Makefile or the “Global compiler flags” option (CYGBLD_GLOBAL_CFLAGS) in your generated eCos configuration) to see if any extra options are required, and if so, what they are.

The following command lines use some other options which are recommended because they use the selective linking feature:

$ TARGET-gcc -c  -IECOS_INSTALL_DIR/include -I. -ffunction-sections -fdata-sections -g \
  -O2 file.c
$ TARGET-gcc -o program file.o -ffunction-sections -fdata-sections -Wl,--gc-sections -g \
  -O2 -LECOS_INSTALL_DIR/lib -Ttarget.ld -nostdlib

24.2. Compiling a C++ Application

The following command lines demonstrate the minimum set of options required to compile and link an eCos program written in C++.

[Note]Note

Remember that when this manual shows TARGET-g++ you should use the full name of the cross compiler, e.g. i386-elf-g++, arm-eabi-g++, or sh-elf-g++. When compiling for the synthetic Linux target, use the native g++ which must have the features required by eCos.

$ TARGET-g++ -c  -IECOS_INSTALL_DIR/include -fno-rtti -fno-exceptions file.cxx
$ TARGET-g++ -o program file.o -LECOS_INSTALL_DIR/lib -Ttarget.ld -nostdlib
[Note]Note

Certain targets may require extra options, for example the SPARClite architectures require the option -mcpu=sparclite. Examine the BASE_DIR/packages/targets file or BASE_DIR/examples/Makefile or the “Global compiler flags” option (CYGBLD_GLOBAL_CFLAGS) in your generated eCos configuration) to see if any extra options are required, and if so, what they are.

The following command lines use some other options which are recommended because they use the selective linking feature:

$ TARGET-g++ -c -IECOS_INSTALL_DIR/include -I. -ffunction-sections -fdata-sections -fno-rtti \
  -fno-exceptions -finit-priority -g -O2 file.cxx
$ TARGET-g++ -o program file.o -W1,--gc-sections -g -O2 -LECOS_INSTALL_DIR/lib \
  -Ttarget.ld -nostdlib
Prev Up Next
Chapter 23. The Component Repository and Working Directories Home Chapter 25. Debugging Techniques