[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: `make build` granularity
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: `make build` granularity
- From: Chuck Yerkes <chuck+obsd_(_at_)_2003_(_dot_)_snew_(_dot_)_com>
- Date: Mon, 25 Aug 2003 20:12:04 -0400
- Mail-followup-to: Chuck Yerkes <chuck+obsd_(_at_)_2003_(_dot_)_snew_(_dot_)_com>, misc_(_at_)_openbsd_(_dot_)_org
Quoting david l goodrich (dlg_(_at_)_dorkzilla_(_dot_)_org):
> when i run `make build` in /usr/src, it builds the whole tree, and then
> `make install` will install /everything/, games, gcc, etc. what about
> machines that don't have, for example, games33.tgz and comp33.tgz
> installed in the base system? won't `make build` and `make install`
> basically do a full install of -CURRENT? is there a way to limit the
> process?
> --david
>
> [demime 0.98d removed an attachment of type application/pgp-signature which had a name of PGP.sig]
If you build, you need a compiler. You'll ALWAYS get include dirs.
Those games33.tgz and comp33.tgz files are just tarballs of part of
the built area. When you build you get the whole OS by default.
/etc/mk.conf
can contain SKIPDIRS.
eg.
SKIPDIRS += games gnu/usr.bin/egcs
SKIPDIRS += usr.bin/rsh usr.bin/rlogin
etc.
+= means you can have multiple lines for readability.
etc.
Visit your host, monkey.org