Date: Fri, 10 Jun 2005 13:15:29 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: "Poul-Henning Kamp" <phk@phk.freebsd.dk> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/tools/tools/nanobsd ... Message-ID: <p06210268becf79438ee9@[128.113.24.47]> In-Reply-To: <1298.1118422892@critter.freebsd.dk> References: <1298.1118422892@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
At 7:01 PM +0200 6/10/05, Poul-Henning Kamp wrote: >In message <p06210266becf5fcd9731@[128.113.24.47]>, Garance A Drosihn writes: > > >>Are any macros defined (-D) in CFLAGS when building for nanoBSD, >>or other "please make a smaller system" situations? ISTR some >>value to check via #ifdef, but now I can't remember what it was >>or where I saw it used. > >Yes, that is what the commit you quote is all about :-) > >nanobsd uses a private make.conf to keep them in. That's not quite what I mean, unless I missed something. Over in usr.bin/env/env.c, I want to add some features that people probably would not car about if they are trying to trim the system down to a minimal size. As near as I can tell, neither the Makefile nor make.conf in tools/tools/nanobsd sets any define's via CFLAGS. So, what variable would a source file check for via #ifdef to skip the compilation of any extra "frill" features? -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06210268becf79438ee9>