nordic-dev.net/nix
nordic-dev.net/nix
2
0
Fork 0
mirror of https://github.com/NixOS/nix.git synced 2024-11-22 06:42:28 +00:00
Code Issues Packages Projects Releases Wiki Activity
mergify/bp/2.24-maintenance/pr-11729
nix/mk/lib.mk

160 lines
4.1 KiB
Makefile
Raw Permalink Normal View History

Initial commit (imported from the Nix repo)
2013-12-10 14:54:34 +00:00
default: all
# Get rid of default suffixes. FIXME: is this a good idea?
.SUFFIXES:
# Initialise some variables.
Make variable names more regular
2014-02-01 11:20:06 +00:00
bin-scripts :=
noinst-scripts :=
Add support for installing man-pages
2014-01-31 14:33:12 +00:00
man-pages :=
Make variable names more regular
2014-02-01 11:20:06 +00:00
install-tests :=
Introduce notion of a test group, use for CA tests Grouping our tests should make it easier to understand the intent than one long poorly-arranged list. It also is convenient for running just the tests for a specific component when working on that component. We need at least one test group so this isn't dead code; I decided to collect the tests for the `ca-derivations` and `dynamic-derivations` experimental features in groups. Do ```bash make ca.test-group -jN ``` and ```bash make dyn-drv.test-group -jN ``` to try running just them. I originally did this as part of #8397 for being able to just the local overlay store alone. I am PRing it separately now so we can separate general infra from new features. Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
2023-07-10 02:24:51 +00:00
install-tests-groups :=
Initial commit (imported from the Nix repo)
2013-12-10 14:54:34 +00:00
Build Windows DLLs with `-Wl,--export-all-symbols` This is not the most elegant, but will match the SOs in exporting everything for now. Later we can refine what is public/private to clean up the interface.
2024-01-09 17:41:42 +00:00
include mk/platform.mk
Initial commit (imported from the Nix repo)
2013-12-10 14:54:34 +00:00
Improved support for building JARs
2014-09-11 13:28:30 +00:00
# Hack to define a literal space.
space :=
space +=
Support specifying a JAR manifest
2014-09-11 13:47:31 +00:00
# Hack to define a literal newline.
define newline
endef
Initial commit (imported from the Nix repo)
2013-12-10 14:54:34 +00:00
# Pass -fPIC if we're building dynamic libraries.
Set default installation paths
2013-12-17 11:13:48 +00:00
BUILD_SHARED_LIBS ?= 1
Initial commit (imported from the Nix repo)
2013-12-10 14:54:34 +00:00
ifeq ($(BUILD_SHARED_LIBS), 1)
Apply OS checks to host platform, not build Previously, the build system used uname(1) output when it wanted to check the operating system it was being built for, which meant that it didn't take into-account cross-compilation when the build and host operating systems were different. To fix this, instead of consulting uname output, we consult the host triple, specifically the third "kernel" part. For "kernel"s with stable ABIs, like Linux or Cygwin, we can use a simple ifeq to test whether we're compiling for that system, but for other platforms, like Darwin, FreeBSD, or Solaris, we have to use a more complicated check to take into account the version numbers at the end of the "kernel"s. I couldn't find a way to just strip these version numbers in GNU Make without shelling out, which would be even more ugly IMO. Because these checks differ between kernels, and the patsubst ones are quite fiddly, I've added variables for each host OS we might want to check to make them easier to reuse.
2021-06-01 07:58:21 +00:00
ifdef HOST_CYGWIN
set _GNU_SOURCE on cygwin this is needed for pipe2()
2017-04-21 14:27:27 +00:00
GLOBAL_CFLAGS += -U__STRICT_ANSI__ -D_GNU_SOURCE
GLOBAL_CXXFLAGS += -U__STRICT_ANSI__ -D_GNU_SOURCE
Set custom compiler flags on Cygwin
2014-12-09 11:20:27 +00:00
else
GLOBAL_CFLAGS += -fPIC
GLOBAL_CXXFLAGS += -fPIC
endif
Apply OS checks to host platform, not build Previously, the build system used uname(1) output when it wanted to check the operating system it was being built for, which meant that it didn't take into-account cross-compilation when the build and host operating systems were different. To fix this, instead of consulting uname output, we consult the host triple, specifically the third "kernel" part. For "kernel"s with stable ABIs, like Linux or Cygwin, we can use a simple ifeq to test whether we're compiling for that system, but for other platforms, like Darwin, FreeBSD, or Solaris, we have to use a more complicated check to take into account the version numbers at the end of the "kernel"s. I couldn't find a way to just strip these version numbers in GNU Make without shelling out, which would be even more ugly IMO. Because these checks differ between kernels, and the patsubst ones are quite fiddly, I've added variables for each host OS we might want to check to make them easier to reuse.
2021-06-01 07:58:21 +00:00
ifndef HOST_DARWIN
ifndef HOST_SOLARIS
ifndef HOST_FREEBSD
Don't pass "--no-copy-dt-needed-entries" option to linker on FreeBSD. Eventually the nested if statements should be replaced by a more general condition, but this is sufficient to make it work on FreeBSD.
2015-10-02 12:19:00 +00:00
GLOBAL_LDFLAGS += -Wl,--no-copy-dt-needed-entries
endif
Support Illumos From https://github.com/NixOS/nix/pull/236
2014-04-03 15:35:16 +00:00
endif
Add support for building shared libraries on Mac OS X
2014-01-09 21:14:34 +00:00
endif
Add support for making relocatable packages using $ORIGIN
2014-03-03 14:19:04 +00:00
SET_RPATH_TO_LIBS ?= 1
Initial commit (imported from the Nix repo)
2013-12-10 14:54:34 +00:00
endif
# Pass -g if we want debug info.
Set default installation paths
2013-12-17 11:13:48 +00:00
BUILD_DEBUG ?= 1
Initial commit (imported from the Nix repo)
2013-12-10 14:54:34 +00:00
ifeq ($(BUILD_DEBUG), 1)
GLOBAL_CFLAGS += -g
GLOBAL_CXXFLAGS += -g
endif
Use `buildprefix` in a few more places `installcheck` doesn't yet work, but the rest of the build can now happen mostly inside a separate build directory. Progress on #9342 Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
2023-11-25 05:33:21 +00:00
include mk/build-dir.mk
include mk/install-dirs.mk
Change dependency file names from foo.dep to .foo.o.dep
2014-02-01 10:31:25 +00:00
include mk/functions.mk
Nicer Make output E.g. CXX src/nix-log2xml/log2xml.o CC src/bsdiff-4.3/bsdiff.o GEN scripts/nix-channel LD src/libmain/libnixmain.so
2014-01-10 21:31:38 +00:00
include mk/tracing.mk
Initial commit (imported from the Nix repo)
2013-12-10 14:54:34 +00:00
include mk/clean.mk
include mk/install.mk
include mk/libraries.mk
include mk/programs.mk
include mk/patterns.mk
include mk/templates.mk
Dedup some markdown -> C++ big literal stuff in build system This pattern rule was unwisely hidden in `src/libstore/local.mk`. Now it is properly in `mk/` and we reuse it for the profile docs too.
2023-05-15 14:38:11 +00:00
include mk/cxx-big-literal.mk
Initial commit (imported from the Nix repo)
2013-12-10 14:54:34 +00:00
include mk/tests.mk
Create compile-commands.json with Make
2024-03-18 15:57:15 +00:00
include mk/compilation-database.mk
Initial commit (imported from the Nix repo)
2013-12-10 14:54:34 +00:00
# Include all sub-Makefiles.
GNU Make 3.81 compatibility 3.81 doesn't understand the ‘define foo =’ syntax, which was added in 3.82. So use ‘define foo’ instead.
2014-02-04 10:02:49 +00:00
define include-sub-makefile
Get rid of whitespace in $(d)
2013-12-12 10:24:03 +00:00
d := $$(patsubst %/,%,$$(dir $(1)))
Initial commit (imported from the Nix repo)
2013-12-10 14:54:34 +00:00
include $(1)
endef
Use `buildprefix` in a few more places `installcheck` doesn't yet work, but the rest of the build can now happen mostly inside a separate build directory. Progress on #9342 Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
2023-11-25 05:33:21 +00:00
$(foreach mf, $(makefiles), $(eval $(call include-sub-makefile,$(mf))))
Initial commit (imported from the Nix repo)
2013-12-10 14:54:34 +00:00
# Instantiate stuff.
Make variable names more regular
2014-02-01 11:20:06 +00:00
$(foreach lib, $(libraries), $(eval $(call build-library,$(lib))))
$(foreach prog, $(programs), $(eval $(call build-program,$(prog))))
$(foreach script, $(bin-scripts), $(eval $(call install-program-in,$(script),$(bindir))))
$(foreach script, $(bin-scripts), $(eval programs-list += $(script)))
$(foreach script, $(noinst-scripts), $(eval programs-list += $(script)))
$(foreach template, $(template-files), $(eval $(call instantiate-template,$(template))))
Introduce notion of a test group, use for CA tests Grouping our tests should make it easier to understand the intent than one long poorly-arranged list. It also is convenient for running just the tests for a specific component when working on that component. We need at least one test group so this isn't dead code; I decided to collect the tests for the `ca-derivations` and `dynamic-derivations` experimental features in groups. Do ```bash make ca.test-group -jN ``` and ```bash make dyn-drv.test-group -jN ``` to try running just them. I originally did this as part of #8397 for being able to just the local overlay store alone. I am PRing it separately now so we can separate general infra from new features. Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
2023-07-10 02:24:51 +00:00
$(foreach test, $(install-tests), \
tests: simplify initialisation and wiring pararameterisation is not actually needed the way things are currently set up, and it confused me when trying to understand what the code does. all but one test sources vars-and-functions.sh, which nominally only defines variables, but in practice is always coupled with the actual initialisation. while the cleaner way of making this more legible would be to source variables and initialisation separately, this would produce a huge diff. the change requires a few small fixes to keep the tests working: - only create test home directory during initialisation that vars-and-functions.sh wrote to the file system seems not write - fix creation of the test directory due to statefulness, the test home directory was implicitly creating the test root, too. decoupling that made it apparent that this was probably not intentional, and certainly confusing. - only source vars-and-functions.sh if init.sh is not needed there is one test case that only needs a helper function but no initialisation side effects - remove some unnecessary cleanups and split parts of re-used test code there were confusing bits in how initialisation code was repurposed, which break if trying to refactor the outer layers naively...
2024-05-06 13:42:49 +00:00
$(eval $(call run-test,$(test))) \
Introduce notion of a test group, use for CA tests Grouping our tests should make it easier to understand the intent than one long poorly-arranged list. It also is convenient for running just the tests for a specific component when working on that component. We need at least one test group so this isn't dead code; I decided to collect the tests for the `ca-derivations` and `dynamic-derivations` experimental features in groups. Do ```bash make ca.test-group -jN ``` and ```bash make dyn-drv.test-group -jN ``` to try running just them. I originally did this as part of #8397 for being able to just the local overlay store alone. I am PRing it separately now so we can separate general infra from new features. Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
2023-07-10 02:24:51 +00:00
$(eval installcheck: $(test).test))
$(foreach test-group, $(install-tests-groups), \
tests: simplify initialisation and wiring pararameterisation is not actually needed the way things are currently set up, and it confused me when trying to understand what the code does. all but one test sources vars-and-functions.sh, which nominally only defines variables, but in practice is always coupled with the actual initialisation. while the cleaner way of making this more legible would be to source variables and initialisation separately, this would produce a huge diff. the change requires a few small fixes to keep the tests working: - only create test home directory during initialisation that vars-and-functions.sh wrote to the file system seems not write - fix creation of the test directory due to statefulness, the test home directory was implicitly creating the test root, too. decoupling that made it apparent that this was probably not intentional, and certainly confusing. - only source vars-and-functions.sh if init.sh is not needed there is one test case that only needs a helper function but no initialisation side effects - remove some unnecessary cleanups and split parts of re-used test code there were confusing bits in how initialisation code was repurposed, which break if trying to refactor the outer layers naively...
2024-05-06 13:42:49 +00:00
$(eval $(call run-test-group,$(test-group))) \
Introduce notion of a test group, use for CA tests Grouping our tests should make it easier to understand the intent than one long poorly-arranged list. It also is convenient for running just the tests for a specific component when working on that component. We need at least one test group so this isn't dead code; I decided to collect the tests for the `ca-derivations` and `dynamic-derivations` experimental features in groups. Do ```bash make ca.test-group -jN ``` and ```bash make dyn-drv.test-group -jN ``` to try running just them. I originally did this as part of #8397 for being able to just the local overlay store alone. I am PRing it separately now so we can separate general infra from new features. Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
2023-07-10 02:24:51 +00:00
$(eval installcheck: $(test-group).test-group) \
$(foreach test, $($(test-group)-tests), \
tests: simplify initialisation and wiring pararameterisation is not actually needed the way things are currently set up, and it confused me when trying to understand what the code does. all but one test sources vars-and-functions.sh, which nominally only defines variables, but in practice is always coupled with the actual initialisation. while the cleaner way of making this more legible would be to source variables and initialisation separately, this would produce a huge diff. the change requires a few small fixes to keep the tests working: - only create test home directory during initialisation that vars-and-functions.sh wrote to the file system seems not write - fix creation of the test directory due to statefulness, the test home directory was implicitly creating the test root, too. decoupling that made it apparent that this was probably not intentional, and certainly confusing. - only source vars-and-functions.sh if init.sh is not needed there is one test case that only needs a helper function but no initialisation side effects - remove some unnecessary cleanups and split parts of re-used test code there were confusing bits in how initialisation code was repurposed, which break if trying to refactor the outer layers naively...
2024-05-06 13:42:49 +00:00
$(eval $(call run-test,$(test))) \
Introduce notion of a test group, use for CA tests Grouping our tests should make it easier to understand the intent than one long poorly-arranged list. It also is convenient for running just the tests for a specific component when working on that component. We need at least one test group so this isn't dead code; I decided to collect the tests for the `ca-derivations` and `dynamic-derivations` experimental features in groups. Do ```bash make ca.test-group -jN ``` and ```bash make dyn-drv.test-group -jN ``` to try running just them. I originally did this as part of #8397 for being able to just the local overlay store alone. I am PRing it separately now so we can separate general infra from new features. Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
2023-07-10 02:24:51 +00:00
$(eval $(test-group).test-group: $(test).test)))
Create compile-commands.json with Make
2024-03-18 15:57:15 +00:00
# Compilation database.
$(foreach lib, $(libraries), $(eval $(call write-compile-commands,$(lib))))
$(foreach prog, $(programs), $(eval $(call write-compile-commands,$(prog))))
compile_commands.json: $(compile-commands-json-files)
@jq --slurp '.' $^ >$@
Restore manual pages Commit d536c57e878a04f795c1ef8ee3232a47035da2cf inadvertedly broke build and installation of all non-autogenerated manual pages (in particular, all the ones documenting the stable CLI), by moving the definition of the man-pages variable in doc/manual/local.mk after its usage in mk/lib.mk. Move including the former earlier so that the correct order is restored.
2024-02-09 17:56:42 +00:00
# Include makefiles requiring built programs.
$(foreach mf, $(makefiles-late), $(eval $(call include-sub-makefile,$(mf))))
Add support for installing man-pages
2014-01-31 14:33:12 +00:00
$(foreach file, $(man-pages), $(eval $(call install-data-in, $(file), $(mandir)/man$(patsubst .%,%,$(suffix $(file))))))
Initial commit (imported from the Nix repo)
2013-12-10 14:54:34 +00:00
Support adding "make help" text
2014-02-01 10:47:34 +00:00
.PHONY: default all man help
Add support for installing man-pages
2014-01-31 14:33:12 +00:00
Revert "Add support for building JARs from Java sources" This reverts commit 259086de841d155f7951c2cc50f799a4631aa512.
2021-02-26 21:42:51 +00:00
all: $(programs-list) $(libs-list) $(man-pages)
Add support for installing man-pages
2014-01-31 14:33:12 +00:00
man: $(man-pages)
Add 'make help'
2013-12-12 10:27:47 +00:00
help:
@echo "The following targets are available:"
@echo ""
@echo " default: Build default targets"
Add support for installing man-pages
2014-01-31 14:33:12 +00:00
ifdef man-pages
@echo " man: Generate manual pages"
endif
Support adding "make help" text
2014-02-01 10:47:34 +00:00
@$(print-top-help)
Make variable names more regular
2014-02-01 11:20:06 +00:00
ifdef programs-list
Add 'make help'
2013-12-12 10:27:47 +00:00
@echo ""
@echo "The following programs can be built:"
@echo ""
Make variable names more regular
2014-02-01 11:20:06 +00:00
@for i in $(programs-list); do echo " $$i"; done
Add 'make help'
2013-12-12 10:27:47 +00:00
endif
Make variable names more regular
2014-02-01 11:20:06 +00:00
ifdef libs-list
Add 'make help'
2013-12-12 10:27:47 +00:00
@echo ""
@echo "The following libraries can be built:"
@echo ""
Make variable names more regular
2014-02-01 11:20:06 +00:00
@for i in $(libs-list); do echo " $$i"; done
Introduce notion of a test group, use for CA tests Grouping our tests should make it easier to understand the intent than one long poorly-arranged list. It also is convenient for running just the tests for a specific component when working on that component. We need at least one test group so this isn't dead code; I decided to collect the tests for the `ca-derivations` and `dynamic-derivations` experimental features in groups. Do ```bash make ca.test-group -jN ``` and ```bash make dyn-drv.test-group -jN ``` to try running just them. I originally did this as part of #8397 for being able to just the local overlay store alone. I am PRing it separately now so we can separate general infra from new features. Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
2023-07-10 02:24:51 +00:00
endif
ifdef install-tests-groups
@echo ""
@echo "The following groups of functional tests can be run:"
@echo ""
@for i in $(install-tests-groups); do echo " $$i.test-group"; done
@echo ""
@echo "(installcheck includes tests in test groups too.)"
Add support for building JARs from Java sources
2013-12-18 15:40:48 +00:00
endif
Support adding "make help" text
2014-02-01 10:47:34 +00:00
@echo ""
@echo "The following variables control the build:"
@echo ""
@echo " BUILD_SHARED_LIBS ($(BUILD_SHARED_LIBS)): Whether to build shared libraries"
@echo " BUILD_DEBUG ($(BUILD_DEBUG)): Whether to include debug symbols"
@echo " CC ($(CC)): C compiler to be used"
@echo " CFLAGS: Flags for the C compiler"
@echo " CXX ($(CXX)): C++ compiler to be used"
@echo " CXXFLAGS: Flags for the C++ compiler"
mk: add support for CPPFLAGS
2021-02-26 21:48:41 +00:00
@echo " CPPFLAGS: C preprocessor flags, used for both CC and CXX"
Support adding "make help" text
2014-02-01 10:47:34 +00:00
@$(print-var-help)
Reference in New Issue Copy Permalink