Re: Where did the Cygwin and Mingw checks go?

[Christopher Faylor]

On Sat, Nov 18, 2000 at 05:26:32AM -0800, Mo DeJong wrote:
>On 18 Nov 2000, Alexandre Oliva wrote:
>
>> On Nov 17, 2000, Eric Christopher <address@hidden> wrote:
>> 
>> > So a solaris cross cygwin compiler would define EXEEXT to be .exe,
>> > however, OBJEXT would be .o because it was compiled on a solaris
>> > box.
>> 
>> I suppose a compiler that targets Cygwin will create .obj object files
>> regardless of its host platform.  I.e., when using a Cygwin compiler
>> (such that --host=cygwin), you'd get OBJEXT=.obj, regardless of the
>> build platform, on which the compiler runs.
>
>No, it depends in what your compiler outputs.
>
>% cat tmp.c 
>int i;
>
>% i386-mingw32msvc-gcc -c tmp.c
>
>% ls tmp.*
>tmp.c  tmp.o
>
>% ./i586-cygwin32-gcc -c tmp.c 
>
>% ls tmp.*
>tmp.c  tmp.o
>
>You would only get a .obj file if you were using VC++.

Correct.  To the best of my knowledge, Cygwin has never produced objects
with a .obj extension.  Since it is supposed to be emulating a UNIX
environment, there is no need to do this.

The .exe extension on executable files is a requirement of the "OS", however,
so we can't avoid using that, unfortunately.

cgf