From 8098203284e6506c0a60ea53154b7396fccf617d Mon Sep 17 00:00:00 2001 From: Tim Gardner Date: Wed, 24 Aug 2011 09:44:01 -0600 Subject: [PATCH] UBUNTU: [Config] Restore prepare-% target It turns out that some tossers like to shortcut the process during development. A common sequence for a quick compile test is to preapre the tree, copy the .config, then perform an in-tree compile. For example, fakeroot debian/rules clean prepare-generic cp debian/build/build-generic/.config . make oldconfig scripts prepare make M=`pwd`/fs/ext4 Signed-off-by: Tim Gardner --- debian/rules.d/2-binary-arch.mk | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/debian/rules.d/2-binary-arch.mk b/debian/rules.d/2-binary-arch.mk index 868f865..c0cf967 100644 --- a/debian/rules.d/2-binary-arch.mk +++ b/debian/rules.d/2-binary-arch.mk @@ -24,6 +24,10 @@ $(stampdir)/stamp-prepare-tree-%: $(commonconfdir)/config.common.$(family) $(arc $(build_cd) $(kmake) $(build_O) -j1 silentoldconfig prepare scripts touch $@ +# Used by developers as a shortcut to prepare a tree for compilation. +prepare-%: $(stampdir)/stamp-prepare-% + @echo Prepared $* for $(arch) + # Do the actual build, including image and modules $(stampdir)/stamp-build-%: target_flavour = $* $(stampdir)/stamp-build-%: $(stampdir)/stamp-prepare-% -- 1.7.10.4