Message-ID: <45A6FFFE.3080903@gmail.com>
Date: Thu, 11 Jan 2007 20:26:54 -0700
From: Morgan Gangwere <0 DOT fractalus AT gmail DOT com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Building applications from source to support cygwin
References: <01dc01c735f7$9ae74330$a501a8c0 AT CAM DOT ARTIMI DOT COM>
In-Reply-To: <01dc01c735f7$9ae74330$a501a8c0@CAM.ARTIMI.COM>
OpenPGP: id=5231E2FA
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dave Korn wrote:
> On 12 January 2007 03:06, Larry Hall (Cygwin) wrote:
> 
>> Christopher Faylor wrote:
>>> On Thu, Jan 11, 2007 at 07:48:02PM -0500, Sparky Sparky wrote:
>>>> I know this is a newbie question, but I can't find it in the
>>>> documentation. How (if?) do you compile a standard x86 source to
>>>> support cygwin?
>>> How would you build the application on linux?  Same way, i.e., something
>>> like: 
>>>
>>> gcc -o foo foo.c
>>
>> Wrong!  You type "make".
>>
>> Phsh, newbies. ;-)
>>
> 
> Wrong!  You type "./configure", then you type "make".
> 
> Phsh, oldbies!  
> 
> [ hmm.. autoconf.. automake... aclocal... we could probably take this back
> waay too far :) ]
> 
>     cheers,
>       DaveK

no, you run
for(file in src/):
   if(system(gcc -o file file) == 0):
      print "oops! Gcc messed up!"

python does building BETTER! :P
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)

iD8DBQFFpv/+XIyDjlIx4voRAi7kAJ9kD/T4asfXeaXLZn6qaRJvAx9DQQCeKmLa
xHGgFEUzGpLxsfp1miW4iqg=
=Hc3k
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/