ExternalVendorCode/genode
1
0
Fork 0
mirror of https://github.com/genodelabs/genode.git synced 2024-12-25 16:31:06 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
5aee80ee32
genode/repos/base/lib/mk
History
Norman Feske 2cbef82b61 ldso-startup: support build from non-base repos 
By always fetching the source relative to BASE_DIR, we can
include the ldso-startup.mk file from other repositories, i.e.,
API packages.
2016-07-15 11:38:27 +02:00
..
spec ldso: Support for RISC-V 2016-02-26 11:36:51 +01:00
base-common.inc Supplement base/log.h with raw output function 2016-06-22 12:21:42 +02:00
base.inc base: new interface for textual output 2016-05-09 13:25:01 +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 ldso-startup: support build from non-base repos 2016-07-15 11:38:27 +02: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

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