This is the mail archive of the 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: ARM tool chain & other questions...

>-----Original Message-----
>From: Grant Edwards []
>Sent: 28 November 2001 17:09

>> > The final question... How stable is the GCC cross compiler 
>when it's been
>> > run on a windows machine under cygwin? Has many people 
>developed major
>> > projects on it. How did you find it. It looks stable to me 
>but the longest C
>> > program i wrote so far using this configuration was 40 
>lines and it was all
>> > completed in one evening. What's the story if it's been 
>used for a couple of
>> > weeks or a month or two??
>> Use linux, you will save a lot of blood and tears vs windows/cygwin.
>That said (and I agree), I've got several customers who are
>doing development under Cygwin and I have never heard of any
>problems other than the usual MS-Windows related complaints.

  I'll speak up to defend cygwin too at this point.  I've built PPC cross
compilers on Solaris, Cygwin and Linux, and the process has been pretty
much the same all round.  AFAIK, there are precisely two (2) additional
things to watch out for on cygwin:  dos-vs-PC-style line ends, which you
fix by mounting all your source directories in textmode, and the fact 
that prior to 2.95.3 you had to give the --with-included-gettext flag to
configure and delete the texinfo/ subdirectory from the gcc source tree
in order to get the .info files to build correctly.

  Furthermore the Gcc cross compiler under cygwin does not in any way
decay with time, whether you've been using it for a couple of weeks or
a couple of years.

  Further-further-more, it's free and you get the source, and if you
need professional support you still have the option of getting a support
contract from redhat/cygwin, which will include bugfixes or new features
to the toolchain according to your requirements.

  I think it's building Gcc for the first few times that causes the blood
sweat and tears, no matter what system you build it on, and finding out
how it works that makes it seem easier later.

Burn your ID card!
Help support the campaign, copy this into your .sig!

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

Want more information?  See the CrossGCC FAQ,
Want to unsubscribe? Send a note to

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