All of lore.kernel.org
 help / color / mirror / Atom feed
From: Radu Moisan <radu.moisan@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3] dbus: include dbus-launch in the main dbus package
Date: Fri, 27 Jul 2012 09:10:23 +0300	[thread overview]
Message-ID: <501230CF.6090000@intel.com> (raw)
In-Reply-To: <CAJTo0LZKHiL75khHuircKy7Xv0aVW29DJjGaCSxXh+K1p6F1oQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]


On 07/27/2012 12:12 AM, Burton, Ross wrote:
> On 26 July 2012 14:17, Enrico Scholz <enrico.scholz@sigma-chemnitz.de> wrote:
>> Radu Moisan <radu.moisan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
>> writes:
>>
>>> Followed suggestions from Bugz 2261:
>>>
>>> 1) remove the --with-x/--without-x configure arguments.
>> why? They are valid ./configure options and common when evaluating the
>> x11 distro-feature.  Selecting them explicitly makes the build more
>> predictable and detects configuration errors earlier.
>>
>> Sense of '--without-x' was disabling of x11 dependency, but not turning
>> off the x11-autolaunch feature.
> That's my fault, and I can't remember my reasoning.  Probably best to
> bring it back so the recipe is explicit.
>
> Radu, bring back this fragment, but correct the options
>
> EXTRA_OECONF_X = "${@base_contains('DISTRO_FEATURES', 'x11',
> '--enable-x11-autolaunch', '--disable-x11-autolaunch', d)}"
>
> Ross
>
I've looked into the configure script and found that autolaunch feature 
is depending on x11, in other words using --with-x/--without-x implies 
--enable-x11-autolaunch/--disable-x11-autolaunch, so I guess the initial 
EXTRA_OECONF_X line will do pretty much the same thing.

EXTRA_OECONF_X = "${@base_contains('DISTRO_FEATURES', 'x11', '--with-x', 
'--without-x', d)}"

Radu

[-- Attachment #2: Type: text/html, Size: 2533 bytes --]

  reply	other threads:[~2012-07-27  6:20 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26  6:17 [PATCH v3] dbus: include dbus-launch in the main dbus package Radu Moisan
2012-07-26  6:29 ` Radu Moisan
2012-07-26  8:08   ` Koen Kooi
2012-07-26  8:42     ` Paul Eggleton
2012-07-26  8:43       ` Koen Kooi
2012-07-26  9:18         ` Radu Moisan
2012-07-26  9:51           ` Koen Kooi
2012-07-26 10:23             ` Burton, Ross
2012-07-26 10:36               ` Radu Moisan
2012-07-26 10:31             ` Radu Moisan
2012-07-26 10:55               ` Radu Moisan
2012-07-26 11:27                 ` Burton, Ross
2012-07-26 11:55                   ` Koen Kooi
2012-07-26 12:00                     ` Burton, Ross
2012-07-26 12:29                       ` Koen Kooi
2012-07-26 12:32                         ` Paul Eggleton
2012-07-26 12:38                           ` Koen Kooi
2012-07-26 12:56                             ` Paul Eggleton
2012-07-26 13:06                               ` Radu Moisan
2012-07-26 13:07                               ` Koen Kooi
2012-07-26 13:12                                 ` Paul Eggleton
2012-07-26 13:21                                   ` Koen Kooi
2012-07-26 12:36                       ` Radu Moisan
2012-07-26 12:51                         ` Koen Kooi
2012-07-26 12:59                           ` Radu Moisan
2012-07-26 13:08     ` Enrico Scholz
2012-07-26 13:24       ` Radu Moisan
2012-07-26 14:32         ` Enrico Scholz
2012-07-26 21:14           ` Burton, Ross
2012-07-26 13:17 ` Enrico Scholz
2012-07-26 21:12   ` Burton, Ross
2012-07-27  6:10     ` Radu Moisan [this message]
2012-07-27  6:15       ` Radu Moisan
2012-07-27 10:02       ` Burton, Ross

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=501230CF.6090000@intel.com \
    --to=radu.moisan@intel.com \
    --cc=openembedded-core@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.