stepchenkoas/mkimage-profiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
59c2169950
mkimage-profiles/main.mk

106 lines
3.2 KiB
Makefile
Raw Normal View History

main.mk introduced, lib/*.mk partially rewritten The former toplevel Makefile is now toplevel main.mk; this change allows for multi-target, multi-arch processing in the current toplevel Makefile. As the "build" symlink semantics change quite considerably when one is doing bulk builds (several pruned builddirs might be useful for comparison), BUILDDIR is now much more likely to be recreated: the cases when it will persist are when it's either a single-image build or when the prefix hasn't changed. There are some more or less subtle bugfixes and enhancements all over the map as well. Done within 20111230..20120102 timeframe, actually...
2011-12-30 14:46:58 +04:00
# steps to build an image:
# --- here
# 1. initialize new profile (BUILDDIR) as a copy of image.in/
# 2. configure distro
# 3. copy the needed bits from metaprofile to a new profile
# --- in BUILDDIR
# 4. build subprofiles and subsequently an image
# deal with one target at a time
IMAGE_TARGET := $(firstword $(MAKECMDGOALS))# ve/generic.tar.gz
ifeq (./,$(dir $(IMAGE_TARGET)))# convenience fallback
IMAGE_TARGET := distro/$(IMAGE_TARGET)# for omitted "distro/"
main.mk: bail out if no image type was specified e.g., `make distro/icewm' instead of `make distro/icewm.iso' would be "successful" as there's a corresponding target indeed but the "success" would just mean building the configuration without running the actual build. Thanks cas@ for hitting this issue and reporting it. PS: note that the initial flagless implementation turned out to produce false positives for e.g. `make distclean'.
2015-04-02 21:02:51 +03:00
IMAGE_GUESS := 1
else
IMAGE_GUESS :=
main.mk introduced, lib/*.mk partially rewritten The former toplevel Makefile is now toplevel main.mk; this change allows for multi-target, multi-arch processing in the current toplevel Makefile. As the "build" symlink semantics change quite considerably when one is doing bulk builds (several pruned builddirs might be useful for comparison), BUILDDIR is now much more likely to be recreated: the cases when it will persist are when it's either a single-image build or when the prefix hasn't changed. There are some more or less subtle bugfixes and enhancements all over the map as well. Done within 20111230..20120102 timeframe, actually...
2011-12-30 14:46:58 +04:00
endif
IMAGE_CONF := $(firstword $(subst ., ,$(IMAGE_TARGET)))# ve/generic
IMAGE_CLASS := $(firstword $(subst /, ,$(IMAGE_TARGET)))# ve
IMAGE_FILE := $(lastword $(subst /, ,$(IMAGE_TARGET)))# generic.tar.gz
Set variable BRANCH, if not defined or empty; show $BRANCH So much clearer and easier. Thanks glebfm@ for the idea.
2022-11-25 14:59:47 +03:00
ifneq (sisyphus,$(BRANCH))
main.mk, mixin.mk, doc: add parametr BRANCH The BRANCH parameter indicates that the target is a starterkit and not a regular build for Sisyphus.
2021-05-30 18:49:00 +03:00
IMAGE_FILE := $(subst regular,alt-$(BRANCH),$(IMAGE_FILE))
endif
main.mk introduced, lib/*.mk partially rewritten The former toplevel Makefile is now toplevel main.mk; this change allows for multi-target, multi-arch processing in the current toplevel Makefile. As the "build" symlink semantics change quite considerably when one is doing bulk builds (several pruned builddirs might be useful for comparison), BUILDDIR is now much more likely to be recreated: the cases when it will persist are when it's either a single-image build or when the prefix hasn't changed. There are some more or less subtle bugfixes and enhancements all over the map as well. Done within 20111230..20120102 timeframe, actually...
2011-12-30 14:46:58 +04:00
IMAGE_NAME := $(firstword $(subst ., ,$(IMAGE_FILE)))# generic
IMAGE_TYPE := $(subst $(IMAGE_NAME).,,$(IMAGE_FILE))# tar.gz
main.mk: bail out if no image type was specified e.g., `make distro/icewm' instead of `make distro/icewm.iso' would be "successful" as there's a corresponding target indeed but the "success" would just mean building the configuration without running the actual build. Thanks cas@ for hitting this issue and reporting it. PS: note that the initial flagless implementation turned out to produce false positives for e.g. `make distclean'.
2015-04-02 21:02:51 +03:00
ifeq ($(IMAGE_NAME),$(IMAGE_TYPE)$(IMAGE_GUESS))
main.mk: fix the help-related glitch `make help/distro' would yield a needless complaint that's been suppressed for `make help' already... Fixes: f147927522411ba92e9af706dc27f95e7c304812
2015-06-03 13:25:45 +03:00
ifneq (help,$(IMAGE_CLASS))
main.mk: bail out if no image type was specified e.g., `make distro/icewm' instead of `make distro/icewm.iso' would be "successful" as there's a corresponding target indeed but the "success" would just mean building the configuration without running the actual build. Thanks cas@ for hitting this issue and reporting it. PS: note that the initial flagless implementation turned out to produce false positives for e.g. `make distclean'.
2015-04-02 21:02:51 +03:00
$(warning no image type/extension specified, run make help?)
endif
main.mk: fix the help-related glitch `make help/distro' would yield a needless complaint that's been suppressed for `make help' already... Fixes: f147927522411ba92e9af706dc27f95e7c304812
2015-06-03 13:25:45 +03:00
endif
main.mk introduced, lib/*.mk partially rewritten The former toplevel Makefile is now toplevel main.mk; this change allows for multi-target, multi-arch processing in the current toplevel Makefile. As the "build" symlink semantics change quite considerably when one is doing bulk builds (several pruned builddirs might be useful for comparison), BUILDDIR is now much more likely to be recreated: the cases when it will persist are when it's either a single-image build or when the prefix hasn't changed. There are some more or less subtle bugfixes and enhancements all over the map as well. Done within 20111230..20120102 timeframe, actually...
2011-12-30 14:46:58 +04:00
# readjustable
ifeq (1,$(NUM_TARGETS))
BUILDDIR_PREFIX ?= mkimage-profiles.build
else
BUILDDIR_PREFIX ?= mkimage-profiles.build/$(IMAGE_CONF).$(ARCH)
endif
build-vm: standalone build is a must, too The problem was spotted by Alexander Bandura: bin/tar2vm wasn't present in the generated profile. I considered extending features.in/Makefile to include bin/ alongside lib/ but that would make the helper's location unpredictable (unless BUILDDIR is specified explicitly) so restricting sudoers would be harder; worse yet, the copied file would come with write access for the user building an image. The implications in restricted case are complex enough anyways so the recommended implementation would only include a fixed readonly location like /usr/share/mkimage-profiles/bin/tar2vm as laid out in doc/vm.txt, and that means it's in the metaprofile not a generated profile.
2012-07-18 17:06:15 +04:00
export MKIMAGE_PROFILES := $(realpath $(dir $(lastword $(MAKEFILE_LIST))))
main.mk introduced, lib/*.mk partially rewritten The former toplevel Makefile is now toplevel main.mk; this change allows for multi-target, multi-arch processing in the current toplevel Makefile. As the "build" symlink semantics change quite considerably when one is doing bulk builds (several pruned builddirs might be useful for comparison), BUILDDIR is now much more likely to be recreated: the cases when it will persist are when it's either a single-image build or when the prefix hasn't changed. There are some more or less subtle bugfixes and enhancements all over the map as well. Done within 20111230..20120102 timeframe, actually...
2011-12-30 14:46:58 +04:00
# preferences
-include $(HOME)/.mkimage/profiles.mk
# most of the actual work done elsewhere
make-3.82 adaptation The issue actually hit image.in/Makefile: "metadata" target in features.in/metadata/lib/50-metadata.mk wasn't reached even if features.in/build-distro/lib/90-build-distro.mk would ACK that the "whatever" actions included "metadata"; thus Metadata/pkg-groups.tar wasn't created and the installer silently failed to install the .base system. Let's armour the rest of the cases where the order of inclusion might be important as well.
2012-10-10 17:18:32 +04:00
include $(sort $(wildcard lib/*.mk))
main.mk introduced, lib/*.mk partially rewritten The former toplevel Makefile is now toplevel main.mk; this change allows for multi-target, multi-arch processing in the current toplevel Makefile. As the "build" symlink semantics change quite considerably when one is doing bulk builds (several pruned builddirs might be useful for comparison), BUILDDIR is now much more likely to be recreated: the cases when it will persist are when it's either a single-image build or when the prefix hasn't changed. There are some more or less subtle bugfixes and enhancements all over the map as well. Done within 20111230..20120102 timeframe, actually...
2011-12-30 14:46:58 +04:00
include conf.d/*.mk
include features.in/*/config.mk
ensure that IMAGEDIR exists (thus globbable) It appears that manually specified IMAGEDIR, e.g. by adding IMAGEDIR = ~/out/$(shell date +%Y%m%d) to ~/.mkimage/profiles.mk, might be problematic due to missing globbing. Let's make sure the paths are globbed and directories are created -- since make's wildcard() returns an empty string when there's nothing there [yet].
2013-02-04 19:18:06 +04:00
# ensure the outdir is created and globbable
check conditions of make for equality of variables with an empty value check conditions of make for equality of variables with an empty value instead of check definition. A defined but empty variable under all these conditions results errors.
2022-11-23 08:39:50 +03:00
ifneq (,$(IMAGEDIR))
ensure that IMAGEDIR exists (thus globbable) It appears that manually specified IMAGEDIR, e.g. by adding IMAGEDIR = ~/out/$(shell date +%Y%m%d) to ~/.mkimage/profiles.mk, might be problematic due to missing globbing. Let's make sure the paths are globbed and directories are created -- since make's wildcard() returns an empty string when there's nothing there [yet].
2013-02-04 19:18:06 +04:00
$(shell mkdir -p $(IMAGEDIR))
IMAGEDIR := $(wildcard $(IMAGEDIR))
endif
main.mk: target refactoring The issue with the original hasty code that stuck around was that it bluntly ignored any ifdef/ifeq constructs due to an obvious reason of being essentially a grep, not a makefile interpreter. It's now fixed so that e.g. arch-specific targets won't pop up for no good reason. Thanks ldv@ for discussion and a reminder about the dump mode (make -p).
2013-06-19 19:57:30 +04:00
# conf.d/*.mk can expose parts conditionally (e.g. DEBUG-only bits)
targets = $(shell \
for i in conf.d/*.mk; do \
make IMAGE_CLASS=$(1) -s -r -p -f $$i 2>/dev/null; \
done \
| sed -rn 's,^($(1)/[^.:]+):.*,\1,p' \
| sort -u)
DISTRO_TARGETS := $(call targets,distro)
VE_TARGETS := $(call targets,ve)
VM_TARGETS := $(call targets,vm)
main.mk introduced, lib/*.mk partially rewritten The former toplevel Makefile is now toplevel main.mk; this change allows for multi-target, multi-arch processing in the current toplevel Makefile. As the "build" symlink semantics change quite considerably when one is doing bulk builds (several pruned builddirs might be useful for comparison), BUILDDIR is now much more likely to be recreated: the cases when it will persist are when it's either a single-image build or when the prefix hasn't changed. There are some more or less subtle bugfixes and enhancements all over the map as well. Done within 20111230..20120102 timeframe, actually...
2011-12-30 14:46:58 +04:00
DISTROS := $(call addsuffices,$(DISTRO_EXTS),$(DISTRO_TARGETS))
VES := $(call addsuffices,$(VE_EXTS),$(VE_TARGETS))
main.mk: Added vm/, ve/ targets into everything target For check all targets.
2020-08-27 19:39:54 +03:00
VES_TAR := $(call addsuffices,.tar,$(VE_TARGETS))
build-vm, main.mk, pack: add recovery.tar recovery.tar needed for tavolga (mipsel). This commit is the result of transferring the required functionality from build-mr (mipsel rootfs). This change uses external tool to build Tavolga-compatible recovery.tar. This simplifies the logic and avoids having recovery workdir in the profile. After this change, m-p will require tavolga-image-tools >= 3.0.
2019-05-19 12:39:04 +03:00
VMS := $(call addsuffices,$(VM_EXTS),$(VM_TARGETS)) \
main.mk, p9.mk, regular-vm.mk: Board name should be a suffix of image name This is consistent with other architectures.
2020-09-07 13:50:56 +03:00
$(call addsuffices,$(VM_TAVOLGA_EXTS), $(filter vm/%-tavolga, $(VM_TARGETS)))
main.mk: Added vm/, ve/ targets into everything target For check all targets.
2020-08-27 19:39:54 +03:00
VMS_IMG := $(call addsuffices,.img,$(VM_TARGETS))
initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration
2012-06-18 22:00:32 +04:00
IMAGES := $(DISTROS) $(VES) $(VMS)
main.mk introduced, lib/*.mk partially rewritten The former toplevel Makefile is now toplevel main.mk; this change allows for multi-target, multi-arch processing in the current toplevel Makefile. As the "build" symlink semantics change quite considerably when one is doing bulk builds (several pruned builddirs might be useful for comparison), BUILDDIR is now much more likely to be recreated: the cases when it will persist are when it's either a single-image build or when the prefix hasn't changed. There are some more or less subtle bugfixes and enhancements all over the map as well. Done within 20111230..20120102 timeframe, actually...
2011-12-30 14:46:58 +04:00
initial build-vm feature Yes, mkimage-profiles is now able to build VM disk images. So far the support is pretty basic: - a single hard drive image with a single partition/FS - only stock root password is configurable - LILO is hardwired as a bootloader The resulting images tend to boot under qemu/kvm though. Please see doc/vm.txt for the warning regarding additional privileges and setup required. This was started back in February but I still hoped to avoid sudo/privileged helper (and libguestfs is almost as undistributable as can be)... Thanks: - http://blog.quinthar.com/2008/07/building-1gb-bootable-qemu-image-using.html - Alexey Morarash who reworked that as https://github.com/tuxofil/linsygen - led@, legion@, vitty@, aen@ for providing advice and inspiration
2012-06-18 22:00:32 +04:00
.PHONY: $(IMAGES) $(DISTRO_TARGETS) $(VE_TARGETS) $(VM_TARGETS)
main.mk introduced, lib/*.mk partially rewritten The former toplevel Makefile is now toplevel main.mk; this change allows for multi-target, multi-arch processing in the current toplevel Makefile. As the "build" symlink semantics change quite considerably when one is doing bulk builds (several pruned builddirs might be useful for comparison), BUILDDIR is now much more likely to be recreated: the cases when it will persist are when it's either a single-image build or when the prefix hasn't changed. There are some more or less subtle bugfixes and enhancements all over the map as well. Done within 20111230..20120102 timeframe, actually...
2011-12-30 14:46:58 +04:00
.PHONY: debug everything help space
main.mk, build.mk: tweaks for error reporting I've finally moved away from LC_MESSAGES=C on my main development system half a year ago and finally spotted that a grep for "Stop\.$" stopped to yield anything now.
2013-06-15 15:40:15 +04:00
# grepping for localized error messages is not trivial
export LC_MESSAGES=C
main.mk introduced, lib/*.mk partially rewritten The former toplevel Makefile is now toplevel main.mk; this change allows for multi-target, multi-arch processing in the current toplevel Makefile. As the "build" symlink semantics change quite considerably when one is doing bulk builds (several pruned builddirs might be useful for comparison), BUILDDIR is now much more likely to be recreated: the cases when it will persist are when it's either a single-image build or when the prefix hasn't changed. There are some more or less subtle bugfixes and enhancements all over the map as well. Done within 20111230..20120102 timeframe, actually...
2011-12-30 14:46:58 +04:00
### duplicate but still needed
everything:
main.mk: Added vm/, ve/ targets into everything target For check all targets.
2020-08-27 19:39:54 +03:00
@n=1; sum=$(words $(DISTROS) $(VES_TAR) $(VMS_IMG)); \
for distro in $(DISTROS) $(VES_TAR) $(VMS_IMG); do \
main.mk introduced, lib/*.mk partially rewritten The former toplevel Makefile is now toplevel main.mk; this change allows for multi-target, multi-arch processing in the current toplevel Makefile. As the "build" symlink semantics change quite considerably when one is doing bulk builds (several pruned builddirs might be useful for comparison), BUILDDIR is now much more likely to be recreated: the cases when it will persist are when it's either a single-image build or when the prefix hasn't changed. There are some more or less subtle bugfixes and enhancements all over the map as well. Done within 20111230..20120102 timeframe, actually...
2011-12-30 14:46:58 +04:00
echo "** building $$distro [$$n/$$sum]:"; \
fix toplevel arch/distro loops There was a somewhat subtle Makefile->main.mk rename leftover lurking in "everything" target: the default Makefile got used, not the supposed main.mk -- which resulted in an attempt to get way too much job done (the number of builds per target became $ARCH squared, not just $ARCH). Huge thanks to led@ for being an inspiring pedantic!
2012-01-17 00:32:54 +04:00
$(MAKE) -f main.mk --no-print-directory $$distro; \
[ "$$n" -lt "$$sum" ] && echo; \
main.mk introduced, lib/*.mk partially rewritten The former toplevel Makefile is now toplevel main.mk; this change allows for multi-target, multi-arch processing in the current toplevel Makefile. As the "build" symlink semantics change quite considerably when one is doing bulk builds (several pruned builddirs might be useful for comparison), BUILDDIR is now much more likely to be recreated: the cases when it will persist are when it's either a single-image build or when the prefix hasn't changed. There are some more or less subtle bugfixes and enhancements all over the map as well. Done within 20111230..20120102 timeframe, actually...
2011-12-30 14:46:58 +04:00
n=$$(($$n+1)); \
done
# config/with/ve/generic config/like/ve config/name/generic config/pack/tar.gz
$(IMAGES): debug \
config/with/$(IMAGE_CONF) \
config/like/$(IMAGE_CLASS) \
config/name/$(IMAGE_NAME) \
config/pack/$(IMAGE_TYPE) \
build; @:
# convenience shortcut
main.mk: factored out help targets These are better off in their own lib/help.mk
2012-03-19 15:23:58 +04:00
$(DISTROS:distro/%=%): %: distro/%; @:
main.mk introduced, lib/*.mk partially rewritten The former toplevel Makefile is now toplevel main.mk; this change allows for multi-target, multi-arch processing in the current toplevel Makefile. As the "build" symlink semantics change quite considerably when one is doing bulk builds (several pruned builddirs might be useful for comparison), BUILDDIR is now much more likely to be recreated: the cases when it will persist are when it's either a single-image build or when the prefix hasn't changed. There are some more or less subtle bugfixes and enhancements all over the map as well. Done within 20111230..20120102 timeframe, actually...
2011-12-30 14:46:58 +04:00
image.in, main.mk: align debug targets Weird but the last round of image builds on e2k started complaining: Makefile:95: *** target file `debug' has both : and :: entries. Stop. Looks like these should have been fixed indeed. But why didn't this surface before then?
2017-08-07 21:49:47 +03:00
debug::
main.mk introduced, lib/*.mk partially rewritten The former toplevel Makefile is now toplevel main.mk; this change allows for multi-target, multi-arch processing in the current toplevel Makefile. As the "build" symlink semantics change quite considerably when one is doing bulk builds (several pruned builddirs might be useful for comparison), BUILDDIR is now much more likely to be recreated: the cases when it will persist are when it's either a single-image build or when the prefix hasn't changed. There are some more or less subtle bugfixes and enhancements all over the map as well. Done within 20111230..20120102 timeframe, actually...
2011-12-30 14:46:58 +04:00
ifeq (2,$(DEBUG))
@$(foreach v,\
$(filter IMAGE_%,$(sort $(.VARIABLES))),\
$(warning $v = $($v)))
endif
Reference in New Issue Copy Permalink