Date: Mon, 20 Jun 2005 18:41:26 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: freebsd-current@FreeBSD.org Subject: Re: Summary: experiences with NanoBSD, successes and nits on a Soekris 4801 Message-ID: <20050620183857.R26664@fledge.watson.org> In-Reply-To: <20050620173016.GB93634@dragon.NUXI.org> References: <20050619155228.Y6413@fledge.watson.org> <66959.1119209763@critter.freebsd.dk> <m2br613i8n.wl%gnn@neville-neil.com> <p0621021dbedbfa4dd5ff@[128.113.24.47]> <20050620094835.Q19830@fledge.watson.org> <20050620173016.GB93634@dragon.NUXI.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 20 Jun 2005, David O'Brien wrote: > On Mon, Jun 20, 2005 at 09:58:46AM +0100, Robert Watson wrote: >> - Try to figure out how to better differentiate build vs. install time >> frobbing. For example, the NanoBSD NO_CXX concern: we want C++ >> applications, we just don't want to install the build chain. >> Currently, we have no way to differentiate these concepts, since our >> dependencies are entirely build-time, and our frobs have to match up >> (generally) between build and install. I.e., devd is built only if >> !NO_CXX, which is a build-time concern. > > Is NanoBSD split into a build and install phase like > buildworld/installworld? If so, can you try the equivalent of 'make > buildworld && make -DNO_CXX installworld'? installworld and buildworld both conditionalize recursing into devd based on NO_CXX. I.e., we don't distinguish between that dependency for build/install separately. Robert N M Watson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050620183857.R26664>