Re: [Resend winegcc03] winewrap can handle the default output name

[Dimitrie O. Paun]

On Tue, 9 Sep 2003, Richard Cohen wrote:
> Slightly different from last time.
> > Default name that mingw uses is a.exe
> > This also stops winewrap from segfaulting when passed no arguments.
>
> Changelog
>      Handle default linker output name (a.exe) in winewrap instead of 
> winegcc

I'm still not sure I like this one, as I said, a.out is a gccism,
and should be handled in winegcc. winewrap does not have to be
command line compatible to the GNU tool (as it currently stands),
we can require an output name for it.

[Resend winegcc03] winewrap can handle the default output name

[Richard Cohen]

Dimitrie O. Paun wrote:
> I'm still not sure I like this one, as I said, a.out is a gccism,

No, a.exe is a mingw-ld ism ;-)
> and should be handled in winegcc. winewrap does not have to be
> command line compatible to the GNU tool (as it currently stands),
> we can require an output name for it.

We have an external interface, winegcc, and an internal interface 
winegcc->winewrap.

+ The external interface is more or less fixed.
+ We can define the internal interface as we see fit -- but for sanity's 
sake it should be as similar as possible to ld
+ A SEGV in winewrap is *absolutely unacceptable*, so we can either
   1. Throw up an error message in winewrap, or
   2. Duplicate the default output name in winegcc & winewrap
   3. Have the default output name only in winewrap

(3) simplifies the code considerably, and I really don't understand your 
objection.

Richard.

[Resend winegcc03] winewrap can handle the default output name

[Dimitrie O. Paun]

On September 10, 2003 06:44 am, Richard Cohen wrote:
> Dimitrie O. Paun wrote:
> > I'm still not sure I like this one, as I said, a.out is a gccism,
>
> No, a.exe is a mingw-ld ism ;-)

True, but I think it may screw up configure scripts. They do work with 
a.out, don't change as I'm fairly sure they will break with a.exe.
> (3) simplifies the code considerably, and I really don't understand your
> objection.

Fine, if we keep the default to a.out...

[Resend winegcc03] winewrap can handle the default output name

[Richard Cohen]

Dimitrie O. Paun wrote:
> True, but I think it may screw up configure scripts. They do work with 
> a.out, don't change as I'm fairly sure they will break with a.exe.

Then won't the configure scripts break with mingw as well ?

Richard.

[Resend winegcc03] winewrap can handle the default output name

[Dimitrie O. Paun]

On Wed, 10 Sep 2003, Richard Cohen wrote:
> Then won't the configure scripts break with mingw as well ?

No, because the configure script tests the extension. If the
extension is .exe, it will try to run XXX.exe, which will not
work in our case.

I've spent some time dealing with this long time ago, it may
have changed, I don't know. But it works properly now (you
can almost even ./configure --with-wine now in wxWindows),
so please test it throughly before changing it.