From: "Tom Hochstein" <tom.hochstein@nxp.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: gtest and gmock not added to SDK
Date: Fri, 22 May 2020 15:50:32 -0700 [thread overview]
Message-ID: <22249.1590187832432063263@lists.openembedded.org> (raw)
In-Reply-To: <CAJ86T=VDtvME1EVBfVOBW5U+84dkpD03ksHJdik15CSOG84Xgg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]
On Fri, May 22, 2020 at 03:33 PM, Andre McCurdy wrote:
>
> On Fri, May 22, 2020 at 2:29 PM Otavio Salvador
> <otavio.salvador@ossystems.com.br> wrote:
>
>> On Fri, May 22, 2020 at 5:48 PM Tom Hochstein <tom.hochstein@nxp.com>
>> wrote:
>>
>>> The gtest and gmock packages provided by googletest are not added to the
>>> SDK by default. I assume it is because the googletest main package is
>>> empty?
>>
>>
>
> Are you including googletest in the image used to create the SDK or
> gmock and gtest?
>
> It looks like gmock and gtest are only mentioned in the googletest
> recipe as PROVIDES, so they are aliases for build time dependencies
> only. For run time dependencies you should use googletest.
Right, I should have mentioned that. I have a DEPENDS on gtest for a package in my image. To fix the SDK, I added an RDEPENDS on googletest from the same package.
>
>
>
>>
>>> I added an RDEPENDS_${PN} from the dependent package to fix it. Is there a
>>> better solution?
>>
>> You can change the packages to have their `-dev` to rdepends on
>> `gtest/gmock-dev` for example.
>>
>> --
>> Otavio Salvador O.S. Systems
>> http://www.ossystems.com.br http://code.ossystems.com.br
>> Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
>
>
[-- Attachment #2: Type: text/html, Size: 1568 bytes --]
next prev parent reply other threads:[~2020-05-22 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 20:48 gtest and gmock not added to SDK Tom Hochstein
2020-05-22 21:29 ` [OE-core] " Otavio Salvador
2020-05-22 22:33 ` Andre McCurdy
2020-05-22 22:50 ` Tom Hochstein [this message]
2020-05-22 23:05 ` Andre McCurdy
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=22249.1590187832432063263@lists.openembedded.org \
--to=tom.hochstein@nxp.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 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.