On May 5, 2014, at 10:42 PM, Julian Elischer <jul...@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=ARM-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’t 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=$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’s no ‘install-toolchain’, but perhaps there should be. Warner
signature.asc
Description: Message signed with OpenPGP using GPGMail
