Date: Mon, 9 Jan 2012 01:04:14 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Stefan Bethke <stb@lassitu.de> Cc: freebsd-arch@freebsd.org Subject: Re: Where should I put ar71xx_* modules? Message-ID: <CAJ-Vmo=peK%2BA%2BTnLVRZvf0TVSnCBisXRRpKgV%2BpwC-qL3-PABQ@mail.gmail.com> In-Reply-To: <DFFFE611-01A1-4B3F-8DFF-72E410483D5D@lassitu.de> References: <CAJ-Vmom08uFV%2BNMryjZon_xnqo95MAK8r2=0s_JqRet7EMdn4g@mail.gmail.com> <09C21BD6-46E1-4593-9E3C-183CF229A613@lassitu.de> <CAJ-VmomWF6g1kgrzKxvsveeOjc-sNoKNoL090331%2BwV4OPSAfw@mail.gmail.com> <DFFFE611-01A1-4B3F-8DFF-72E410483D5D@lassitu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9 January 2012 00:52, Stefan Bethke <stb@lassitu.de> wrote:
> We have lots of modules that have specific requirements; they're still co=
nnected to the build. =A0What warrants different handling here? =A0You coul=
d put them under .if ${MACHINE_CPUARCH} !=3D "mips" like a number of them a=
re already.
Hm, I didn't want to add modules for a specific SoC that won't ever be
built for any other platform. Eg, if someone does a XLR build, they
shouldn't get ar71xx modules built.
But sure, I can just connect them to the mips build and be done with it.
Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=peK%2BA%2BTnLVRZvf0TVSnCBisXRRpKgV%2BpwC-qL3-PABQ>