NetBSD

Commit Graph

Author	SHA1	Message	Date
pooka	11815d9c1d	Depend ioconf.c on config (if doing a USETOOLS==yes build). While this is not strictly sensible, it keeps UPDATE=1 builds rolling if I change some aspect of config (such as adding the cfdriver/cfattach lists now). This is going away eventually.	2010-03-25 20:37:36 +00:00
pooka	4f4d4d6450	deal with ioconf.h	2010-03-22 14:42:01 +00:00
pooka	40bb87a667	Move make snippets for use with config(1) ioconf functionality from rump into share/mk. This is to make it useful for all kernel builders. Note: we have waaay too many weird and wonderful ways of making kernel code (monolithic kernel, modules, rump). There should be only one way to build kernel code instead of a maze of twisty little .mk files, all not quite alike. When that is fixed, this snippet can go into the more generic .mk file.	2010-03-21 06:55:44 +00:00

Author

SHA1

Message

Date

pooka

11815d9c1d

Depend ioconf.c on config (if doing a USETOOLS==yes build).

While this is not strictly sensible, it keeps UPDATE=1 builds
rolling if I change some aspect of config (such as adding the
cfdriver/cfattach lists now).  This is going away eventually.

2010-03-25 20:37:36 +00:00

pooka

4f4d4d6450

deal with ioconf.h

2010-03-22 14:42:01 +00:00

pooka

40bb87a667

Move make snippets for use with config(1) ioconf functionality from

rump into share/mk.  This is to make it useful for all kernel
builders.

Note: we have waaay too many weird and wonderful ways of making
kernel code (monolithic kernel, modules, rump).  There should be
only one way to build kernel code instead of a maze of twisty little
.mk files, all not quite alike.  When that is fixed, this snippet can go
into the more generic .mk file.

2010-03-21 06:55:44 +00:00

3 Commits