Re: [Mingw-users] Why program in MSYS depends upon msys-1.0.dll

[Eli Z. <el...@gn...>]

> Date: Sun, 5 Jul 2015 12:20:20 -0700 (PDT)
> From: "Alan W. Irwin" <ir...@be...>
> 
> The MinGW part of MinGW/MSYS includes, e.g.,
> 
> MinGW-4.7.2/bin/mingw32-make.exe
> 
> while the MSYS part of MinGW/MSYS includes
> 
> MinGW-4.7.2/msys/1.0/bin/make.exe

Yes.

> For CMake-based build systems, if you put MinGW-4.7.2/bin on the PATH
> and keep MinGW-4.7.2/msys/1.0/bin _off_ the PATH then you can use the
> "MinGW Makefiles" CMake generator and mingw32-make.exe to build
> executables for a project.  Alternatively, you can put both locations
> on the PATH, and use the "MSYS Makefiles" CMake generator and make.exe
> to build executables for a project.

In general, I recommend to have MinGW on MSYS's PATH, but not the
other way around.

> In the "MinGW Makefiles" case I assume those executables are not
> linked in any way to msys-1.0.dll, but in the "MSYS Makefiles" case I
> assume they are linked to msys-1.0.dll.

Yes.

> Can somebody confirm those assumptions?

Done.

> Also, can somebody help with the appropriate options for either
> readelf or objdump to discover what libraries are linked to an
> executable?

objdump -x xyzzy.exe | fgrep -I "dll name:"