This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ 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]

Re: [WAY OT]: need a windows-based PPC cross-compiler


[Sorry to break threading; Thunderbird stupidly won't let you reply do individual posts in a digest. Please CC me in any replies.]


Subject:
Re: [WAY OT]: need a windows-based PPC cross-compiler
From:
Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
Date:
Tue, 19 Apr 2005 10:15:01 -0400
To:
Dave Murphy <wintermute2k4@ntlworld.com>, "Robert P. J. Day" <rpjday@mindspring.com>, crossgcc list <crossgcc@sources.redhat.com>


To:
Dave Murphy <wintermute2k4@ntlworld.com>, "Robert P. J. Day" <rpjday@mindspring.com>, crossgcc list <crossgcc@sources.redhat.com>



On Mon, Apr 18, 2005 at 08:57:24PM +0100, Dave Murphy wrote:


Robert P. J. Day wrote:


i spologize profusely for this OT post but, after googling, i still
haven't quite found what i'm looking for.

i need a windows or cygwin-based PPC cross-compiler toolchain to
generate code for an 8xx PPC target.  i've done all my work on linux
using DENX's ELDK 3.1.1 PPC toolchain, and i'm deliriously happy with
it.

sadly, there are some other folks who want to build the same project,
but they *strongly* prefer to work under windows.  and since the entire
build is managed by gnu make, it would seem that working under cygwin
is the only option.

given the cross-compiler expertise on this list, i'm hoping someone can
point me in the right direction.  thanks.




you might like to check out devkitPPC - it's meant primarily for
Gamecube development but should be suitable for other powerpc targets
with a little linkscript & crt0 massaging. It's built using mingw (
http://www.mingw.org ) and I highly recommend minsys as an alternative
to cygwin.



Of course "minsys" is really just an older version of cygwin under the hood so it's not like you're not using cygwin when you build packages using this package.



Oh.
Anytime anyone even mentions the -mno-cygwin flag on the Cygwin mailing list, they get sent packing to the MinGW group. At least the MinGW/MSYS folks try to provide a method of creating native Win32 executables without linking to a 3rd party DLL. For the others: When you build in Cygwin, your executable links to the Cygwin DLL. To distribute this executable, you have to redistribute the Cygwin DLL, which can't operate with other versions of itself. One runs into "DLL hell" with distributing a Cygwin-built program. MinGW/MSYS really is an *alternative* to building in Cygwin.


Though to be fair, I can understand that it may not be in the interest of Redhat to do anything about the Cygwin DLL hell. It doesn't do any good to intimate, as above, that MSYS "is really just an older version of Cygwin", thereby promoting Cygwin over MinGW/MSYS, when in reality there *are* distinct differences, though not obvious. And like all engineering, the differences are a matter of tradeoffs, one is not better than the other.

And I very much appreciate the fact that there is cooperation on maintaining the window/cygwin/mingw port of GCC from both cgf and Danny Smith.

Oddly enough, the msys home page doesn't mention this fact.


You must have not digged deep enough:
<http://www.mingw.org/history.shtml>
Oh, and they also mention Cygwin here too:
<http://www.mingw.org/mingwfaq.shtml#faq-usingwithcygwin>

I don't recall Cygwin mentioning MinGW/MSYS...

Eric



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]