Norman Feske 9651974448 Add stdcxx-4.6.1 to libports, fix #339
This patch adds libstdc++ to libports. With the previous version of the
stdcxx library, the build system used the C++ standard library that
comes with the compiler. This mechanism was prone to inconsistencies of
types defined in the header files used at compile time of the tool chain
and the types provided by our libc. By building the C++ standard library
as part of the Genode build process, such inconsistencies cannot happen
anymore.

Note that the patch changes the meaning of the 'stdcxx' library for
users that happened to rely on 'stdcxx' for hybrid Linux/Genode
applications. For such uses, the original mechanism is still available,
in the renamed form of 'toolchain_stdcxx'.
2012-09-04 12:37:56 +02:00
..
2011-12-22 16:19:25 +01:00
2011-12-22 16:19:25 +01:00
2011-12-22 16:19:25 +01:00
2011-12-22 16:19:25 +01:00
2012-07-16 14:54:19 +02:00
2011-12-22 16:19:25 +01:00
2011-12-22 16:19:25 +01:00
2011-12-22 16:19:25 +01:00
2011-12-22 16:19:25 +01:00
2011-12-22 16:19:25 +01:00
2011-12-22 16:19:25 +01:00
2011-12-22 16:19:25 +01:00
2011-12-22 16:19:25 +01:00
2011-12-22 16:19:25 +01:00
2011-12-22 16:19:25 +01:00
2011-12-22 16:19:25 +01:00
2011-12-22 16:19:25 +01:00

This directory contains library description files.  Each '<libname>.mk' file
holds the instruction for building the library '<libname>'. These makefiles are
never used directly but they are called from the build system when required.
When called, the build system passes the following variables:

:'BASE_DIR': This is the base directory of the source tree.

Source codes are specified by setting the 'SRC_CC' and 'SRC_C' variables.
The source code locations must be specified via 'vpath'.
A library can include other libraries by setting the 'LIBS'
variable.

Each '<libname>.mk' file must include the 'lib.mk' role file:

! include $(BASE_DIR)/mk/lib.mk

Libraries implementing one and the same library interface may have specific
implementations for different platforms. Such platform-specific '<libname>.mk'
files should be placed into corresponding subdirectories. For example, the
'linux'-specific implementation of the 'server' library resides in the 'linux/'
subdirectory. The build system automatically searches the right '<libname>.mk'
file by evaluating the 'SPECS' configuration variable. If 'SPECS' is set to
'host linux', the build system will look into the directories './', './host',
and './linux'.