This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See crosstool-NG for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
"Yann E. MORIN" <yann.morin.1998@free.fr> writes: > Esben, All, > > On Saturday 21 April 2012 20:45:24 Esben Haabendal wrote: >> "Yann E. MORIN" <yann.morin.1998@free.fr> writes: >> >> > Changes (from 4.000 feet high): >> > - no need for a pre-exisiting x-compiler for the target >> > - a complete x-compiler for target is built for internal use, but is not >> > exported for the user to use >> >> Will it still be possible to use a pre-existing x-compiler for target? >> >> When building let's say 3 canadian-cross crompilers, fx. >> >> i686-linux -> arm-linux >> x86_64-linux -> arm-linux >> mingw32 -> arm-linux >> >> It would be nice to be able to not have to build the same target >> x-compiler three times. > > Ah, I did not think of this use-case... No, the new infra will not allow > that. The whole purpose was to get rid of the separate cross-compiler build, > to be able to build the canadian cross in one run (except of course the > cross- compiler for the host which is needed anyway to cross-build all the > other stuff for the host). > > I believe this will be easy to re-add in the next release, though. The code > was there anyway, it's just a matter to re-enable it. > > Thanks for the suggestion! Great, I will look forward to that, so I don't have to get stuck on an old version of ct-NG :-) /Esben -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |