Re: Where did the Cygwin and Mingw checks go?

[Mo DeJong]

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++.

Mo DeJong
Red Hat Inc