Richard W.M. Jones wrote:
On Thu, Jan 29, 2009 at 12:04:53AM +0100, Farkas Levente wrote:
> Richard W.M. Jones wrote:
>> On Wed, Jan 28, 2009 at 09:09:16PM +0100, Farkas Levente wrote:
>>> Richard W.M. Jones wrote:
>>>> On Wed, Jan 28, 2009 at 04:53:40PM +0000, Richard W.M. Jones wrote:
>>>>> On Wed, Jan 28, 2009 at 03:09:22PM +0100, Farkas Levente wrote:
>>>>>> hi,
>>>>>> as i previously send it (i just update it and resend) i agree
with dan's
>>>>>> comment so i remove params from mingw32_make.
>>>>>> devel branch is enough for this.
>>>>> ACK.
>>>> Although I'm still questioning why we need _mingw32_make at all ...
>>> to be able to use the same source (ie. mingw32-macros.mingw32) and have
>>> to edit it one place, for all helper scripts (ie. mingw32-configure
>>> mingw32-make).
>> No, no, I mean why do we need a make macro or script at all?
>>
>> The GNU coding standards define that this will work in all circumstances:
>>
>> ./configure --lots-of-options
>> make
>>
>> where options on the ./configure command line are turned into defaults
>> for make.
> suppose you make some cross compilation development. everywhere you put
> %{_mingw32_make} into the spec file but wouldn't like to always run it
> through rpmbuild you can use mingw32-make in the working directory.
No, I don't mean this. Why don't we remove both the _mingw32_make
macro and the mingw32-make script? Any usage of this macro/script
would be replaced by a simple 'make' command.
not all projects use gnu toolchain:-(
--
Levente "Si vis pacem para bellum!"