From owner-svn-src-head@FreeBSD.ORG Tue May 6 04:42:14 2014 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 66A2F729; Tue, 6 May 2014 04:42:14 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3ACEDEEA; Tue, 6 May 2014 04:42:13 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-232-70.lns20.per1.internode.on.net [121.45.232.70]) (authenticated bits=0) by vps1.elischer.org (8.14.8/8.14.8) with ESMTP id s464g9aP000429 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 5 May 2014 21:42:12 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <5368681C.9020108@freebsd.org> Date: Tue, 06 May 2014 12:42:04 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Warner Losh , svn-src-head@freebsd.org Subject: Re: svn commit: r265419 - head/share/mk References: <201405060421.s464LnXl065686@svn.freebsd.org> In-Reply-To: <201405060421.s464LnXl065686@svn.freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2014 04:42:14 -0000 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.. 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. 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. 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.. J