From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Tue, 28 Apr 2015 10:02:36 +0200 Subject: [Buildroot] [PATCH] cc-tool: new package In-Reply-To: <553F385A.50308@bis.org.pl> References: <1430142129-32750-1-git-send-email-marcin@bis.org.pl> <20150427173126.23797992@free-electrons.com> <553E9212.4090805@bis.org.pl> <20150427231028.5a0fd7df@free-electrons.com> <553F385A.50308@bis.org.pl> Message-ID: <20150428100236.7ac9ff4e@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Dear Marcin Bis, On Tue, 28 Apr 2015 09:35:54 +0200, Marcin Bis wrote: > > This is not what a host tools is. A host tool runs on your PC, i.e > > where you do the Buildroot build. For sure your PC has sufficient > > resources to run cc-tool. > > As I understand, host-tools are intended for doing something with images > generated by Buildroot e.g. flashing, generating fs images etc. Right. > cc-tool does not fall under this category. > It is some how similar to openocd, but openocd can be used to debug > bootloader/Linux kernel running on some SoC-s (so it perfectly makes > sense here). Indeed. > TI chips, which cc-tool talks to - are not able to run Linux at all. Ok, so what you mean is that those TI chips are typically not connected to the development PC directly, but are generally connected to the embedded system that runs Buildroot. > Of course cc-tool can be added to Buildroot as a host tool too. > I can prepare the patch if you want. Nope, if you don't use it, don't do it. I'm fine with a target package after the explanations you provided. Thanks! Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com