All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume BERAUDO <guillaume.beraudo@belledonne-communications.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] linphone: added recipe for v3.4.3
Date: Wed, 8 Jun 2011 10:29:10 +0200	[thread overview]
Message-ID: <20110608102910.50c67a63@guibc> (raw)
In-Reply-To: <20110607151843.GD23137@jama.jama.net>

Hi,

> > > > > > +OVERRIDES_append = ":video:console"
> > > > > 
> > > > > This looks like someone trying to implement USE flags in
> > > > > OE :). But I'm not sure it's right way and I haven't noticed
> > > > > this used in any other recipe. So it would be better to
> > > > > discuss first.
> > > > 
> > > > I am new to openembedded and thus may have missed something in
> > > > the documentations. Can you point me to some elegant way to
> > > > implement recipe flavours?
> > > 
> > > I don't think TSC agreed on some sort of USE-flag solution or
> > > policy yet, but keeping shared EXTRA_OECONF in linphone-3.4.3.inc
> > > and then EXTRA_OECONF_append with nogtk specific options in
> > > separate files like linphone-nogtk_3.4.3.bb would be easier to
> > > understand (at least to me), even when not so "elegant" as your
> > > OVERRIDES solution.

With your advice, a typical linphone recipe would contain a block like
this:

# With video
DEPENDS_append = " libxv ffmpeg libv4l"
EXTRA_OECONF_append = "
--with-ffmpeg=${STAGING_DIR_HOST}${layout_exec_prefix} --enable-video"

# Without video
#EXTRA_OECONF_append = " --disable-video"


# GTK GUI
DEPENDS_append = " gtk+"
PROVIDES_append = " linphone"
PACKAGES_prepend = "${PN}-dbg ${PN} ${PN}-doc ${PN}-dev ${PN}-locale "
EXTRA_OECONF_append = " --enable-gtk_ui=yes"

# Without GTK GUI
#EXTRA_OECONF_append = " --enable-gtk_ui=no"


Though it is easier at first glance I feel it error prone.
When creating a new recipe, it is easy to forget uncommenting
directives.

Is it blocking to use my initial solution with OVERRIDES?
If yes, what about using a "@base_conditional"?
Eg:
LINPHONE_FLAVOUR_WITH_GTK = '1'
@base_conditional('LINPHONE_FLAVOUR_WITH_GTK', '1', 'something when
active', 'something when inactive')

This would keep the recipes simple and avoid using any OVERRIDES or
_append.



> > There is also some conditionnals with the DEPENDS.
> > What is the use of all the "DEPENDS_some-package-name" directives?
> > Isn't it identical to only use the global "DEPENDS"?
> 
> Yes it looks weird and broken on quick glance.
> but "shared" DEPENDS = "foo" in linphone-3.4.3.inc and DEPENDS_append
> = "gtk+" in linphone-gtk_1.2.4.bb makes sense
>  
> > I removed all the RDEPENDS stuff. Can you confirm it was
> > unnecessary?
> 
> all linked .so providers should be picked to rdepends automatically by
> package.bbclass so only extra stuff like linphone-gtk-config would be
> needed in extra RDEPENDS_${PN} in linphone-gtk_1.2.4.bb.

Isn't the "inherit pkgconfig" managing it already?

Also, do you thing this line is of any use?
"export PKG_CONFIG=${STAGING_BINDIR_NATIVE}/pkg-config"

Regards
Guillaume



  reply	other threads:[~2011-06-08  8:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <guillaume.beraudo@belledonne-communications.com>
2011-06-07 12:13 ` [PATCH] linphone: added recipe for v3.4.3 Guillaume Beraudo
2011-06-07 12:41   ` Martin Jansa
2011-06-07 12:57     ` Guillaume BERAUDO
2011-06-07 13:09       ` Martin Jansa
2011-06-07 13:34         ` Guillaume BERAUDO
2011-06-07 13:23     ` Guillaume BERAUDO
2011-06-07 13:33       ` Martin Jansa
2011-06-07 14:23         ` Guillaume BERAUDO
2011-06-07 15:18           ` Martin Jansa
2011-06-08  8:29             ` Guillaume BERAUDO [this message]
2011-06-07 12:42   ` Koen Kooi
2011-06-07 12:59     ` Guillaume BERAUDO
2011-06-15  8:42 ` [PATCH v2] " Guillaume Beraudo
2011-06-15  8:47   ` Koen Kooi
2011-06-15  8:54     ` Guillaume BERAUDO
2011-06-15  8:54   ` Phil Blundell
2011-06-15  9:04     ` Guillaume BERAUDO
2011-06-15  9:02 ` [PATCH v3] " Guillaume Beraudo
2011-06-22 11:16   ` Guillaume BERAUDO
2011-06-22 14:41     ` Khem Raj
2011-06-23  8:28       ` Guillaume BERAUDO

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=20110608102910.50c67a63@guibc \
    --to=guillaume.beraudo@belledonne-communications.com \
    --cc=martin.jansa@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.