This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Compiling with Borland's bcc32... more simply stated
- From: Christopher Faylor <cgf-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 7 Jul 2002 00:06:07 -0400
- Subject: Re: Compiling with Borland's bcc32... more simply stated
- References: <20020707040221.3064.qmail@web40208.mail.yahoo.com>
- Reply-to: cygwin at cygwin dot com
On Sat, Jul 06, 2002 at 09:02:21PM -0700, Motivus wrote:
>>I suspect that the reason you didn't receive any replies is that your
>>question doesn't make much sense. The whole point of cygwin is to
>>provide an environment for building GNU tools without reliance of
>>proprietary programs like those provided by Borland's. It is extremely
>>unlikely that you'll be able to use Borland's compiler to build GNU
>>tools for an ARM target.
>>
>>Just install gcc, like the rest of the Cygwin world, and use that.
>>Rerun setup.exe (from Install Cygwin Now!), click on the plus sign next
>>to "Devel" and then select gcc and any other tools you need.
>
>Oh. Now THAT'S embarrassing! I think I blinded myself by following a
>procedure for building the GNU tools under UNIX and then configuring
>them for cross-development on an ARM core. But I wasn't thinking
>through the changes that would have to be made when coming at it from a
>Cygwin environment.
Theoretically, there should be no changes required for setting things up
for cross development under the Cygwin environment. It should be
roughly the same as under UNIX.
>Thanks for the help! I mean it!!!
De nada.
cgf
--
Please do not send me personal email with cygwin questions.
Use the resources at http://cygwin.com/ .
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/