5c571b9af4
This looks a bit weird (two subprofiles become a bit more tightly coupled) but in fact install2 does depend on stage1, and if stage1 doesn't create squashcfg.mk then install2 is just fine with defaults (provided they fit the installer kernel used). A proper mkimage test infrastructure might be handy though. Also there: - 01-initfs: partial cleanup (bootsplash is obsolete anyways) - regarding 03-test-kernel's errorlevel test: if 0, 1 and 2 need to be distinguished, "!" MUST NOT be used as it negates so that 0 becomes 1 and the rest becomes 0
28 lines
776 B
Makefile
28 lines
776 B
Makefile
# step 4: build install2 subprofile (installer "live" part)
|
|
|
|
ifndef GLOBAL_BUILDDIR
|
|
$(error GLOBAL_BUILDDIR not defined)
|
|
endif
|
|
|
|
default: all
|
|
|
|
include $(GLOBAL_BUILDDIR)/distcfg.mk
|
|
include $(GLOBAL_BUILDDIR)/functions.mk
|
|
include $(MKIMAGE_PREFIX)/config.mk
|
|
|
|
# this might have been prepared by ../stage1/scripts.d/03-test-kernel
|
|
-include $(GLOBAL_BUILDDIR)/squashcfg.mk
|
|
|
|
# need kernel modules only (which require corresponding kernel-image);
|
|
# these go into work chroot; NB: no vmlinuz there
|
|
IMAGE_PACKAGES_REGEXP = $(call kpackages,$(INSTALLER_KMODULES),$(INSTALLER_KFLAVOUR))
|
|
IMAGE_PACKAGES = $(COMMON_PACKAGES) \
|
|
$(INSTALL2_PACKAGES) \
|
|
./packages
|
|
|
|
MKI_PACK_RESULTS = squash:altinst
|
|
|
|
include $(MKIMAGE_PREFIX)/targets.mk
|
|
|
|
all: | build-image run-image-scripts pack-image
|