Date: Tue, 6 May 2014 09:18:15 -0600 From: Warner Losh <imp@bsdimp.com> To: Julian Elischer <julian@freebsd.org> Cc: svn-src-head@freebsd.org, Warner Losh <imp@FreeBSD.org> Subject: Re: svn commit: r265419 - head/share/mk Message-ID: <913B82D9-D361-4631-A32E-16330CB55E17@bsdimp.com> In-Reply-To: <5368681C.9020108@freebsd.org> References: <201405060421.s464LnXl065686@svn.freebsd.org> <5368681C.9020108@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_9AFB977B-5CF7-4419-A96F-2758EE50DCD7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On May 5, 2014, at 10:42 PM, Julian Elischer <julian@freebsd.org> wrote: > While you are wandering around in the Makefiles, I was wondering > if you could estimate the amount of work to have the ability to > specify the location of the build toolchain a bit better.. For building the /usr/src tree, this is easy. > Currently it's $(OBJPREFIX)/$(.CURDIR)/tmp or something > (different if cross compiling of course), but it'd > be nice to be able to generate a crossbuild toolchain externally > that can be used by other software.. It'd be really nice to be able > to use our sources to generate an ARM crossbuild set that > could then be used on third party software to make pi binaries for = example. make xdev is intended to do exactly that. > We have all this neat crossbuild capabilityin our source tree.. it's = be truely spectacular > if that was an exportable target. "make TARGET=3DARM-pi = crossbuildtools" which > could be used with a given make,conf file to "just build" ARM-rpi = binaries. make xdev should be what you want. Please let me know how it doesn=92t = meet your needs. You can either use it as a full cross compiler (the names are chosen so common tools = pick them up right), or you can do path games and have it appear as cc, as, etc. > At $JOB we currently we have a build env (which is incredibly broken = but that another story) > that expects to pull all includes, libs and tools from a certain = place... > I currently prepopulate it by doing make DESTDIR=3D$PLACE = installworld. > which is a bit of an overkill, but at least it works.. The toolchain = set we use in > buildworld would be about perfect to drop in there.. but > "make toolchain && cp -pr /obj/...../tmp/* $PLACE" > doesn't strike me as the most elegant way to do it.. Maybe xdev is right for you :) As far as I know, there=92s no = =91install-toolchain=92, but perhaps there should be. Warner --Apple-Mail=_9AFB977B-5CF7-4419-A96F-2758EE50DCD7 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTaP03AAoJEGwc0Sh9sBEAzFgP/2phnVGgyf+CWsniViYQ77v2 PJ7yJc9IFIpmYvzFUPxvUFf7d7iS3Vrvt7Eo83e3Hmh9Ykt/QFeyGJrr+VGfN/wg qxl+737AsWpg4Ox/QQgrt5sgVjyrw4zR2IJ/d5ebeGohg8IvUMOpi6W5sIwjLvUQ 7KcXUSzmdE6t+LYNH5d6je9BfWP4Wtz1BpA4026fgVquSJQS/c8/014Z/fZCSvbt ezvMS/Y3CfPNFUQsZW6CdYQUNb6rx42+P0aEr+U6sVeRWIL7D+DyYFJTzAX7ZOhx H6tHoZvPPqzfJXrRsghnyzkJM0AgsHe77/uPeGXw6SAROjJ9k+bWIAwEqzw7IFlc ZebcHSdzpbvqvy5HX5cv4Azvs+X5xX1tGDfLzrXtQWacfmJCURf27p+6wPPPCcdn 9mJEtqMt3AAwvHdFTAxv7wYEgflHy1cHGekVZwbfJ1cEGAyCuxOKPuLzomC/4JEU KgrEA3vHFTQJW+OJh4cm8KfgJPkFiFTPP6JRtna8H/wDkBY/EIqOLoCYv5PX4vO8 1+5kW8zp23p1QnRqEA+O3cv5jirT1AsdwNFCvUDMjmmD20icjERj5eqpofBRjkJ+ Xoo01FLh1PzguFhTW28cyvzArtYiKo6OpMlwVcRIik716kbJc2/KohU1t4bcMmVC 3y0H4lqDSXepLzkNf+V2 =muxn -----END PGP SIGNATURE----- --Apple-Mail=_9AFB977B-5CF7-4419-A96F-2758EE50DCD7--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?913B82D9-D361-4631-A32E-16330CB55E17>