From: Trevor Woerner <twoerner@gmail.com>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH 01/17] libwebsockets: rely on cmake.bbclass to put cmake package files in dev package
Date: Thu, 24 May 2018 13:30:14 -0400 [thread overview]
Message-ID: <20180524173013.GA30624@linux-uys3> (raw)
In-Reply-To: <CAJ86T=U5THX1tOFnTzBwr1sMoRvLqFiwqNbn0HT==fv5o9Mo-A@mail.gmail.com>
On Mon 2018-05-21 @ 11:10:59 AM, Andre McCurdy wrote:
> It hasn't been updated to give ordering for PACKAGECONFIG or
> BBCLASSEXTEND but the conventions for those (based on recipes in
> oe-core) seem to be:
>
> - PACKAGECONFIG lines go between "inherit ..." and EXTRA_OECONF
> - BBCLASSEXTEND goes at the end of the recipe
Done.
Thanks for the pointers/tips :-)
prev parent reply other threads:[~2018-05-24 17:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 1:30 [meta-oe][PATCH 01/17] libwebsockets: rely on cmake.bbclass to put cmake package files in dev package Andre McCurdy
2018-05-18 1:30 ` [meta-oe][PATCH 02/17] openobex: " Andre McCurdy
2018-05-18 1:30 ` [meta-oe][PATCH 03/17] rocksdb: " Andre McCurdy
2018-05-18 1:30 ` [meta-oe][PATCH 04/17] capnproto: " Andre McCurdy
2018-05-18 1:30 ` [meta-oe][PATCH 05/17] grpc: " Andre McCurdy
2018-05-18 1:30 ` [meta-oe][PATCH 06/17] json-spirit: " Andre McCurdy
2018-05-18 1:30 ` [meta-oe][PATCH 07/17] librcf: " Andre McCurdy
2018-05-18 1:30 ` [meta-oe][PATCH 08/17] msgpack-c: " Andre McCurdy
2018-05-18 1:30 ` [meta-oe][PATCH 09/17] rapidjson: " Andre McCurdy
2018-05-18 1:30 ` [meta-oe][PATCH 10/17] glm: " Andre McCurdy
2018-05-18 1:30 ` [meta-oe][PATCH 11/17] openjpeg: " Andre McCurdy
2018-05-18 1:30 ` [meta-oe][PATCH 12/17] ceres-solver: " Andre McCurdy
2018-05-18 1:30 ` [meta-oe][PATCH 13/17] gflags: " Andre McCurdy
2018-05-18 1:30 ` [meta-oe][PATCH 14/17] libftdi: " Andre McCurdy
2018-05-18 1:30 ` [meta-oe][PATCH 15/17] libssh: " Andre McCurdy
2018-05-18 1:30 ` [meta-oe][PATCH 16/17] libtinyxml2: " Andre McCurdy
2018-05-18 1:30 ` [meta-oe][PATCH 17/17] poco: " Andre McCurdy
2018-05-18 1:56 ` [meta-oe][PATCH 01/17] libwebsockets: " Khem Raj
2018-05-18 19:07 ` Andre McCurdy
2018-05-18 21:01 ` Khem Raj
2018-05-18 22:28 ` Andre McCurdy
2018-05-19 2:37 ` Trevor Woerner
2018-05-19 4:52 ` Khem Raj
2018-05-19 11:59 ` Peter Kjellerstedt
2018-05-19 19:35 ` Trevor Woerner
2018-05-20 8:23 ` André Draszik
2018-05-21 18:10 ` Andre McCurdy
2018-05-24 17:30 ` Trevor Woerner [this message]
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=20180524173013.GA30624@linux-uys3 \
--to=twoerner@gmail.com \
--cc=armccurdy@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
/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.