genode/base/lib/mk
Genode Labs da4e1feaa5 Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
..
host Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
README Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
allocator_avl.mk Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
avl_tree.mk Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
console.mk Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
cxx.mk Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
elf.mk Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
env.mk Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
heap.mk Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
log_console.mk Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
platform.mk Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
process.mk Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
raw_server.mk Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
raw_signal.mk Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
server.mk Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
signal.mk Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
slab.mk Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
stdcxx.mk Imported Genode release 11.11 2011-12-22 16:19:25 +01:00
thread.mk Imported Genode release 11.11 2011-12-22 16:19:25 +01:00

README

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'.