Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: ChenQi <Qi.Chen@windriver.com>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 6/8] sysprof: convert to meson build
Date: Thu, 21 Dec 2017 15:07:19 +0200	[thread overview]
Message-ID: <8de24be3-b98a-ed71-67e5-e7528d0d1cd4@linux.intel.com> (raw)
In-Reply-To: <8af60152-a9bc-f16c-9666-3b0bd8ef6b75@windriver.com>

On 12/21/2017 12:14 PM, ChenQi wrote:
> It should be '_' instead '-'.
> '-Denable_gtk=true,-Denable_gtk=false,gtk+3'.

Thanks for spotting, I just sent a fixed patchset. Meson does not mind 
setting non-existing options :(

> I'm also trying out meson these days, as new version of systemd uses meson.

They've dropped autotools, right? I can imagine gstreamer will be the 
next to do that.

> I only checked this recipe of this series.
> Your other recipes also use '-'. Could you please double check if that's 
> correct?

I checked; it's correct. Sysprof is the only one which is using _ rather 
than - in options.

Alex


  reply	other threads:[~2017-12-21 13:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15 16:06 [PATCH 0/8] Introduce meson build system Alexander Kanavin
2017-12-15 16:06 ` [PATCH 1/8] meson: add a recipe and class from meta-oe Alexander Kanavin
2017-12-15 16:06 ` [PATCH 2/8] gnomebase.bbclass: split into autotools and meson versions Alexander Kanavin
2017-12-15 16:06 ` [PATCH 3/8] json-glib: convert to meson build Alexander Kanavin
2017-12-15 16:06 ` [PATCH 4/8] libepoxy: " Alexander Kanavin
2017-12-15 16:06 ` [PATCH 5/8] libinput: " Alexander Kanavin
2017-12-15 16:06 ` [PATCH 6/8] sysprof: " Alexander Kanavin
2017-12-21 10:14   ` ChenQi
2017-12-21 13:07     ` Alexander Kanavin [this message]
2017-12-15 16:06 ` [PATCH 7/8] gst-player: Upgrade, rename to gst-examples Alexander Kanavin
2017-12-15 16:06 ` [PATCH 8/8] meson: export native env only for native build Alexander Kanavin

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=8de24be3-b98a-ed71-67e5-e7528d0d1cd4@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=Qi.Chen@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox