Date: Tue, 14 Aug 2012 17:35:51 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Dave Hayes <dave@jetcafe.org> Cc: freebsd-arm@freebsd.org Subject: Re: Building ARM ports (was Re: Globalscale Dreamplug and 8.3 RELEASE) Message-ID: <CAJ-Vmok-n_focw5x4nM1Go2c0xRoeU=xehDAtTgeM2%2BtZ94GjA@mail.gmail.com> In-Reply-To: <502AEC99.70708@jetcafe.org> References: <5008728C.5040100@jetcafe.org> <1343846511.1128.34.camel@revolution.hippie.lan> <501B0E04.5040901@jetcafe.org> <1343951251.1128.53.camel@revolution.hippie.lan> <502AEC99.70708@jetcafe.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Guys/girls/etc, OpenWRT manages it. They started from the ground up with having to cross-build. Just because the problem is hard to tackle doesn't mean we shouldn't try. There's like a dozen half-done attempts at this. I realise you can't address _all_ the ports at once, but surely starting with a small subset and working outward is doable. I'll put up a bounty for anyone who actually comes up with a basic framework for supporting cross-building ports, documents how it does/doesn't work (eg if things like build vs run dependencies) and has a basic design for how to slowly fix ports to support it. Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmok-n_focw5x4nM1Go2c0xRoeU=xehDAtTgeM2%2BtZ94GjA>