[9fans] kernel mk

[9fans] kernel mk

[boyd, rounin]

one thing i have never understood is why i need to:

    mk 'CONF=foo' foo

why can't i?

    mk foo

or just:

    mk

with some default variable in the mkfile?

Re: [9fans] kernel mk

[Russ Cox]

> or just:
>
>     mk
>
> with some default variable in the mkfile?

you can, as long as the default is the one
you want to compile.

as to why you have to say mk 'CONF=pcf' instead
of mk 9pcf when the default isn't right, i think i
tried to remove this once and the metarules you'd have
to write end up applying to too much.

russ

Re: [9fans] kernel mk

[boyd, rounin]

> of mk 9pcf when the default isn't right, i think i
> tried to remove this once and the metarules you'd have
> to write end up applying to too much.

my findings exactly.

damn ec2t doan work, but i'll play with it tomorrow.

being able to type azerty is a big win.  in fact i found
myself typing qwerty on it.

i would suggest that kbmap, if it exixts, be bound, by default, to /dev

Re: [9fans] kernel mk

[Geoff Collyer]

You don't have to; I type

	mk			# build 9pc
	mk 'CONF=pccpu'		# build 9pccpu
	mk 'CONFLIST=pc pccpu' all # build both
	mk all			# build all kernels

The reason you can't just type

	mk 9pccpu

is that there would have to already be a mkfile target named `9pccpu',
so adding a new kernel configuration would require editing the kernel
mkfile.  The use of CONF and CONFLIST allows mk to construct the
necessary rules on the fly:

$p$CONF:	$CONF.c $OBJ $LIB
	$CC $CFLAGS '-DKERNDATE='`{date -n} $CONF.c
	$LD -o $target -T0x80100020 -l $OBJ $CONF.$O $LIB
	size $target