On Sun, Mar 25, 2007 at 02:54:02AM -0400, Daniel Richard G. wrote:
> > # Some Windows-specific targets for MinGW. Do not use for Cygwin.
> >
> > winshared : .libs/@WIN_PREFIX@??? .libs/@WIN_PREFIX@??? \
> > .libs/@WIN_PREFIX@???
> >
> > .libs/@WIN_PREFIX@??? : libpcre.la
> > $(CC) $(CFLAGS) -shared -o $@ pcre.coff\
> > -Wl,--whole-archive .libs/libpcre.a \
> > -Wl,--out-implib,.libs/libpcre.dll.a \
> [...]
>
> I'm thinking that all this---the rules to create e.g. pcre.dll, and the
> .coff metadata---should be addressed by the CMake side of things. They're a
> bit of a third wheel in Makefile.am, and MinGW can be considered a special
> case of a "Windows build environment."
>
> This way, on MinGW, ./configure gets you Unixy-style MinGW libraries
> (libpcre-0.dll et al.), and CMake gets you more Windowsy-style ones
> (pcre.dll + Explorer properties).
I'm not sure I agree here. If it's just a matter of running a few more
commands, why not just do it? Also, what is really the difference
between a autotools generated dll and a cmake generated dll?
Bob Rossi
