From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org,
benjamin.esquivel@intel.com,
"Aníbal Limón" <limon.anibal@gmail.com>
Subject: Re: [PATCH 18/20] classes/populate_sdk_ext: Add SDK_EXT_TARGET_MANIFEST and SDK_EXT_HOST_MANIFEST
Date: Tue, 2 Feb 2016 16:13:12 -0600 [thread overview]
Message-ID: <56B129F8.9000402@linux.intel.com> (raw)
In-Reply-To: <1685931.lfZTPyxPBX@peggleto-mobl.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 4679 bytes --]
On 02/02/2016 04:06 PM, Paul Eggleton wrote:
> On Tue, 02 Feb 2016 16:05:06 Aníbal Limón wrote:
>> On 02/02/2016 03:52 PM, Paul Eggleton wrote:
>>> On Tue, 02 Feb 2016 09:14:21 Aníbal Limón wrote:
>>>> From: Aníbal Limón <limon.anibal@gmail.com>
>>>>
>>>> Extensible SDK needs to point to the correct manifest so add
>>>> SDK_EXT_TARGET_MANIFEST and SDK_EXT_HOST_MANIFEST variables.
>>>>
>>>> oeqa/oetest.py: Fix SDKExtTestContext for load the correct manifests.
>>>>
>>>> Signed-off-by: Aníbal Limón <limon.anibal@gmail.com>
>>>> ---
>>>>
>>>> meta/classes/populate_sdk_ext.bbclass | 3 +++
>>>> meta/lib/oeqa/oetest.py | 11 +++++++++--
>>>> 2 files changed, 12 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/meta/classes/populate_sdk_ext.bbclass
>>>> b/meta/classes/populate_sdk_ext.bbclass index fc96a4b..27dc030 100644
>>>> --- a/meta/classes/populate_sdk_ext.bbclass
>>>> +++ b/meta/classes/populate_sdk_ext.bbclass
>>>> @@ -43,6 +43,9 @@ B_task-populate-sdk-ext = "${SDK_DIR}"
>>>>
>>>> TOOLCHAINEXT_OUTPUTNAME = "${SDK_NAME}-toolchain-ext-${SDK_VERSION}"
>>>> TOOLCHAIN_OUTPUTNAME_task-populate-sdk-ext =
>>>> "${TOOLCHAINEXT_OUTPUTNAME}"
>>>>
>>>> +SDK_EXT_TARGET_MANIFEST =
>>>> "${SDK_DEPLOY}/${TOOLCHAINEXT_OUTPUTNAME}.target.manifest"
>>>> +SDK_EXT_HOST_MANIFEST =
>>>> "${SDK_DEPLOY}/${TOOLCHAINEXT_OUTPUTNAME}.host.manifest" +
>>>>
>>>> SDK_TITLE_task-populate-sdk-ext = "${@d.getVar('DISTRO_NAME', True) or
>>>>
>>>> d.getVar('DISTRO', True)} Extensible SDK"
>>>>
>>>> python copy_buildsystem () {
>>>>
>>>> diff --git a/meta/lib/oeqa/oetest.py b/meta/lib/oeqa/oetest.py
>>>> index 6beb6c5..c951989 100644
>>>> --- a/meta/lib/oeqa/oetest.py
>>>> +++ b/meta/lib/oeqa/oetest.py
>>>>
>>>> @@ -382,14 +382,18 @@ class SDKTestContext(TestContext):
>>>> self.sdktestdir = sdktestdir
>>>> self.sdkenv = sdkenv
>>>>
>>>> + if not hasattr(self, 'target_manifest_name'):
>>>> + self.target_manifest_name = "SDK_TARGET_MANIFEST"
>>>>
>>>> try:
>>>> - with open(d.getVar("SDK_TARGET_MANIFEST", True)) as f:
>>>>
>>>> + with open(d.getVar(self.target_manifest_name, True)) as f:
>>>> self.pkgmanifest = f.read()
>>>>
>>>> except IOError as e:
>>>> bb.fatal("No package manifest file found. Did you build the
>>>> sdk
>>>>
>>>> image?\n%s" % e)
>>>>
>>>> + if not hasattr(self, 'host_manifest_name'):
>>>> + self.host_manifest_name = "SDK_HOST_MANIFEST"
>>>>
>>>> try:
>>>> - with open(d.getVar("SDK_HOST_MANIFEST", True)) as f:
>>>>
>>>> + with open(d.getVar(self.host_manifest_name, True)) as f:
>>>> self.hostpkgmanifest = f.read()
>>>>
>>>> except IOError as e:
>>>> bb.fatal("No host package manifest file found. Did you build
>>>>
>>>> the sdk image?\n%s" % e) @@ -406,6 +410,9 @@ class
>>>>
>>>> SDKTestContext(TestContext):
>>>> class SDKExtTestContext(SDKTestContext):
>>>> def __init__(self, d, sdktestdir, sdkenv):
>>>> + self.target_manifest_name = "SDK_EXT_TARGET_MANIFEST"
>>>> + self.host_manifest_name = "SDK_EXT_HOST_MANIFEST"
>>>> +
>>>>
>>>> super(SDKExtTestContext, self).__init__(d, sdktestdir, sdkenv)
>>>>
>>>> self.sdkextfilesdir =
>>>> os.path.join(os.path.dirname(os.path.abspath(
>>>
>>> I really don't like the idea of passing the variable name here rather than
>>> values. However, besides that, the manifest is always the SDK name plus
>>> .host.manifest or .target.manifest - do we even need to pass separate
>>> names? All you should need is the name of the SDK i.e. the value of
>>> TOOLCHAINEXT_OUTPUTNAME.
>>
>> I prefer to have explicit value and construct them into one place
>> instead of have many name constructions like you said to use
>> TOOLCHAINEXT_OUTPUTNAME and suppose that always be end with .{host,
>> target}.manifest.
>
> When you add a variable to populate_sdk_ext.bbclass, it isn't just defined for
> the ext SDK - it's defined for every image recipe. I want to try to avoid
> defining additional variables and thus expanding the environment where we don't
> really need to.
I guess two more variable expansions gives you no more/less performance
and also gives you the possibility to have the thing set in a clean manner,
>
> The naming of the manifest is something we can rely on, because external tools
> need to be able to.
May be now, :).
alimon
>
> Cheers,
> Paul
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-02-02 22:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 15:14 [PATCH 00/20] Add Extensible SDK test suite Aníbal Limón
2016-02-02 15:14 ` [PATCH 01/20] testimage: Modularize helper functions for get test lists Aníbal Limón
2016-02-02 15:14 ` [PATCH 02/20] classes/testsdk: Add new class testsdk Aníbal Limón
2016-02-02 15:14 ` [PATCH 03/20] classes/testimage: Add defeault inherit for testsdk Aníbal Limón
2016-02-02 15:14 ` [PATCH 04/20] populate_sdk_ext: Set TOOLCHAINEXT_OUTPUTNAME Aníbal Limón
2016-02-02 15:14 ` [PATCH 05/20] get_test_suites: Add sdkext type for load test suites Aníbal Limón
2016-02-02 15:14 ` [PATCH 06/20] classes/testsdk: Add testsdkext task only install Aníbal Limón
2016-02-02 15:14 ` [PATCH 07/20] bb/fetch2: Move export_proxies function from wget to utils Aníbal Limón
2016-02-02 15:14 ` [PATCH 08/20] classes/testsdk: Add call to export_proxies on testsdkext Aníbal Limón
2016-02-02 15:14 ` [PATCH 09/20] toolchain-shar-extract.sh: Add proxy variable to new env Aníbal Limón
2016-02-02 15:14 ` [PATCH 10/20] testimage/testsdk: Modularize TestContext Aníbal Limón
2016-02-02 15:14 ` [PATCH 11/20] testimage/testsdk: Move get test suites routine inside TestContext Aníbal Limón
2016-02-02 15:14 ` [PATCH 12/20] oetest.py/TestContext: Move loadTests and runTests inside it Aníbal Limón
2016-02-02 15:14 ` [PATCH 13/20] oeqa/oetest.py: Fix missing oeqa.runtime import Aníbal Limón
2016-02-02 21:25 ` Paul Eggleton
2016-02-02 21:31 ` Aníbal Limón
2016-02-02 21:32 ` Paul Eggleton
2016-02-02 15:14 ` [PATCH 14/20] classes/testsdk: Add function run_test_context Aníbal Limón
2016-02-02 15:14 ` [PATCH 15/20] classes/populate_sdk_ext: Add OE_SDK_EXT_SILENT env variable Aníbal Limón
2016-02-02 21:19 ` Paul Eggleton
2016-02-02 21:23 ` Aníbal Limón
2016-02-02 21:25 ` Paul Eggleton
2016-02-02 21:30 ` Aníbal Limón
2016-02-02 21:31 ` Paul Eggleton
2016-02-02 21:38 ` Aníbal Limón
2016-02-02 21:40 ` Paul Eggleton
2016-02-02 21:47 ` Aníbal Limón
2016-02-02 21:49 ` Paul Eggleton
2016-02-02 15:14 ` [PATCH 16/20] classes/testsdk: Add compatibility SDK testsuite to eSDK Aníbal Limón
2016-02-02 15:14 ` [PATCH 17/20] testsdkext: Add skeleton for support Extensible SDK tests Aníbal Limón
2016-02-02 15:14 ` [PATCH 18/20] classes/populate_sdk_ext: Add SDK_EXT_TARGET_MANIFEST and SDK_EXT_HOST_MANIFEST Aníbal Limón
2016-02-02 21:52 ` Paul Eggleton
2016-02-02 22:05 ` Aníbal Limón
2016-02-02 22:06 ` Paul Eggleton
2016-02-02 22:13 ` Aníbal Limón [this message]
2016-02-02 22:15 ` Paul Eggleton
2016-02-02 15:14 ` [PATCH 19/20] oeqa/sdkext: Add devtool basic tests for eSDK Aníbal Limón
2016-02-02 22:03 ` Paul Eggleton
2016-02-02 22:14 ` Aníbal Limón
2016-02-02 15:14 ` [PATCH 20/20] classes/testsdk: Add help information on how to run tests Aníbal Limón
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=56B129F8.9000402@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=benjamin.esquivel@intel.com \
--cc=limon.anibal@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox