From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building a usable ImageMagick
Date: Wed, 4 Nov 2009 09:24:38 +0100 [thread overview]
Message-ID: <20091104092438.29d3c3cf@surf> (raw)
In-Reply-To: <20091104072640.GC10219@jasper.tkos.co.il>
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
next prev parent reply other threads:[~2009-11-04 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 7:26 [Buildroot] Building a usable ImageMagick Baruch Siach
2009-11-04 8:24 ` Thomas Petazzoni [this message]
2009-11-04 8:30 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091104092438.29d3c3cf@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox