Re: [pcre-dev] Replies to many, again

Daniel Richard G. wrote:

> Sheri,
>
> So MSYS binaries don't use any DLL libraries of their own? I'd figure there
> might be ones for e.g. libiconv or libxml2.
>

There are a couple under the bin directory:

Sheri@xx-xxxxxxxxxx /usr/bin
$ ls *.dll
libW11.dll msys-1.0.dll

Sheri@xx-xxxxxxxxxx /usr/bin
$


Msys is just the front end/console app.

In the bin directory under my mingw dir, I have mingwm10.dll.

My mingw dir is not the like-named subdir of msys (that is empty). Msys
knows the location of mingw because of an fstab file in its etc. dir.

Under mingw, there is also a libs dir but it is full of .a and .o files.
I believe .a files are static libraries (as a user, I am only familiar
with .dll libraries - short for dynamic link libraries; when an
application is linked to an .a file, I think the user of the application
doesn't see any separate libraries.).
> (I was hoping to see what the naming convention was for these such DLLs---
> "lib" prefix or no? Library version number or no?---to compare with what
> Libtool is giving us in that environment.)
>
In the myriad of dll files in the system32 directory under Windows,
there are no prefixes or version number. Version info is available when
these dll files are mouse-hovered, and in file properties. That's the
feature you get when a coff file gets linked in (at least via gcc).

Regards,
Sheri