Re: [Mingw-users] ingw32-make 3.80 does not accept any command lineargument

[Bo Yang <techrazy.yang@xxxxxxxxx>]

Brian Dessent :
> Bo Yang wrote:
>
>   
>> When I invoke the mingw32-make 3.80 on windows command window, it works
>> well. But when I invoke it on the Msys shell, it did not accept any
>> command line arguments. I call "mingw32-make -v" or "mingw32-make -f
>> abc.mk", it always give me the same output which complain that "it can't
>> find any Makefile in the current directory". Could you please tell me
>> why it behave so strangely? Does this have something to do with the Msys
>> 1.0 underlaid mingw runtime?
>>     
>
> It sounds like you made the mistake of putting a non-MSYS binary in your
> MSYS bin directory.  You need to put it elsewhere, as only MSYS binaries
> can go there.  Alternatively you can upgrade to MSYS >= 1.11 which uses
> a different method of detecting which binaries are MSYS binaries.
>   
You mean, the files in /bin directory of Msys is not windows native 
binaries. So what are they?
>> Ah, I am sorry, but what is the difference between mingw32-make and msys 
>> make? I can't understand. Does not msys's make a windows native build?
>>     
>
> No, it has nothing to do with what is produced -- that is a function of
> what toolchain is in the PATH, what programs the Makefile was written to
> invoke, and the options specified therein.  This is not something that
> 'make' itself really has anything to do with, it is just a dumb tool
> that invokes whatever commands the Makefile instructs, it doesn't really
> have any specific knowledge of what it's doing.
>
> The difference is that a MinGW make will only understand Win32 paths
> (e.g. c:/foo/bar) whereas a MSYS make will understand both POSIX (e.g.
> /usr/local) and Win32 paths, assuming that it is a version of make that
> is new enough to have the "accept Win32 drive-letter style paths when
> built in posix-y mode" patch.  The implications of this difference can
> be subtle, especially when using MSYS as a build environment because all
> the MSYS tools do POSIX->Win32 juggling for command line arguments.  But
> this does not cover paths that are substituted by autoconf or that are
> directly generated by non-MSYS apps, as for example the case where the
> Makefile uses gcc's automatic dependency generation options.
>   
Yeah, so what is the difference between cyginw's make and msys's make?

Regards!
Bo


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
MinGW-users mailing list
MinGW-users@xxxxxxxxxxxxxxxxxxxxx

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users