From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcus Osdoba Date: Tue, 14 Sep 2010 21:49:11 +0200 Subject: [Buildroot] preserve toolchain In-Reply-To: References: <4C8FBA92.1020006@googlemail.com> Message-ID: <4C8FD1B7.1070901@googlemail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Am 14.09.2010 20:45, schrieb Grant Edwards: > On 2010-09-14, Marcus Osdoba wrote: > >> For a shorter development cycle I like to preserve the toolchain >> generated by buildroot for the next run. > I used to try to do that, and had many problems with it. As a result, > I switched to using crosstool-ng to build the toolchain. > >> I naivly copied the output/toolchain to some other directory and set >> the toolchain directory in the buildroot config. The bin-directory >> does not include the gcc-binaries. Do I have to create links in the >> bin-directory to the gccs? >> >> Is it possible to take the same toolchain for package build the next >> time? > I managed to do it, but it required a number of customizations to the > external toolchain makefile, and there were still some minor issues > that required work-arounds in a shell-script that I was using to do > builds. I eventually gave up and heeded the advice of the > maintainers: now I use crosstool-ng to build my external toolchain. > >> Can I recycle the toolchain generated by buildroot? > Using crosstool-ng to build an external toolchain is the normal way of > accomplishing what you want to accomplish. > Many thanks for this clear statement and field report! This saved much time for me.