* [Buildroot] Building a usable ImageMagick
@ 2009-11-04 7:26 Baruch Siach
2009-11-04 8:24 ` Thomas Petazzoni
0 siblings, 1 reply; 3+ messages in thread
From: Baruch Siach @ 2009-11-04 7:26 UTC (permalink / raw)
To: buildroot
Hi Buildroot list,
I'm trying to produce a working ImageMagick installation under Buildroot.
According to my test ImageMagick depends on having *.la files in the
/usr/lib/ImageMagick-6.4.8/modules-Q16/coders/ directory in order to find its
codecs at run-time. Unfortunately, the target-finalize target in the main
Makefile includes the following line:
find $(TARGET_DIR)/usr/lib \( -name '*.a' -o -name '*.la' \) -print0 | xargs -0 rm -f
which means that all *.la file get removed from the target. What is the best
approach to solve this issue?
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] Building a usable ImageMagick
2009-11-04 7:26 [Buildroot] Building a usable ImageMagick Baruch Siach
@ 2009-11-04 8:24 ` Thomas Petazzoni
2009-11-04 8:30 ` Thomas Petazzoni
0 siblings, 1 reply; 3+ messages in thread
From: Thomas Petazzoni @ 2009-11-04 8:24 UTC (permalink / raw)
To: buildroot
Hello,
Le Wed, 4 Nov 2009 09:26:40 +0200,
Baruch Siach <baruch@tkos.co.il> a ?crit :
> I'm trying to produce a working ImageMagick installation under
> Buildroot. According to my test ImageMagick depends on having *.la
> files in the /usr/lib/ImageMagick-6.4.8/modules-Q16/coders/ directory
> in order to find its codecs at run-time.
Argh, odd. I just had a quick look at ImageMagick source code, and
that's right, they seem to use the .la files at runtime, at least to
get the list of available modules.
> Unfortunately, the target-finalize target in the main Makefile
> includes the following line:
>
> find $(TARGET_DIR)/usr/lib \( -name '*.a' -o -name '*.la' \) -print0
> | xargs -0 rm -f
>
> which means that all *.la file get removed from the target. What is
> the best approach to solve this issue?
.la files really aren't meant to be used at run time, so I would
suggest to fix ImageMagick. Why don't they use the .so files to get the
list of available modules ?
Sincerly,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] Building a usable ImageMagick
2009-11-04 8:24 ` Thomas Petazzoni
@ 2009-11-04 8:30 ` Thomas Petazzoni
0 siblings, 0 replies; 3+ messages in thread
From: Thomas Petazzoni @ 2009-11-04 8:30 UTC (permalink / raw)
To: buildroot
Le Wed, 4 Nov 2009 09:24:38 +0100,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> a ?crit :
> .la files really aren't meant to be used at run time, so I would
> suggest to fix ImageMagick. Why don't they use the .so files to get
> the list of available modules ?
We're not the only ones having the issue it seems:
http://src.opensolaris.org/source/xref/sfw/usr/src/cmd/ImageMagick/la.patch
http://src.opensolaris.org/source/xref/jds/spec-files/branches/opensolaris-2008-05/patches/imagemagick-01-ltdl.diff
Sincerly,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-11-04 8:30 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-11-04 7:26 [Buildroot] Building a usable ImageMagick Baruch Siach
2009-11-04 8:24 ` Thomas Petazzoni
2009-11-04 8:30 ` Thomas Petazzoni
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox