From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: Joshua Lock <joshua.g.lock@linux.intel.com>, yocto@yoctoproject.org
Cc: richard.purdie@intel.com
Subject: Re: [[PATCH][yocto-autobuilder] 1/2] buildsteps/CreateAutoConf.py: Add support for specify MACHINE by build prop
Date: Wed, 18 Jan 2017 12:20:52 -0600 [thread overview]
Message-ID: <587FB204.80200@linux.intel.com> (raw)
In-Reply-To: <1484763187.3137.1.camel@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2177 bytes --]
On 01/18/2017 12:13 PM, Joshua Lock wrote:
> On Mon, 2017-01-16 at 10:25 -0600, Aníbal Limón wrote:
>> Sometimes is a good idea to could specify a machine to build via a
>> build
>> property.
>
> Why's that? I can guess but the commit log should really tell me what
> the motivation for the change is.
In the performance buildset patch [1] there is a build property to
specify the machine via the web interface, without this change the
machine is overwrite to predefined in the buildset.
Cheers,
alimon
[1]
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/tree/buildset-config.yocto-qa/nightly-oe-build-perf-test.conf?h=contrib/alimon/devel&id=6c25a37cd801f2cdecc21c76499625a117e08ff7#n7
>
>>
>> Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
>> ---
>> .../site-
>> packages/autobuilder/buildsteps/CreateAutoConf.py | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/lib/python2.7/site-
>> packages/autobuilder/buildsteps/CreateAutoConf.py
>> b/lib/python2.7/site-
>> packages/autobuilder/buildsteps/CreateAutoConf.py
>> index 021f542..7915dd5 100644
>> --- a/lib/python2.7/site-
>> packages/autobuilder/buildsteps/CreateAutoConf.py
>> +++ b/lib/python2.7/site-
>> packages/autobuilder/buildsteps/CreateAutoConf.py
>> @@ -174,7 +174,11 @@ class CreateAutoConf(ShellCommand):
>> fout = fout + 'baselib = \\042${@d.getVar(\\047B
>> ASE_LIB_tune-\\047 + (d.getVar(\\047DEFAULTTUNE\\047, True) or
>> \\047INVALID\\047), True) or \\047lib\\047}\\042 \n'
>> if self.distro == "poky-rt":
>> fout = fout +
>> 'PREFERRED_PROVIDER_virtual/kernel="linux-yocto-rt" \n'
>> - machine=self.machine
>> + machine=self.getProperty('custom_machine')
>> + if machine:
>> + self.machine = machine
>> + else:
>> + machine = self.machine
>> if layerversion is not None and int(layerversion) > 1:
>> if self.machine == "atom-pc":
>> machine = self.machine.replace("atom-pc",
>> "genericx86")
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-01-18 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 16:25 [[PATCH][yocto-autobuilder] 1/2] buildsteps/CreateAutoConf.py: Add support for specify MACHINE by build prop Aníbal Limón
2017-01-16 16:25 ` [[PATCH][yocto-autobuilder] 2/2] buildset-config.yocto-qa: Add nightly-oe-build-perf-test buildset Aníbal Limón
2017-01-18 18:13 ` [[PATCH][yocto-autobuilder] 1/2] buildsteps/CreateAutoConf.py: Add support for specify MACHINE by build prop Joshua Lock
2017-01-18 18:20 ` Aníbal Limón [this message]
2017-01-19 10:37 ` Beth 'pidge' Flanagan
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=587FB204.80200@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=joshua.g.lock@linux.intel.com \
--cc=richard.purdie@intel.com \
--cc=yocto@yoctoproject.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.