On 22 Dec 2013, at 6:58 am, Martin Strubel <hack...@section5.ch> wrote:

> Now, pondering about the clean top-down way cross-compile-approach, I
> think this would turn out in quite a nightmare, at least for mingw.
> Obstacles:
> The mingw runtime isn't part of GCC, neither is the win32API, and making
> it build inside the 'unified' directory structure of gcc is a big
> question mark. GHDL needs them to build though.
> So this will turn into a multi pass compilation dance anyhow:
> - Build native bootstrap toolchain to use for further compilation
> - Build mingw compiler with ADA support, first pass
> - Build supporting runtime/win32api with mingw
> (-) Build mingw with ADA and VHDL, second pass
> 
> (-) is yet missing, the current development build procedure to weld a
> cross ghdl backend against the mingw cross compiler is still hacky and
> not tested in a sandboxed build environment.

>From Drangon Zhou's scripts I kind of gathered that changes might be a 
>nightmare and that these would either be a patch against a particular gcc 
>distribution or require gcc developer acquiescence and introduction (which 
>might not be forthcoming for a marginal 'market').

> But good news so far is that the current ghdl-update sources compile
> just fine in native and cross mode (thumbs up for Brian). So allow me
> some time to come up with some patches that don't look like a bad hack :-)

I think I managed not send a snarky post saying you could do all the fiddling 
at the translate/gcc/dist.sh script level, which would have the saving grace of 
not requiring someone to verify your changes don't affect any other ghdl build 
method, but from Tristan's post he is apparently volunteering.  

The big question is whether or not a cross compile target can be generalized, 
and it likely can be, EXE suffixes aside.

And I take it you are aware libgrt.a is GPLv2?  The implication being 
distributed executable models are GPL'd.   There's a ghdl-discuss thread from 
April 28, 2010, where Tristan says he didn't anticipate someone delivering 
executable models, maybe he'll bend to an LGPL.













_______________________________________________
Ghdl-discuss mailing list
Ghdl-discuss@gna.org
https://mail.gna.org/listinfo/ghdl-discuss

Reply via email to