Re: [Mingw-users] Building DLLs using MinGW & libtool

[Earnie B. <ear...@ya...>]

Bob Friesenhahn wrote:
> 
> On Tue, 11 Jun 2002, Earnie Boyd wrote:
> 
> > Do you have the msysDTK?  And msysDVLPR?
> >
> > All autoconfiguration tools must have the same prefix, that's why I
> > provided the msysDTK.  I have the configured all of the tools to
> > --prefix=/usr.
> 
> I have not discovered a shred of documentation on the MinGW web site
> as to what msysDTK and msysDVLPR are intended for.  In order to
> determine what they are, the end user must download the package and
> list its contents.  I installed msysDTK because it appeared to be
> benign (but useful), but I get the impression that msysDVLPR replaces
> the MinGW compilation environment with a new one which is intended to
> build MSYS components.
> 

The msysDVLPR doesn't replace the MinGW binaries, they sit in a
different location.  It does provide a set of GCC and binutils binaries
that create binaries dependent on the msys-1.0.dll.  However, you must
enter into the "MSYS environment" to use them.  By "MSYS environment" I
mean that the uname -s returns MSYS instead of MINGW32.  To enter into
the "MSYS environment" I've provided a script named msysdvlpr, execute
it and you should see a new window with MSYS in the left of the title
bar instead of MINGW32.

> I have no intention to tie the built product to any special MinGW/MSYS
> DLLs.  My objective is to offer ImageMagick users an alternative to
> using the expensive Visual C++ compiler if they want to compile for
> Windows.  I should be able to tell users to download and install MinGW
> X.X and MSYS X.X.X, start MSYS, type "./configure --enable-shared",
> 'make', 'make install', and go have fun.  It shouldn't be necessary
> for users to install more packages than that.
> 

Good.  My mention of msysDVLPR was due to the fact that you were trying
to update your environment with CVS libtool.  I'd suggest you enter into
the "MSYS environment" to configure and build it.  I also suggest
--prefix=/usr as that is where the autoconf/automake tools are prefixed
and libtool must match their prefix.

Earnie.