Date: Wed, 27 Mar 2013 15:13:31 -0600 From: Warner Losh <imp@bsdimp.com> To: Adrian Chadd <adrian@FreeBSD.org> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: RFC: "Crochet" build tool Message-ID: <36F7C55A-61A1-40D4-A37B-5A942FEF19F7@bsdimp.com> In-Reply-To: <CAJ-Vmo=5VuHhOo7qv6j8k2YEA2cEO5fzfFa_Qmao8dNkBru5zw@mail.gmail.com> References: <CFBA557F-3DB9-40BA-B222-8E8C67707C9B@freebsd.org> <5DFA61DB-70E4-4C3D-ACA0-995A175706C8@neville-neil.com> <5151B454.9090402@ceetonetechnology.com> <1CBF1416-3237-4DCE-8D61-7E998265C887@neville-neil.com> <1364311809.36972.27.camel@revolution.hippie.lan> <CAJ-Vmomcaoe4cBFtFbXHSe2ygWA9JZnMkE_zoy80unuT-L1Axg@mail.gmail.com> <5151D045.80305@thieprojects.ch> <CAJ-Vmomk0aGykV2Zv_9nW9Lg9THHspkfjHhiu7dEz1k1nPAibw@mail.gmail.com> <5151D9DB.7050001@thieprojects.ch> <167CF57D-01E3-4857-BF0E-C40B00FED226@netgate.com> <CAJ-VmokxSYqy4Zr1wtN=Ln4-2wJybqGeh_LSAC1tNM44DjTF1w@mail.gmail.com> <6AE34496-58E3-488B-BEE9-07FFB5A06AB3@netgate.com> <610BDDE6-A8EC-4D84-8FAF-1B6014808C24@bsdimp.com> <CAJ-Vmo=5VuHhOo7qv6j8k2YEA2cEO5fzfFa_Qmao8dNkBru5zw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 27, 2013, at 10:39 AM, Adrian Chadd wrote: > On 26 March 2013 17:23, Warner Losh <imp@bsdimp.com> wrote: >=20 >>> No, but none of them currently exist for non-x86 platforms, either. >>=20 >> Except that they do. I've built arm images in the past. >=20 > Do you have an example for using ARM + nanobsd? In the past it has been as simple as just setting NANO_ARCH to arm. Mips = required a hack that you set fdisk_mips to fdisk_i386 or something = similar... > One of the big changes I made for my build scripts is to separate out > toolchain/userland building (which is done once for a given > architecture) from kernel building (once per target) from image > building (again, once per target.) >=20 > It'd be nice if we could do something similar in -HEAD. Yes. NanoBSD needs some work in this area... It currently assumes that = you are building the image, not one of many related images, so it = couples those things together... Of course, it would help if the base = supported the external toolchain better, but that should be close... Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36F7C55A-61A1-40D4-A37B-5A942FEF19F7>