[alpine-devel] Re: Cross-compilers [was: Re: [alpine-aports] [PATCH 2/3] testing/gcc-arm-none-eabi: New aport]
how about providing a single APKBUILD for all cross-compilers targeting
embedded bare-metal platforms and using subpackages to create the actual cross
The attached APKBUILD implements this for gcc. The same should approach could
be applied to binutils, newlib (in case of non-AVR devices) and gdb (in case of
non-AVR devices). Also C++ support should be provided (at least for AVR
devices) to enable users to use Arduino. (Right now I disabled it for faster
Btw: Is there a way to not create the base package?
On Mon, 28 Aug 2017 10:09:50 +0300
Timo Teras <timo.teras_at_iki.fi> wrote:
> We've occasionally received requests for cross-compilers. And in fact
> we do keep the *-avr variant already because we can't have native
> building for it really nor run alpine on these microcontrollers.
> Now ARM embedded is the second most popular, and many would benefit
> from a cross compiler, probably me including.
> I was earlier hopeful on getting an 'abuild build flavors' feature
> where abuild could be used to automatically build several different
> flavors of same APKBUILD - in cross-compiler case involving building
> binutils & gcc for several different CTARGETs.
> But as this feature has not been implemented yet, I'm writing to check
> if anyone is working on it, or willing to work on it very soon. Or
> should we open up to accept cross-compilers as separate APKBUILDs until
> this feature is done?
> Also, arm-none-eabi is also targetting bare-metal. So I wonder if this
> should be separately added anyway. _at_ncopa, any thoughts if this
> should/could reference the main 'gcc' or be separate like suggested in
> the patch?
> On Sat, 26 Aug 2017 16:07:28 +0200
> Marian Buschsieweke <marian.buschsieweke_at_ovgu.de> wrote:
> > The GNU Compiler Collection for embedded ARM targets (e.g. Cortex
> > M0/M3/M4/...) http://gcc.gnu.org
Received on Mon Sep 18 2017 - 18:10:35 UTC
- application/octet-stream attachment: APKBUILD