From: Adrian Bunk <bunk@stusta.de>
To: Lei YU <mine260309@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] googletest: move to release 1.10.0
Date: Mon, 25 Nov 2019 05:08:31 +0200 [thread overview]
Message-ID: <20191125030831.GA16252@localhost> (raw)
In-Reply-To: <1574315133-73046-1-git-send-email-mine260309@gmail.com>
On Thu, Nov 21, 2019 at 01:45:33PM +0800, Lei YU wrote:
> The googletest recipe was using 1.8.1 tag, and in the recipe it was
> using the git revision instead of the tag release.
>
> Rename it to googletest_git.bb and use the 1.10.0 release revision to
> get the latest release.
>...
When removing the version from the recipe name you have to set PV manually.
> --- /dev/null
> +++ b/meta-oe/recipes-test/googletest/googletest_git.bb
> @@ -0,0 +1,21 @@
> +DESCRIPTION = "Google's framework for writing C++ tests"
> +HOMEPAGE = "https://github.com/google/googletest"
> +SECTION = "libs"
> +LICENSE = "BSD-3-Clause"
> +LIC_FILES_CHKSUM = "file://googlemock/LICENSE;md5=cbbd27594afd089daa160d3a16dd515a \
> + file://googletest/LICENSE;md5=cbbd27594afd089daa160d3a16dd515a"
> +
> +PROVIDES += "gmock gtest"
> +
> +S = "${WORKDIR}/git"
> +SRCREV = "703bd9caab50b139428cea1aaff9974ebee5742e"
> +SRC_URI = "git://github.com/google/googletest.git"
> +
> +inherit cmake
> +
> +ALLOW_EMPTY_${PN} = "1"
> +ALLOW_EMPTY_${PN}-dbg = "1"
> +
> +RDEPENDS_${PN}-dev += "${PN}-staticdev"
> +
> +BBCLASSEXTEND = "native nativesdk"
cu
Adrian
next prev parent reply other threads:[~2019-11-25 3:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 5:45 [meta-oe][PATCH] googletest: move to release 1.10.0 Lei YU
2019-11-25 3:08 ` Adrian Bunk [this message]
2019-11-25 3:41 ` Lei YU
2019-11-25 5:03 ` Khem Raj
2019-11-29 16:44 ` Peter Kjellerstedt
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=20191125030831.GA16252@localhost \
--to=bunk@stusta.de \
--cc=mine260309@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox