Re: [winegcc03] winewrap can handle the default output name
Dimitrie O. Paun wrote: The reason I've handled it in winegcc rather than winewrap is that this seems to be a (historical) feature that's specific to gcc, and there doesn't seem to be any reason to have such a feature perpetuated in winewrap. winegcc <-> gcc, winewrap<->ld $ man ld ... -o output --output=output Use output as the name for the program produced by ld; if this option is not specified, the name a.out is used by default. The script command "OUTPUT" can also specify the output file name. Anyone up for renaming winewrap to wineld ? ;-} Richard.
Re: [winegcc03] winewrap can handle the default output name
On August 13, 2003 09:55 pm, Richard Cohen wrote: > 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 The reason I've handled it in winegcc rather than winewrap is that this seems to be a (historical) feature that's specific to gcc, and there doesn't seem to be any reason to have such a feature perpetuated in winewrap. -- Dimi.
Re: [winegcc03] winewrap can handle the default output name
On August 14, 2003 04:30 am, Richard Cohen wrote: > winegcc <-> gcc, winewrap<->ld > > $ man ld > ... > -o output > --output=output > Use output as the name for the program produced by > ld; if this option is not specified, the name a.out > is used by default. The script command "OUTPUT" can > also specify the output file name. > > Anyone up for renaming winewrap to wineld ? ;-} Well, it's true that winewrap does ld's job, but we don't have to maintain mingw/binutil compatibility for this one. For people that need wine/mingw portability, they should use gcc/winegcc as a frontend to do the linking. I don't have a problem having winewrap default to a.exe if no name is given. But I'm not sure we need to do to the trouble of providing (too much) ld compatibility, as we do in winegcc. -- Dimi.
