genode/repos/base/lib/mk
Norman Feske 40a5af42eb Clean up base-library structure
This patch moves the base library from src/base to src/lib/base,
flattens the library-internal directory structure, and moves the common
parts of the library-description files to base/lib/mk/base.inc and
base/lib/mk/base-common.inc.

Furthermore, the patch fixes a few cosmetic issues (whitespace and
comments only) that I encountered while browsing the result.

Fixes #1952
2016-05-09 13:24:11 +02:00
..
spec ldso: Support for RISC-V 2016-02-26 11:36:51 +01:00
base-common.inc Clean up base-library structure 2016-05-09 13:24:11 +02:00
base.inc Clean up base-library structure 2016-05-09 13:24:11 +02:00
component_entry_point.mk Move server API concept to base framework 2016-04-11 11:51:46 +02:00
cxx.mk Clean up base-library structure 2016-05-09 13:24:11 +02:00
ldso-startup.mk base: Genode's dynamic linker 2014-11-12 14:44:15 +01:00
ldso.inc ldso: use get_page_size_log2 instead of "12" 2016-04-25 10:48:01 +02:00
platform.mk Move repositories to 'repos/' subdirectory 2014-05-14 16:08:00 +02:00
README Move repositories to 'repos/' subdirectory 2014-05-14 16:08:00 +02:00
startup.inc Move server API concept to base framework 2016-04-11 11:51:46 +02:00
syscall.mk Move repositories to 'repos/' subdirectory 2014-05-14 16:08:00 +02: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'.