ExternalVendorCode/genode
1
0
Fork 0
mirror of https://github.com/genodelabs/genode.git synced 2024-12-27 01:11:06 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
240e70d989
genode/repos/base-sel4/lib/mk/core-sel4.inc

55 lines
1.7 KiB
PHP
Raw Normal View History

sel4: explicit vpath for each file in core The pattern rule picked up the wrong platform_services.cc in the depot-archive case only because the archive integrates generic and sel4-specific source files into REP_DIR.
2018-04-18 14:42:08 +00:00
GEN_CORE_DIR = $(dir $(call select_from_repositories,src/core/main.cc))
BASE_REP_DIR = $(GEN_CORE_DIR)/../..
core: unify handling of boot modules Instead of solving the problem to deliver ROM modules to core while booting differently for the several kernels (multi-boot, elfweaver, core re-linking), this commit unifies the approaches. It always builds core as a library, and after all binaries are built from a run-script, the run-tool will link an ELF image out of the core-library and all boot modules. Thereby, core can access its ROM modules directly. This approach now works for all kernels except Linux. With this solution, there is no [build_dir]/bin/core binary available anymore. For debugging purposes you will find a core binary without boot modules, but with debug symbols under [run_dir].core. Fix #2095
2016-09-15 14:08:33 +00:00
sel4: explicit vpath for each file in core The pattern rule picked up the wrong platform_services.cc in the depot-archive case only because the archive integrates generic and sel4-specific source files into REP_DIR.
2018-04-18 14:42:08 +00:00
GEN_SRC_CC += \
core_log.cc \
core_mem_alloc.cc \
core_rpc_cap_alloc.cc \
cpu_session_component.cc \
cpu_session_support.cc \
cpu_thread_component.cc \
dataspace_component.cc \
default_log.cc \
dump_alloc.cc \
io_mem_session_component.cc \
main.cc \
pd_session_component.cc \
pd_session_support.cc \
platform_thread.cc \
ram_dataspace_factory.cc \
region_map_component.cc \
rom_session_component.cc \
signal_receiver.cc \
signal_transmitter_proxy.cc \
trace_session_component.cc
REP_SRC_CC += \
capability_space.cc \
core_log_out.cc \
core_region_map.cc \
io_mem_session_support.cc \
irq_session_component.cc \
pager.cc \
platform.cc \
platform_pd.cc \
platform_thread.cc \
ram_dataspace_support.cc \
rpc_cap_factory.cc \
signal_source_component.cc \
stack_area.cc \
thread_start.cc
SRC_CC += $(GEN_SRC_CC) $(REP_SRC_CC)
Disambiguate kernel-specific file names This patch removes possible ambiguities with respect to the naming of kernel-dependent binaries and libraries. It also removes the use of kernel-specific global side effects from the build system. The reach of kernel-specific peculiarities has thereby become limited to the actual users of the respective 'syscall-<kernel>' libraries. Kernel-specific build artifacts are no longer generated at magic places within the build directory (like okl4's includes, or the L4 build directories of L4/Fiasco and Fiasco.OC, or the build directories of various kernels). Instead, such artifacts have been largely moved to the libcache. E.g., the former '<build-dir>/l4/' build directory for the L4 build system resides at '<build-dir>/var/libcache/syscall-foc/build/'. This way, the location is unique to the kernel. Note that various tools are still generated somewhat arbitrarily under '<build-dir>/tool/' as there is no proper formalism for building host tools yet. As the result of this work, it has become possible to use a joint Genode build directory that is usable with all kernels of a given hardware platform. E.g., on x86_32, one can now seamlessly switch between linux, nova, sel4, okl4, fiasco, foc, and pistachio without rebuilding any components except for core, the kernel, the dynamic linker, and the timer driver. At the current stage, such a build directory must still be created manually. A change of the 'create_builddir' tool will follow to make this feature easily available. This patch also simplifies various 'run/boot_dir' plugins by removing the option for an externally hosted kernel. This option remained unused for many years now. Issue #2190
2016-12-10 00:30:38 +00:00
Generalize ABI mechanism to shared objects This patch make the ABI mechanism available to shared libraries other than Genode's dynamic linker. It thereby allows us to introduce intermediate ABIs at the granularity of shared libraries. This is useful for slow-moving ABIs such as the libc's interface but it will also become handy for the package management. To implement the feature, the build system had to be streamlined a bit. In particular, archive dependencies and shared-lib dependencies are now handled separately, and the global list of 'SHARED_LIBS' is no more. Now, the variable with the same name holds the per-target list of shared libraries used by the target.
2016-12-29 17:27:45 +00:00
LIBS += base-sel4-common syscall-sel4 cxx
core: unify handling of boot modules Instead of solving the problem to deliver ROM modules to core while booting differently for the several kernels (multi-boot, elfweaver, core re-linking), this commit unifies the approaches. It always builds core as a library, and after all binaries are built from a run-script, the run-tool will link an ELF image out of the core-library and all boot modules. Thereby, core can access its ROM modules directly. This approach now works for all kernels except Linux. With this solution, there is no [build_dir]/bin/core binary available anymore. For debugging purposes you will find a core binary without boot modules, but with debug symbols under [run_dir].core. Fix #2095
2016-09-15 14:08:33 +00:00
Disambiguate kernel-specific file names This patch removes possible ambiguities with respect to the naming of kernel-dependent binaries and libraries. It also removes the use of kernel-specific global side effects from the build system. The reach of kernel-specific peculiarities has thereby become limited to the actual users of the respective 'syscall-<kernel>' libraries. Kernel-specific build artifacts are no longer generated at magic places within the build directory (like okl4's includes, or the L4 build directories of L4/Fiasco and Fiasco.OC, or the build directories of various kernels). Instead, such artifacts have been largely moved to the libcache. E.g., the former '<build-dir>/l4/' build directory for the L4 build system resides at '<build-dir>/var/libcache/syscall-foc/build/'. This way, the location is unique to the kernel. Note that various tools are still generated somewhat arbitrarily under '<build-dir>/tool/' as there is no proper formalism for building host tools yet. As the result of this work, it has become possible to use a joint Genode build directory that is usable with all kernels of a given hardware platform. E.g., on x86_32, one can now seamlessly switch between linux, nova, sel4, okl4, fiasco, foc, and pistachio without rebuilding any components except for core, the kernel, the dynamic linker, and the timer driver. At the current stage, such a build directory must still be created manually. A change of the 'create_builddir' tool will follow to make this feature easily available. This patch also simplifies various 'run/boot_dir' plugins by removing the option for an externally hosted kernel. This option remained unused for many years now. Issue #2190
2016-12-10 00:30:38 +00:00
INC_DIR += $(REP_DIR)/src/core/include $(GEN_CORE_DIR)/include \
sel4: explicit vpath for each file in core The pattern rule picked up the wrong platform_services.cc in the depot-archive case only because the archive integrates generic and sel4-specific source files into REP_DIR.
2018-04-18 14:42:08 +00:00
$(REP_DIR)/src/include $(BASE_REP_DIR)/src/include
core: unify handling of boot modules Instead of solving the problem to deliver ROM modules to core while booting differently for the several kernels (multi-boot, elfweaver, core re-linking), this commit unifies the approaches. It always builds core as a library, and after all binaries are built from a run-script, the run-tool will link an ELF image out of the core-library and all boot modules. Thereby, core can access its ROM modules directly. This approach now works for all kernels except Linux. With this solution, there is no [build_dir]/bin/core binary available anymore. For debugging purposes you will find a core binary without boot modules, but with debug symbols under [run_dir].core. Fix #2095
2016-09-15 14:08:33 +00:00
include $(GEN_CORE_DIR)/version.inc
sel4: explicit vpath for each file in core The pattern rule picked up the wrong platform_services.cc in the depot-archive case only because the archive integrates generic and sel4-specific source files into REP_DIR.
2018-04-18 14:42:08 +00:00
_vpath = $(foreach f,$(1),$(eval vpath $(f) $(2)))
Disambiguate kernel-specific file names This patch removes possible ambiguities with respect to the naming of kernel-dependent binaries and libraries. It also removes the use of kernel-specific global side effects from the build system. The reach of kernel-specific peculiarities has thereby become limited to the actual users of the respective 'syscall-<kernel>' libraries. Kernel-specific build artifacts are no longer generated at magic places within the build directory (like okl4's includes, or the L4 build directories of L4/Fiasco and Fiasco.OC, or the build directories of various kernels). Instead, such artifacts have been largely moved to the libcache. E.g., the former '<build-dir>/l4/' build directory for the L4 build system resides at '<build-dir>/var/libcache/syscall-foc/build/'. This way, the location is unique to the kernel. Note that various tools are still generated somewhat arbitrarily under '<build-dir>/tool/' as there is no proper formalism for building host tools yet. As the result of this work, it has become possible to use a joint Genode build directory that is usable with all kernels of a given hardware platform. E.g., on x86_32, one can now seamlessly switch between linux, nova, sel4, okl4, fiasco, foc, and pistachio without rebuilding any components except for core, the kernel, the dynamic linker, and the timer driver. At the current stage, such a build directory must still be created manually. A change of the 'create_builddir' tool will follow to make this feature easily available. This patch also simplifies various 'run/boot_dir' plugins by removing the option for an externally hosted kernel. This option remained unused for many years now. Issue #2190
2016-12-10 00:30:38 +00:00
sel4: explicit vpath for each file in core The pattern rule picked up the wrong platform_services.cc in the depot-archive case only because the archive integrates generic and sel4-specific source files into REP_DIR.
2018-04-18 14:42:08 +00:00
$(call _vpath,$(GEN_SRC_CC),$(GEN_CORE_DIR))
$(call _vpath,$(REP_SRC_CC),$(REP_DIR)/src/core)
Reference in New Issue Copy Permalink