From: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] gphoto2_2.4.8.bb: Stop configure from looking in /usr/local/include
Date: Tue, 2 Nov 2010 07:38:18 +0100 [thread overview]
Message-ID: <AANLkTin5-JTEH=Zk__6MWxY53t_WYufSX4x+w6sonE7t@mail.gmail.com> (raw)
In-Reply-To: <4CCF64DD.9080709@gmail.com>
2010/11/2 Graham Gower <graham.gower@gmail.com>:
> * Point configure at where it can find jpeg.
> * Explicitly disable cdk and aalib.
> * Fix license while here.
>
> Signed-off-by: Graham Gower <graham.gower@gmail.com>
> ---
> recipes/gphoto2/gphoto2_2.4.8.bb | 9 +++++++--
> 1 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/recipes/gphoto2/gphoto2_2.4.8.bb b/recipes/gphoto2/gphoto2_2.4.8.bb
> index ea54713..836ea85 100644
> --- a/recipes/gphoto2/gphoto2_2.4.8.bb
> +++ b/recipes/gphoto2/gphoto2_2.4.8.bb
> @@ -1,7 +1,8 @@
> DESCRIPTION = "gphoto2 is a command-line utility to fetch pictures from digital cameras"
> SECTION = "console/utils"
> -LICENSE = "GPL"
> -DEPENDS = "libtool libgphoto2 popt"
> +LICENSE = "GPLv2+"
> +DEPENDS = "libtool libgphoto2 popt jpeg"
The original recipe would build without the depends on jpeg
adding it to depends should be mentioned in the commit message
> +PR = "r1"
>
> SRC_URI = "${SOURCEFORGE_MIRROR}/gphoto/gphoto2-${PV}.tar.bz2;name=gphoto2 \
> file://gphoto-popt-fixup.patch"
> @@ -11,6 +12,10 @@ SRC_URI[gphoto2.sha256sum] = "a2e2f70fd6051234cbc3d76dc82df6991e8a07ead56aa8d5c4
>
> inherit autotools
>
> +EXTRA_OECONF="--without-cdk \
> + --without-aalib \
> + --with-jpeg-prefix=${STAGING_EXECPREFIXDIR}"
> +
I have some concerns here.
For configure it seems best to explicitly set and reset the flags in
it, otherwise you may just pick up whatever happened to be build
before.
from --help:
Optional Features:
--disable-option-checking ignore unrecognized --enable/--with options
--disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no)
--enable-FEATURE[=ARG] include FEATURE [ARG=yes]
--disable-dependency-tracking speeds up one-time build
--enable-dependency-tracking do not reject slow dependency extractors
--enable-shared[=PKGS] build shared libraries [default=yes]
--enable-static[=PKGS] build static libraries [default=yes]
--enable-fast-install[=PKGS]
optimize for fast installation [default=yes]
--disable-libtool-lock avoid locking (might break parallel builds)
--disable-largefile omit support for large files
--disable-nls do not use Native Language Support
--disable-rpath do not hardcode runtime library paths
Optional Packages:
--with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
--without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
--with-pic try to use only PIC/non-PIC objects [default=use
both]
--with-gnu-ld assume the C compiler uses GNU ld [default=no]
--with-gnu-ld assume the C compiler uses GNU ld default=no
--with-libiconv-prefix[=DIR] search for libiconv in DIR/include and DIR/lib
--without-libiconv-prefix don't search for libiconv in
includedir and libdir
--with-libintl-prefix[=DIR] search for libintl in DIR/include and DIR/lib
--without-libintl-prefix don't search for libintl in includedir and libdir
--with-libgphoto2=PREFIX
where to find libgphoto2, "no" or "auto"
--without-pthread Don't use pthread
--without-cdk Do not use cdk
--with-cdk-prefix=PREFIX
Location of cdk
--without-jpeg Do not use jpeg
--with-jpeg-prefix=PREFIX
Location of jpeg
--with-libexif=PREFIX where to find libexif, "no" or "auto"
--without-aalib Do not use aalib
--without-readline Do not use readline
All things that are not mentioned in DEPENDS should (IMHO) be
explicitly be turned off.
And for the things in DEPENDS I would encourage to still add them.
E.g. --with-jpeg. Yes I know these will always be picked up when a
DEPENDS = "jpeg" is present, but making it explict does not hurt and
it trips an error if jpeg is not there and someone does a bitbake -b
of the recipe (instead of silently building a package without jpeg).
Thanks for your contribution & apologies for using your commit for a
rant on configure flags.
Frans.
> do_configure_append() {
> find ${S} -name Makefile | xargs sed -i 's:/usr/include:${STAGING_INCDIR}:'
> }
> --
> 1.7.1
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2010-11-02 6:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 1:09 [PATCH] gphoto2_2.4.8.bb: Stop configure from looking in /usr/local/include Graham Gower
2010-11-02 6:38 ` Frans Meulenbroeks [this message]
2010-11-02 22:00 ` Khem Raj
2010-11-03 9:42 ` Frans Meulenbroeks
2010-11-03 15:17 ` Khem Raj
2010-11-03 15:44 ` Andrea Adami
2010-11-03 15:47 ` Martin Jansa
2010-11-03 16:07 ` Khem Raj
2010-11-03 19:04 ` Frans Meulenbroeks
2010-11-03 20:06 ` Khem Raj
2010-11-03 20:21 ` Frans Meulenbroeks
2010-11-03 20:46 ` Khem Raj
2010-11-05 7:51 ` Frans Meulenbroeks
2010-11-05 15:39 ` Khem Raj
2010-11-05 17:21 ` Frans Meulenbroeks
2010-11-03 0:04 ` Graham Gower
2010-11-03 7:57 ` Koen Kooi
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='AANLkTin5-JTEH=Zk__6MWxY53t_WYufSX4x+w6sonE7t@mail.gmail.com' \
--to=fransmeulenbroeks@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.