make -mno-win32 the gcc default?
Wed Jan 10 14:27:00 GMT 2001
I didn't see this in the Cygwin mailing list but the CYGWIN environment
variable controls the behavior of the Cygwin DLL. GCC is not the Cygwin
This has nothing to do with "cygwin" or "make".
So, Charles' suggestion is correct.
On Wed, Jan 10, 2001 at 05:13:55PM -0500, Charles Wilson wrote:
>Sure. 'export CC="gcc -mwin32"' and 'export CXX="g++ -mwin32"' in your
>Ashok Vadekar wrote:
>> Could the switch be controlled by a $CYGWIN keyword? Then both modes could
>> be considered default wrt. the command line. You would merely have to decide
>> how you wanted cygwin (make, really) to behave.
>> On Wed, Jan 10, 2001 at 04:54:26PM -0500, Charles Wilson wrote:
>> > Christopher Faylor wrote:
>> > >
>> > > Earnie has been proposing this and I sort of like the idea but dread the
>> > > potential hue and cry that could result.
>> > >
>> > I also like the idea, but am terrified of the torrent of "It worked with
>> > gcc-2.95.2 and cygwin beta 1.1 [sic]" complaints. Also I'm not sure
>> > that all of "my" packages are _WIN32 clean. (For the most part, if they
>> > compiled -- I was happy. I didn't look too closely beyond that. I know
>> > that zlib and libpng are WIN32 clean 'cause I tested them with
>> > -mno-win32. Dunno *for sure* about the rest).
>> > > So, is the hue and cry from the lack of WIN32 counterbalanced by potentially
>> > > easier UNIX porting?
>> > Ummm....yyyyeeessss....I think????
>> > --Chuck
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin