Date: Sun, 14 Nov 2010 10:43:38 -0700 From: John Hein <jhein@symmetricom.com> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-hackers@freebsd.org, freebsd-current <freebsd-current@freebsd.org>, freebsd-embedded@freebsd.org Subject: Re: The path is now set for "busybox", FreeBSD style Message-ID: <19680.8138.582316.245120@gossamer.timing.com> In-Reply-To: <AANLkTinUjWqiMUmN0=fYTP8rjCzoHh=D%2B7XL=ROqWobM@mail.gmail.com> References: <AANLkTinUjWqiMUmN0=fYTP8rjCzoHh=D%2B7XL=ROqWobM@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Adrian Chadd wrote at 11:40 +0800 on Nov 14, 2010: > I've committed the below changes to -HEAD. You can now create and build your > own busybox style binary system, completely cross-compiled within the > existing Make framework. It isn't as impressive as it sounds though - a lot > of the framework is already there from just building crunchgen'ed > rescue/sysinstall binaries. > > There's a few things which should be done. Specifically, being able to build > an alternative set of libraries before building the crunchgen target. The > base crosscompile system may include support for PAM, Kerberos, ATM/IPX, etc > but you may not want your crunch'ed image to have them. To do this right > now, you have to disable these features in the main build. That may be OK > for some. > > But just to stress it - I've got a couple of access point images at home > running a crunchgen'ed environment under MIPS and besides the obvious binary > bloat, it works perfectly well. Besides a cut-down startup framework, the > image cross-builds entirely from the base FreeBSD source tree. > > Let me know if you'd like to give it a shot and I'll put my "bsdbox" > Makefile scripts online to try. That's great. I assume it be not be hard for someone to take your scripts as a starting point and create a sysutils/bsdbox akin to sysutils/busybox?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19680.8138.582316.245120>