How-to Build New Applications
Checkout top level release
directory and cd to it. This contains the Makefile infrastructure:
cvs co -d <mydir> release cd <mydir>
Checkout the appropriate projects:
cvs co rce cvs co rceusr cvs co rceapp
The ideas behind these three projects are as follows:
- rce project provides common infrastructure that should be re-usable for all software that runs on the RCE. It is like a C++ extension of the RTEMS BSP (e.g. network, thread wrappers, ethernet/PGP PIC drivers).
- rceusr is higher level code that can be reused (e.g. libraries to support a console application, or a particular use of PGP).
- rceapp is the highest level executables.
Edit projects.mk
according to your needs (this is the list of projects to build)
Build one or more of the available targets, eg:
gmake ppc-rtems-rce405 gmake i386-linux
You may append -opt
to the architecture name for building with optimization and/or -dbg
for building with the debugging information. For example the following commands specify valid targets:
gmake i386-linux-opt gmake i386-linux-dbg gmake i386-linux-opt-dbg
These commands can be issued at the top level to build the specified architecture for all projects in the release, at the project level to build all packages for that project or at the package level to build one package only. Note that:
gmake rceapp.console.ppc-rtems-rce405
and
cd rceapp/console gmake ppc-rtems-rce405
are equivalent.
Note that we use shared libraries on Linux, but with the much-improved-but-not-perfect $ORIGIN approach for locating shared libraries, so there is no more LD_LIBRARY_PATH or RPATH to worry about.