Re: [Mingw-users] Final Q on libjpeg dll build

[Paul S. <pa...@is...>]

Hello Soren,

Soren Andersen <so...@wo...> wrote on Sunday, November 26, 2000:

SA> Hello,

SA> I know the users want to discuss other things. Still, I will report
SA> this: after two messages the important info that I'd better have a very
SA> recent ld.exe & gcc.exe finally got through to me, so i have them (as
SA> such:
SA>                 GNU ld version 19990818 (with BFD 19990818)
SA>                 gcc version 2.95.2 19991024 (release)

    Now, can you bridge new devel tools and my port? Just in case it's
not obvious ;-) (I guess it should be in the docs also), you should
apply patch.diff and run (sh script) Build.sh from my distribution.
Let's look at the latter:

=======
#!/bin/sh

echo Should build using native compiler
prefix=/usr/local
export CFLAGS="-O2 -DBUILD"
./configure
make libjpeg.a
a2dll libjpeg.a -o libjpeg.6.dll
make
install -c libjpeg.a $prefix/lib
install -c libjpeg.6.dll $prefix/bin
install -c jconfig.h jerror.h jmorecfg.h jpeglib.h $prefix/include
========

        So, this means: you've got to have all the standard posix
stuff on PATH, but gcc should be mingw's. Whole idea is first to build
static lib the usual way and then convert it to dll via a2dll utility,
available from http://www.is.lg.ua/~paul/devel/ .

        As for your own problems, I may guess you wouldn't have them
if you used binutils from www.mingw.org (but note: they are alpha,
it's only guess, since you don't bother to provide exact command which
you use to build stuff).

SA> .\libjpeg_dll.a

    Per latest gnu-win32 conventions, this should be libjpeg.dll.a.
New ld will try such name first when told -ljpeg (unless also told
--static).

SA>    **thanks**,
SA>      soren andersen

--
Paul Sokolovsky, IT Specialist
http://www.brainbench.com/transcript.jsp?pid=11135