From:	dj AT delorie DOT com (DJ Delorie)
Subject:	gcc --print-file-name: win32 or posix?
22 Dec 1998 18:44:59 -0800 :
Message-ID:	<199812230227.VAA02263.cygnus.cygwin32.developers@envy.delorie.com>
To:	cygwin32-developers AT cygnus DOT com

Opinion/technical question time, folks!

If you do "gcc --print-file-name libgcc.a" cygwin's gcc currently
prints the result using Win32 paths.  This breaks cygwin's make.  We
were just about to change it to print posix paths, but we realized
that it was done this way for a reason, and there are cases where it
makes sense to print win32 paths.

We thought about using -mcygwin or -mmingw to trigger the output type,
but those only work for native gcc's - they won't work if the gcc is
host=cygwin but a different target (the -m options are
target-specific, not host-specific).

My thought was that if gcc was built for a cygwin host, chances are,
the other tools were also, so posix paths make sense, and if gcc is
built with non-cygwin, chances are the other tools were too, so native
paths make sense.

Can anyone think of other possible solutions or caveats?

- Raw text -