From: "Feist, James" <james.feist@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] nlohmann-json: Add symlink to json.hpp and update to 3.3.0
Date: Thu, 11 Oct 2018 13:41:13 -0700 [thread overview]
Message-ID: <6ddccc38-c256-1ab9-e01f-360febf6cfe9@linux.intel.com> (raw)
In-Reply-To: <CAMKF1spEhWhnGzvePs5QDZspaT6u=rMg3T_n=QtuuZ87EJWB6A@mail.gmail.com>
On 10/11/2018 1:33 PM, Khem Raj wrote:
> Hi James
>
> It seems this srcrev does not exist on master branch but on develop
> branch probably
> we need to add branch=develop to SRC_URI as well.
>
> see
>
> http://errors.yoctoproject.org/Errors/Build/69670/
My mistake, clicking the tag in github jumped my branch, I'll fix
the revision and resubmit.
Thanks,
James
> On Thu, Oct 11, 2018 at 10:15 AM James Feist
> <james.feist@linux.intel.com> wrote:
>>
>> nlohmann-json has examples in their repo that refer to
>> the header as json.hpp directly, as such many packages
>> that require nlohmann-json expect json.hpp and not
>> nlohmann/json.hpp as the cmake file installs. Create symlink
>> so that access is available by either option. Also update
>> to release 3.3.0.
>>
>> Signed-off-by: James Feist <james.feist@linux.intel.com>
>> ---
>> .../nlohmann-json/nlohmann-json_git.bb | 10 ++++++++--
>> 1 file changed, 8 insertions(+), 2 deletions(-)
>>
>> diff --git a/meta-oe/recipes-devtools/nlohmann-json/nlohmann-json_git.bb b/meta-oe/recipes-devtools/nlohmann-json/nlohmann-json_git.bb
>> index a89b659ae..c1e108b38 100644
>> --- a/meta-oe/recipes-devtools/nlohmann-json/nlohmann-json_git.bb
>> +++ b/meta-oe/recipes-devtools/nlohmann-json/nlohmann-json_git.bb
>> @@ -6,9 +6,9 @@ LIC_FILES_CHKSUM = "file://LICENSE.MIT;md5=9a8ae1c2d606c432a2aa2e2de15be22a"
>>
>> SRC_URI = "git://github.com/nlohmann/json.git"
>>
>> -PV = "3.2.0+git${SRCPV}"
>> +PV = "3.3.0+git${SRCPV}"
>>
>> -SRCREV = "8c20571136f2d5351b379a06ad6591bd980880fe"
>> +SRCREV = "f1768a540a7b7c5cc30cdcd6be9e9ef91083719b"
>>
>> S = "${WORKDIR}/git"
>>
>> @@ -21,3 +21,9 @@ EXTRA_OECMAKE += "-DJSON_BuildTests=OFF"
>> RDEPENDS_${PN}-dev = ""
>>
>> BBCLASSEXTEND = "native nativesdk"
>> +
>> +# other packages commonly reference the file directly as "json.hpp"
>> +# create symlink to allow this usage
>> +do_install_append() {
>> + ln -s nlohmann/json.hpp ${D}${includedir}/json.hpp
>> +}
>> --
>> 2.17.1
>>
prev parent reply other threads:[~2018-10-11 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 17:14 [meta-oe][PATCH] nlohmann-json: Add symlink to json.hpp and update to 3.3.0 James Feist
2018-10-11 20:33 ` Khem Raj
2018-10-11 20:41 ` Feist, James [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=6ddccc38-c256-1ab9-e01f-360febf6cfe9@linux.intel.com \
--to=james.feist@linux.intel.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.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.