All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Adrian Ratiu <adrian.ratiu@collabora.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>,
	Adrian Bunk <bunk@stusta.de>
Subject: Re: [meta-oe][PATCH v3] renderdoc: add new recipe
Date: Fri, 4 Oct 2019 01:37:59 +0200	[thread overview]
Message-ID: <CA+chaQeeZFnAAUbGFGHgypBF-O53pv1Gv7q8ZmjiOH95D5Wksw@mail.gmail.com> (raw)
In-Reply-To: <87ftkf9ery.fsf@collabora.com>

This should have x11 in REQUIRED_DISTRO_FEATURES to fix:

ERROR: Nothing PROVIDES 'libxcb' (but
meta-oe/meta-oe/recipes-graphics/renderdoc/renderdoc_1.4.bb DEPENDS on or
otherwise requires it)
libxcb was skipped: missing required distro feature 'x11' (not in
DISTRO_FEATURES)
ERROR: Required build target 'meta-world-pkgdata' has no buildable
providers.
Missing or unbuildable dependency chain was: ['meta-world-pkgdata',
'renderdoc', 'libxcb']

On Sun, Sep 29, 2019 at 7:46 PM Adrian Ratiu <adrian.ratiu@collabora.com>
wrote:

> On Sun, 29 Sep 2019, Adrian Bunk <bunk@stusta.de> wrote:
> > On Sat, Sep 28, 2019 at 12:48:10PM -0700, Khem Raj wrote:
> >> On Fri, Sep 27, 2019 at 9:56 AM Adrian Ratiu <
> adrian.ratiu@collabora.com> wrote:
> >>...
> >> > --- /dev/null
> >> > +++
> b/meta-oe/recipes-graphics/renderdoc/renderdoc/0002-q-renderdoc-CMakeLists.txt-remove-flag-unsupported-b.patch
> >> > @@ -0,0 +1,48 @@
> >> > +From 40511a6f4dc6311c8cf7f2954d1202ede55881ff Mon Sep 17 00:00:00
> 2001
> >> > +From: Adrian Ratiu <adrian.ratiu@collabora.com>
> >> > +Date: Wed, 25 Sep 2019 19:31:14 +0300
> >> > +Subject: [PATCH] (q)renderdoc/CMakeLists.txt: remove flag
> unsupported by GCC
> >> > +
> >> > +-Wno-unknown-warning is not supported by GCC, only by Clang so we
> >> > +remove it because newer GCC versions like 9.2.0 will complain, older
> >> > +versions would just ignore it.
> >> > +
> >> > +Upstream-Status: Pending [
> https://github.com/baldurk/renderdoc/pull/1530]
> >> > +
> >>
> >> gcc9 does support -Wno-unknown-warning perhaps you want
> >> -Wno-error=unknown-warning
> >>...
> >> > +TARGET_CFLAGS += "-Wno-error=deprecated-copy"
> >> > +
> >>
> >> this option is GCC specific mark it
> >> TARGET_CFLAGS_append_toolchain-gcc
> >>...
> >
> > Using -Wno-error always could solve both problems,
> > and would also avoid similar problems in the future.
>
> That's a good idea, however I can't pass directly -Wno-error in the
> recipe because of how the top-level CMakelists.txt is written: it always
> *appends* -Werror to the flags, so it overwrites our -Wno-error.
>
> A better solution which has the same effect is to use
> -DCMAKE_BUILD_TYPE=Release which prevents -Werror being appended at all
> in the top-level CMakelists.txt (there is no other effect than this!)
>
> Thanks! Will send an updatet v4 soon.
>
> >
> > cu
> > Adrian
> >
> > --
> >
> >        "Is there not promise of rain?" Ling Tan asked suddenly out
> >         of the darkness. There had been need of rain for many days.
> >        "Only a promise," Lao Er said.
> >                                        Pearl S. Buck - Dragon Seed
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>


  reply	other threads:[~2019-10-03 23:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-27 16:56 [meta-oe][PATCH v3] renderdoc: add new recipe Adrian Ratiu
2019-09-28 19:48 ` Khem Raj
2019-09-29 12:40   ` Adrian Bunk
2019-09-29 17:46     ` Adrian Ratiu
2019-10-03 23:37       ` Martin Jansa [this message]
2019-10-04  9:53         ` Adrian Ratiu
2019-10-04 16:31           ` Khem Raj
2019-09-29 17:41   ` Adrian Ratiu

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=CA+chaQeeZFnAAUbGFGHgypBF-O53pv1Gv7q8ZmjiOH95D5Wksw@mail.gmail.com \
    --to=martin.jansa@gmail.com \
    --cc=adrian.ratiu@collabora.com \
    --cc=bunk@stusta.de \
    --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.