Add KERNFAST define. When defined, it skips all the config, depends

and clean steps.  KERNFAST was selected to complement KERNCONF which
is typically used in these scenarios (especially with cross building).

Reviewed by:	arch@
This commit is contained in:
Warner Losh 2009-01-15 04:19:03 +00:00
parent a9cade51ed
commit 791777753c

View File

@ -5,6 +5,7 @@
# -DNO_CLEANDIR run ${MAKE} clean, instead of ${MAKE} cleandir # -DNO_CLEANDIR run ${MAKE} clean, instead of ${MAKE} cleandir
# -DNO_CLEAN do not clean at all # -DNO_CLEAN do not clean at all
# -DNO_SHARE do not go into share subdir # -DNO_SHARE do not go into share subdir
# -DKERNFAST define NO_KERNELCONFIG, NO_KERNELCLEAN and NO_KERNELCONFIG
# -DNO_KERNELCONFIG do not run config in ${MAKE} buildkernel # -DNO_KERNELCONFIG do not run config in ${MAKE} buildkernel
# -DNO_KERNELCLEAN do not run ${MAKE} clean in ${MAKE} buildkernel # -DNO_KERNELCLEAN do not run ${MAKE} clean in ${MAKE} buildkernel
# -DNO_KERNELDEPEND do not run ${MAKE} depend in ${MAKE} buildkernel # -DNO_KERNELDEPEND do not run ${MAKE} depend in ${MAKE} buildkernel
@ -697,6 +698,11 @@ distrib-dirs distribution:
# be set to cross-build, we have to make sure TARGET is set # be set to cross-build, we have to make sure TARGET is set
# properly. # properly.
.if defined(KERNFAST)
NO_KERNELCLEAN= t
NO_KERNELCONFIG= t
NO_KERNELDEPEND= t
.endif
.if !defined(KERNCONF) && defined(KERNEL) .if !defined(KERNCONF) && defined(KERNEL)
KERNCONF= ${KERNEL} KERNCONF= ${KERNEL}
KERNWARN= KERNWARN=