From mboxrd@z Thu Jan 1 00:00:00 1970 From: Baruch Siach Date: Thu, 3 May 2012 21:08:57 +0300 Subject: [Buildroot] Building For Host as Target In-Reply-To: References: Message-ID: <20120503180857.GA2763@tarshish> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hi Assaf, On Thu, May 03, 2012 at 06:14:49PM +0300, Assaf Inbal wrote: > I'm working on a project based on buildroot and I want to have the ability > to compile my packages for both my MIPS target using an external toolchain > (which works great) but I also want to be able to compile for my host. > To be precise, I want to use the local gcc and libraries so I will be able > to run my packages locally as well. > I've tried setting an external toolchain path as "/usr" but as a part of > preparing the target file system everything from my /lib,/etc and others > are copied to the output directory, which is, well, bad. > > I've also toyed with creating a fake toolchain that was basically links to > the host's binaries but that also didn't go very well. > > Does anyone have an idea on how I might be able to achieve this? It seems to me that the easiest way is to select either i386 or x86_64 as target architecture (assuming that your host is a PC, we have recently discovered that this is not always the case), and run the result in a chroot, or in a virtualized system, on your development host. For a ready made qemu example see board/qemu/x86/readme.txt. baruch -- http://baruch.siach.name/blog/ ~. .~ Tk Open Systems =}------------------------------------------------ooO--U--Ooo------------{= - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -