From: Saul Wold <sgw@linux.intel.com>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: qingtao.cao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] cairo: add libpng to EXTRA_libcairo_la_DEPENDENCIES
Date: Wed, 13 Mar 2013 09:33:36 -0700 [thread overview]
Message-ID: <5140AA60.8020705@linux.intel.com> (raw)
In-Reply-To: <055756a16301a9a8d41701c48d30cf4bddc44617.1363154328.git.liezhi.yang@windriver.com>
On 03/13/2013 01:58 AM, Robert Yang wrote:
> There is a build error when I update the git repo and build again:
>
> x86_64-linux-libtool: link: cannot find the library `/path/to/sysroots/x86_64-linux/usr/lib/libpng15.la' or ...
>
> This because libpng was 1.5 before I update the git repo, and it
> is 1.6 now, libpng's include dir and lib dir are special, they are:
>
> /usr/include/libpngXX/png.h
> /usr/lib/libpngXX.la
>
> The XX is the version, e.g, libpng15.la, cairo doesn't handle this
> depends well, the configure finds that the lbpng is 1.6 after the
> update, but it doesn't rebuild libcairo.la since this depends isn't in
> the Makefile, it should have a file like cairo.def (cairo has this file,
> but it is only used for windows) to record this dependency. Add
> libpng's includedir to EXTRA_libcairo_la_DEPENDENCIES as a quick fix.
>
I understand what you are trying to do here, but this is a point fix for
a much bigger issue with the renaming of libpngXX, there are a number of
other issues that will be uncovered and making this a hard code change
here is not correct.
There are other .la that will contain pngXX and cause problems, this
issue is also contained in SSTATE files, in the past we would do PR
bumps to all the affected recipes that depended on PNG.
Sau!
> [YOCTO #4002]
>
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> ---
> meta/recipes-graphics/cairo/cairo_1.12.14.bb | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/meta/recipes-graphics/cairo/cairo_1.12.14.bb b/meta/recipes-graphics/cairo/cairo_1.12.14.bb
> index 16f9d7b..857cfa6 100644
> --- a/meta/recipes-graphics/cairo/cairo_1.12.14.bb
> +++ b/meta/recipes-graphics/cairo/cairo_1.12.14.bb
> @@ -38,6 +38,19 @@ FILES_cairo-gobject = "${libdir}/libcairo-gobject.so.*"
> FILES_cairo-script-interpreter = "${libdir}/libcairo-script-interpreter.so.*"
> FILES_cairo-perf-utils = "${bindir}/cairo-trace ${libdir}/cairo/libcairo-trace.so.*"
>
> +do_compile() {
> + # The libpng's include is special, it is usually
> + # usr/include/libpngXX, the XX is the version number, add it to
> + # libcairo.la's dependencies so that libcairo.la can be rebuilt
> + # when libpng upgrades.
> + if [ "${PN}" = "cairo-native" ]; then
> + libpng_DEPS="`pkg-config libpng --variable=includedir`"
> + else
> + libpng_DEPS="${STAGING_DIR_HOST}`pkg-config libpng --variable=includedir`"
> + fi
> + oe_runmake EXTRA_libcairo_la_DEPENDENCIES="$libpng_DEPS"
> +}
> +
> do_install_append () {
> rm -rf ${D}${bindir}/cairo-sphinx
> rm -rf ${D}${libdir}/cairo/cairo-fdr*
>
next prev parent reply other threads:[~2013-03-13 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 8:58 [PATCH 0/1] cairo: add libpng to EXTRA_libcairo_la_DEPENDENCIES Robert Yang
2013-03-13 8:58 ` [PATCH 1/1] " Robert Yang
2013-03-13 16:33 ` Saul Wold [this message]
2013-03-15 3:32 ` Robert Yang
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=5140AA60.8020705@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=qingtao.cao@windriver.com \
/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