djbfft in pkg-multimedia SVN, new revision of a52dec
Fabian Greffrath
greffrath at leat.rub.de
Mon May 19 09:35:59 UTC 2008
Hi all,
I'd like to bring this topic back to your attention.
My plan is to package the djbfft library and link a52dec against it to
get rid of #441693. djbfft is an extremely fast library for
floating-point convulsion that is a soft dependency for a52dec and
will speed up the decoding process (at least I hope so!).
I have decided to build only a normal and a PIC static djbfft library
and to do without a shared library. The reasons for this are that (1)
upstream does only build a static library and that (2) the library is
optimized for speed and this benefit may get lost if linked dynamically.
Now I've got a question regarding how to link liba52 against the
djbfft library. I know that for a shared library to link against a
static one I have to link against the PIC version of the static one,
i.e. -ldjbfft_pic. This is not necessary for the static version of
liba52, but what if I do also link the static liba52 against the PIC
static libdjbfft_pic? Is there any possible harm in this? Should I
consider both cases in the Makefiles, i.e. if building the static
liba52 do -ldjbfft but if building the shared liba52 do -ldjbfft_pic?
How about the utilities in the a52dec package, should they be linked
against the PIC or the normal libdjbfft?
Please enlighten me!
Cheers,
Fabian
--
Dipl.-Phys. Fabian Greffrath
Ruhr-Universität Bochum
Lehrstuhl für Energieanlagen und Energieprozesstechnik (LEAT)
Universitätsstr. 150, IB 3/134
D-44780 Bochum
Telefon: +49 (0)234 / 32-26334
Fax: +49 (0)234 / 32-14227
E-Mail: greffrath at leat.ruhr-uni-bochum.de
More information about the pkg-multimedia-maintainers
mailing list