Re: [yocto] Files missing from SDK

2017-03-07 Thread Gary Thomas 

On 2017-03-07 23:26, Paul Eggleton wrote:

On Tuesday, 7 March 2017 5:44:05 PM NZDT Gary Thomas wrote:

On 2017-03-06 21:56, Paul Eggleton wrote:

On Tuesday, 7 March 2017 2:28:22 AM NZDT Gary Thomas wrote:

On 2017-03-06 13:22, Burton, Ross wrote:

On 3 March 2017 at 06:39, Gary Thomas 
> wrote:

I'm trying to build SDKs for my board, both the native style
using populate_sdk_ext as well as including the SDK packages
in my image.  My image includes some extended libraries of
my own packaging (am335x-pru-support) that I need to get into
these SDKs.  This package (via debian renaming) turns into

  libprussdrv-dbg - 2016-08-30-r0.23 - am335x-pru-support version
  2016-08-30-r0 - Debugging files libprussdrv-dev - 2016-08-30-r0.23
  - am335x-pru-support version 2016-08-30-r0 - Development files
  libprussdrv-staticdev - 2016-08-30-r0.23 - am335x-pru-support
  version 2016-08-30-r0 - Development files (St) libprussdrv1 -
  2016-08-30-r0.23 - am335x-pru-support version 2016-08-30-r0>

On my board/image, I can get the files I need but only if I manually
include libprussdrv-dev>

  # opkg files libprussdrv-dev | sort
  /usr/bin/pasm
  /usr/include/pruss/
  /usr/include/pruss/pruss_intc_mapping.h
  /usr/include/pruss/prussdrv.h
  /usr/lib/libprussdrv.so

How can I get these automatically added to my SDK images?  To build
the

board SDK, I'm adding these packages to my image:
  CORE_IMAGE_EXTRA_INSTALL = "packagegroup-core-sdk
  packagegroup-core-standalone-sdk-target">

I suppose I could add libprussdrv-dev to that list, but I'd like it
a
bit more automated.>

For the native SDK, I tried adding this to local.conf:
  TOOLCHAIN_HOST_TASK_append = " nativesdk-am335x-pru-support"

which only got me the 'pasm' tool in my sysroot, but nothing else.

If libprussdrv1 is in your image then the -dev package should be pulled
into your SDK images, assuming that you have IMAGE_FEATURES+=dev-pkgs
already.


Thanks, that did it for the embedded SDK


That shouldn't actually be necessary. IMAGE_FEATURES controls what goes
into the image, adding dev-pkgs to that is going to include those in the
image, not just the SDK. We have a SDKIMAGE_FEATURES and the default
value of that includes dev-pkgs. If libprussdrv1 is in the image and
SDKIMAGE_FEATURES is at the default (or otherwise includes dev-pkgs) I
have to say I'm not sure what would be preventing this from working.


The same should mean that standalone SDKs (populate_sdk-style) contain
the
headers too.  Worse case, TOOLCHAIN_TARGET_TASK_append = "
libprussdrvi-dev".


Sadly, this still doesn't work.  With the TOOLCHAIN* line above, I get:
   ERROR: Nothing RPROVIDES 'libprussdrv1-dev'

Without it, no changes - the bits are still missing.


As with almost all variables, in TOOLCHAIN_TARGET_TASK you want the
recipe-
space name of the package, not the final (post debian-renamed) name.


I tried that as well, and it got a lot farther along, but failed in
the final steps:

ERROR: uninative-tarball-1.0-r0 do_populate_sdk: Unable to install packages.
Command
'/build/p8701_2016-10-22/tmp/work/x86_64-nativesdk-amltdsdk-linux/uninative
-tarball/1.0-r0/recipe-sysroot-native/usr/bin/opkg --volatile-cache -f
/build/p8701_2016-10-22/tmp/work/x86_64-nativesdk-amltdsdk-linux/uninative-
tarball/1.0-r0/opkg.conf -t
/build/p8701_2016-10-22/tmp/work/x86_64-nativesdk-amltdsdk-linux/uninative-
tarball/1.0-r0/temp/ipktemp/ -o
/build/p8701_2016-10-22/tmp/work/x86_64-nativesdk-amltdsdk-linux/uninative-
tarball/1.0-r0/sdk/image/opt/amltd/2.2+snapshot/sysroots/none
--force_postinstall --prefer-arch-to-version   install libprussdrv-dev'
returned 255: Collected errors:
  * opkg_prepare_url_for_install: Couldn't find anything to satisfy
'libprussdrv-dev'.

ERROR: uninative-tarball-1.0-r0 do_populate_sdk: Function failed:
do_populate_sdk


It sounds like you're setting TOOLCHAIN_TARGET_TASK at the configuration
level, thus affecting uninative-tarball as well. Set it in your image recipe
(or a class / inc file used from there) and that should work.


Thanks, that solved that problem.  I'm now getting the missing files in my
[host] SDK, getting much closer.

I'm still missing some others though - files from 
[meta-ti]recipes-ti/devtools/ti-cgt-pru_2.1.4.bb
I am getting the appropriate files when I build using bitbake, as well as
on my target when I include the sdk components, just not when I build a
host SDK using -c populate_sdk_ext

That's a very differently packaged recipe (lots of magic), so I'll take it up 
with the meta-ti list

Thanks for your help

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org

Re: [yocto] Files missing from SDK

2017-03-07 Thread Paul Eggleton 
On Tuesday, 7 March 2017 5:44:05 PM NZDT Gary Thomas wrote:
> On 2017-03-06 21:56, Paul Eggleton wrote:
> > On Tuesday, 7 March 2017 2:28:22 AM NZDT Gary Thomas wrote:
> >> On 2017-03-06 13:22, Burton, Ross wrote:
> >>> On 3 March 2017 at 06:39, Gary Thomas  > > wrote:
> >>> I'm trying to build SDKs for my board, both the native style
> >>> using populate_sdk_ext as well as including the SDK packages
> >>> in my image.  My image includes some extended libraries of
> >>> my own packaging (am335x-pru-support) that I need to get into
> >>> these SDKs.  This package (via debian renaming) turns into
> >>> 
> >>>   libprussdrv-dbg - 2016-08-30-r0.23 - am335x-pru-support version
> >>>   2016-08-30-r0 - Debugging files libprussdrv-dev - 2016-08-30-r0.23
> >>>   - am335x-pru-support version 2016-08-30-r0 - Development files
> >>>   libprussdrv-staticdev - 2016-08-30-r0.23 - am335x-pru-support
> >>>   version 2016-08-30-r0 - Development files (St) libprussdrv1 -
> >>>   2016-08-30-r0.23 - am335x-pru-support version 2016-08-30-r0>
> >>> 
> >>> On my board/image, I can get the files I need but only if I manually
> >>> include libprussdrv-dev>
> >>> 
> >>>   # opkg files libprussdrv-dev | sort
> >>>   /usr/bin/pasm
> >>>   /usr/include/pruss/
> >>>   /usr/include/pruss/pruss_intc_mapping.h
> >>>   /usr/include/pruss/prussdrv.h
> >>>   /usr/lib/libprussdrv.so
> >>> 
> >>> How can I get these automatically added to my SDK images?  To build
> >>> the
> >>> 
> >>> board SDK, I'm adding these packages to my image:
> >>>   CORE_IMAGE_EXTRA_INSTALL = "packagegroup-core-sdk
> >>>   packagegroup-core-standalone-sdk-target">
> >>> 
> >>> I suppose I could add libprussdrv-dev to that list, but I'd like it
> >>> a
> >>> bit more automated.>
> >>> 
> >>> For the native SDK, I tried adding this to local.conf:
> >>>   TOOLCHAIN_HOST_TASK_append = " nativesdk-am335x-pru-support"
> >>> 
> >>> which only got me the 'pasm' tool in my sysroot, but nothing else.
> >>> 
> >>> If libprussdrv1 is in your image then the -dev package should be pulled
> >>> into your SDK images, assuming that you have IMAGE_FEATURES+=dev-pkgs
> >>> already.
> >> 
> >> Thanks, that did it for the embedded SDK
> > 
> > That shouldn't actually be necessary. IMAGE_FEATURES controls what goes
> > into the image, adding dev-pkgs to that is going to include those in the
> > image, not just the SDK. We have a SDKIMAGE_FEATURES and the default
> > value of that includes dev-pkgs. If libprussdrv1 is in the image and
> > SDKIMAGE_FEATURES is at the default (or otherwise includes dev-pkgs) I
> > have to say I'm not sure what would be preventing this from working.
> > 
> >>> The same should mean that standalone SDKs (populate_sdk-style) contain
> >>> the
> >>> headers too.  Worse case, TOOLCHAIN_TARGET_TASK_append = "
> >>> libprussdrvi-dev".
> >> 
> >> Sadly, this still doesn't work.  With the TOOLCHAIN* line above, I get:
> >>ERROR: Nothing RPROVIDES 'libprussdrv1-dev'
> >> 
> >> Without it, no changes - the bits are still missing.
> > 
> > As with almost all variables, in TOOLCHAIN_TARGET_TASK you want the
> > recipe-
> > space name of the package, not the final (post debian-renamed) name.
> 
> I tried that as well, and it got a lot farther along, but failed in
> the final steps:
> 
> ERROR: uninative-tarball-1.0-r0 do_populate_sdk: Unable to install packages.
> Command
> '/build/p8701_2016-10-22/tmp/work/x86_64-nativesdk-amltdsdk-linux/uninative
> -tarball/1.0-r0/recipe-sysroot-native/usr/bin/opkg --volatile-cache -f
> /build/p8701_2016-10-22/tmp/work/x86_64-nativesdk-amltdsdk-linux/uninative-
> tarball/1.0-r0/opkg.conf -t
> /build/p8701_2016-10-22/tmp/work/x86_64-nativesdk-amltdsdk-linux/uninative-
> tarball/1.0-r0/temp/ipktemp/ -o
> /build/p8701_2016-10-22/tmp/work/x86_64-nativesdk-amltdsdk-linux/uninative-
> tarball/1.0-r0/sdk/image/opt/amltd/2.2+snapshot/sysroots/none
> --force_postinstall --prefer-arch-to-version   install libprussdrv-dev'
> returned 255: Collected errors:
>   * opkg_prepare_url_for_install: Couldn't find anything to satisfy
> 'libprussdrv-dev'.
> 
> ERROR: uninative-tarball-1.0-r0 do_populate_sdk: Function failed:
> do_populate_sdk

It sounds like you're setting TOOLCHAIN_TARGET_TASK at the configuration 
level, thus affecting uninative-tarball as well. Set it in your image recipe 
(or a class / inc file used from there) and that should work.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Intoducting myself: Applying for Outreachy

2017-03-07 Thread akuster808 

Soumya,

Are you trying to apply for the intership? You may want to take a look at

https://www.yoctoproject.org/outreachy-internship

Not sure how that differs from the outreach program.

Maybe Jefro or Tracy can clarify.

regards,

Armin



On 03/07/2017 09:08 AM, Leonardo Sandoval wrote:

On Tue, 2017-03-07 at 22:18 +0530, Soumya Gupta wrote:

Hi all,


My name is Soumya, an I am a final year Engineering undergraduate
student from New Delhi. I would love to work to contribute to Yocto
for the summer.


I have been coding in Python for the past year and I am quite at ease
with the same. It states on the Outreachy page, that there is a
project relating to the building of autobuilders. I want to work on
the same.

can you point to that page?

There is an autobuilder repo at git.yoctoproject.org, perhaps you can
start looking there.


Being a newbie, it would be great, if someone could guide me on the
right path here

Thanks already


Best,
Soumya Atul Gupta
Final Year Undergraduate Student, ECE
Netaji Subhas Institute of Technology
New Delhi, India


--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto




--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Not able to create a new BSP layer using yocto-bsp script

2017-03-07 Thread Leonardo Sandoval 
On Tue, 2017-03-07 at 09:15 +, Eswaran Vinothkumar (BEG/PJ-IOT-EL)
wrote:

> 
> I tried using both the master andmorty-16.0.1  branches of poky.
> 

Can you try the same yocto-bsp command from master? If you have the same
issue, please report it on bugzilla.yoctoproject.org

>  
> 
>  
> 
> Mit freundlichen Grüßen / Best regards 
> Vinothkumar Eswaran
> 
> 
> 
>  
> 
> 
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Intoducting myself: Applying for Outreachy

2017-03-07 Thread Soumya Gupta 
Hi,

Please look under Yocto under Participating Organisations

Thank you

Best,
Soumya Atul Gupta
Final Year Undergraduate Student, ECE
Netaji Subhas Institute of Technology
New Delhi, India


On Tue, Mar 7, 2017 at 10:38 PM, Leonardo Sandoval <
leonardo.sandoval.gonza...@linux.intel.com> wrote:

> On Tue, 2017-03-07 at 22:18 +0530, Soumya Gupta wrote:
> > Hi all,
> >
> >
> > My name is Soumya, an I am a final year Engineering undergraduate
> > student from New Delhi. I would love to work to contribute to Yocto
> > for the summer.
> >
> >
> > I have been coding in Python for the past year and I am quite at ease
> > with the same. It states on the Outreachy page, that there is a
> > project relating to the building of autobuilders. I want to work on
> > the same.
>
> can you point to that page?
>
> There is an autobuilder repo at git.yoctoproject.org, perhaps you can
> start looking there.
>
> >
> > Being a newbie, it would be great, if someone could guide me on the
> > right path here
> >
> > Thanks already
> >
> >
> > Best,
> > Soumya Atul Gupta
> > Final Year Undergraduate Student, ECE
> > Netaji Subhas Institute of Technology
> > New Delhi, India
> >
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Intoducting myself: Applying for Outreachy

2017-03-07 Thread Leonardo Sandoval 
On Tue, 2017-03-07 at 22:18 +0530, Soumya Gupta wrote:
> Hi all, 
> 
> 
> My name is Soumya, an I am a final year Engineering undergraduate
> student from New Delhi. I would love to work to contribute to Yocto
> for the summer. 
> 
> 
> I have been coding in Python for the past year and I am quite at ease
> with the same. It states on the Outreachy page, that there is a
> project relating to the building of autobuilders. I want to work on
> the same.  

can you point to that page?

There is an autobuilder repo at git.yoctoproject.org, perhaps you can
start looking there.

> 
> Being a newbie, it would be great, if someone could guide me on the
> right path here
> 
> Thanks already 
> 
> 
> Best,
> Soumya Atul Gupta
> Final Year Undergraduate Student, ECE
> Netaji Subhas Institute of Technology
> New Delhi, India
> 
> 
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Intoducting myself: Applying for Outreachy

2017-03-07 Thread Soumya Gupta 
Hi all,

My name is Soumya, an I am a final year Engineering undergraduate student
from New Delhi. I would love to work to contribute to Yocto for the summer.

I have been coding in Python for the past year and I am quite at ease with
the same. It states on the Outreachy page, that there is a project relating
to the building of autobuilders. I want to work on the same.

Being a newbie, it would be great, if someone could guide me on the right
path here
Thanks already


Best,
Soumya Atul Gupta
Final Year Undergraduate Student, ECE
Netaji Subhas Institute of Technology
New Delhi, India
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [qa-tools][PATCH v2] testopia_update: Add option to define test plan

2017-03-07 Thread Aníbal Limón 
Ack

On 03/07/2017 07:58 AM, jose.perez.carra...@linux.intel.com wrote:
> From: Jose Perez Carranza 
> 
> There are cases where the test plan and the product name are not equal hence
> an option is added to handle those cases and define the test plan to work on.
> 
> Signed-off-by: Jose Perez Carranza 
> ---
>  testopia_update.py  | 13 +---
>  testopia_update/product/__init__.py | 40 
> -
>  2 files changed, 32 insertions(+), 21 deletions(-)
> 
> diff --git a/testopia_update.py b/testopia_update.py
> index 9b35188..044074a 100755
> --- a/testopia_update.py
> +++ b/testopia_update.py
> @@ -70,6 +70,9 @@ def get_args():
>  dest="project_revision", help='SCM Revision of the project.')
>  parser.add_argument('--project-date', required=False,
>  dest="project_date", help='SCM version/revision date of the 
> project.')
> +parser.add_argument('--test-plan', required=False,
> +dest="plan_name", help='Name of the test plan of the product, used 
> when \
> +test plan name is different from product 
> name.')
>  
>  parser.add_argument('--results-log', required=False,
>  dest="results_log", help='Results log.')
> @@ -115,8 +118,12 @@ if __name__ == '__main__':
>  if not os.path.exists(opts.store_location):
>  os.makedirs(opts.store_location)
>  
> +kwargs = {}
> +if args.plan_name:
> +kwargs['plan_name'] = args.plan_name
> +
>  testopia = Testopia(opts.username, opts.password, opts.url, 
> sslverify=False)
> -products = get_products(testopia, opts, logger, config)
> +products = get_products(testopia, opts, logger, config, **kwargs)
>  
>  if args.list_products:
>  print("List of available products: \n")
> @@ -141,8 +148,8 @@ if __name__ == '__main__':
>  
>  test_plan = product.get_test_plan(args.branch_name)
>  if not test_plan:
> -logger.error("%s: Test plan for product %s and branch %s not 
> exists."\
> - % (sys.argv[0], args.product_name, args.branch_name))
> +logger.error("%s: Test plan %s for product %s and branch %s not 
> exists."\
> + % (sys.argv[0], product.plan ,args.product_name, 
> args.branch_name))
>  
>  sys.exit(1)
>  
> diff --git a/testopia_update/product/__init__.py 
> b/testopia_update/product/__init__.py
> index e401824..18b112e 100644
> --- a/testopia_update/product/__init__.py
> +++ b/testopia_update/product/__init__.py
> @@ -1,13 +1,17 @@
>  import re
>  
> -
>  class Product(object):
> -def __init__(self, testopia, opts, logger, config):
> +def __init__(self, testopia, opts, logger, config, **kwargs):
>  self.testopia = testopia
>  self.opts = opts
>  self.logger = logger
>  self.config = config
>  
> +if 'plan_name' in kwargs:
> +self.plan = kwargs['plan_name']
> +else:
> +self.plan = self.name
> +
>  def support(self, name):
>  if self.name == name:
>  return True
> @@ -16,11 +20,11 @@ class Product(object):
>  def get_test_plan(self, branch_name):
>  tp = None
>  
> -tp_name = '%s: %s branch' % (self.name, branch_name)
> +tp_name = '%s: %s branch' % (self.plan, branch_name)
>  
>  tp = self.testopia.testplan_list(name=tp_name)
>  if not tp:
> -tp_alt_name = '%s: %s branch' % (self.name, branch_name.lower())
> +tp_alt_name = '%s: %s branch' % (self.plan, branch_name.lower())
>  tp = self.testopia.testplan_list(name=tp_alt_name)
>  
>  if tp:
> @@ -68,7 +72,7 @@ class Product(object):
>  category_name, optional):
>  summary_alts = []
>  summary_alts.append('%s_%s_%s_%s' % (ttype, project_version,
> -category_name, self.name))
> +category_name, self.plan))
>  summary_alts.append('%s_%s_%s' % (ttype, project_version,
>  category_name))
>  summary_alts.append('%s_%s' % (ttype, category_name))
> @@ -186,7 +190,7 @@ class Product(object):
>  
>  return missing
>  
> -def get_products(testopia, opts, config, logger):
> +def get_products(testopia, opts, config, logger, **kwargs):
>  
>  
>  from . import bitbake
> @@ -204,18 +208,18 @@ def get_products(testopia, opts, config, logger):
>  
>  products = []
>  
> -products.append(bitbake.BitbakeProduct(testopia, opts, logger, config))
> -products.append(bsp_qemu.BSPQEMUProduct(testopia, opts, logger, config))
> -products.append(meta_yocto.MetaYoctoProduct(testopia, opts, logger, 
> config))
> -products.append(oe_core.OECoreProduct(testopia, opts, logger, config))
> -products.append(runtime.RuntimeProduct(testopia, opts, logger, config))
> -products.append(toaster.ToasterProduct(testopia, opts, logger, config))
> -products.append(adt.ADTProduct(testopia, opts, logger, config))
> -products.append(

[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, Mar. 7, 2017 8:00 AM US Pacific Time

2017-03-07 Thread Jolley, Stephen K 
Attendees: Stephen, Armin, Joshua, Stephano, Sona, Ross, Richard, Saul,



Agenda:



* Opens collection - 5 min (Stephen)

* Yocto Project status - 5 min (Stephen/team)

YP 2.3 M3 is being ready to be built.  Should build this week.

YP 2.2.1 was released 2 weeks ago.

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.3_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.3_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.3_Features

* Opens - 10 min

Sona - CII-badge - a quality requirement tool.  Might be good to use on YP. 
Link: https://bestpractices.coreinfrastructure.org/projects/765  Discussed pros 
and cons of using it for YP.  Sona will put bugs into bugzilla for any 
unresolved issues.

Sona - meta-spdxscanner layer questions - Most likely won't be in YP 2.3, but 
not a bad idea.

Richard - Need someone to step up and get licensing support for YP; after the 
loss of Beth.

* Team Sharing - 10 min


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:(503) 712-0534
*Cell:   (208) 244-4460
* Email:
stephen.k.jol...@intel.com
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [qa-tools][PATCH v2] testopia_update: Add option to define test plan

2017-03-07 Thread jose . perez . carranza 
From: Jose Perez Carranza 

There are cases where the test plan and the product name are not equal hence
an option is added to handle those cases and define the test plan to work on.

Signed-off-by: Jose Perez Carranza 
---
 testopia_update.py  | 13 +---
 testopia_update/product/__init__.py | 40 -
 2 files changed, 32 insertions(+), 21 deletions(-)

diff --git a/testopia_update.py b/testopia_update.py
index 9b35188..044074a 100755
--- a/testopia_update.py
+++ b/testopia_update.py
@@ -70,6 +70,9 @@ def get_args():
 dest="project_revision", help='SCM Revision of the project.')
 parser.add_argument('--project-date', required=False,
 dest="project_date", help='SCM version/revision date of the project.')
+parser.add_argument('--test-plan', required=False,
+dest="plan_name", help='Name of the test plan of the product, used 
when \
+test plan name is different from product 
name.')
 
 parser.add_argument('--results-log', required=False,
 dest="results_log", help='Results log.')
@@ -115,8 +118,12 @@ if __name__ == '__main__':
 if not os.path.exists(opts.store_location):
 os.makedirs(opts.store_location)
 
+kwargs = {}
+if args.plan_name:
+kwargs['plan_name'] = args.plan_name
+
 testopia = Testopia(opts.username, opts.password, opts.url, 
sslverify=False)
-products = get_products(testopia, opts, logger, config)
+products = get_products(testopia, opts, logger, config, **kwargs)
 
 if args.list_products:
 print("List of available products: \n")
@@ -141,8 +148,8 @@ if __name__ == '__main__':
 
 test_plan = product.get_test_plan(args.branch_name)
 if not test_plan:
-logger.error("%s: Test plan for product %s and branch %s not exists."\
- % (sys.argv[0], args.product_name, args.branch_name))
+logger.error("%s: Test plan %s for product %s and branch %s not 
exists."\
+ % (sys.argv[0], product.plan ,args.product_name, 
args.branch_name))
 
 sys.exit(1)
 
diff --git a/testopia_update/product/__init__.py 
b/testopia_update/product/__init__.py
index e401824..18b112e 100644
--- a/testopia_update/product/__init__.py
+++ b/testopia_update/product/__init__.py
@@ -1,13 +1,17 @@
 import re
 
-
 class Product(object):
-def __init__(self, testopia, opts, logger, config):
+def __init__(self, testopia, opts, logger, config, **kwargs):
 self.testopia = testopia
 self.opts = opts
 self.logger = logger
 self.config = config
 
+if 'plan_name' in kwargs:
+self.plan = kwargs['plan_name']
+else:
+self.plan = self.name
+
 def support(self, name):
 if self.name == name:
 return True
@@ -16,11 +20,11 @@ class Product(object):
 def get_test_plan(self, branch_name):
 tp = None
 
-tp_name = '%s: %s branch' % (self.name, branch_name)
+tp_name = '%s: %s branch' % (self.plan, branch_name)
 
 tp = self.testopia.testplan_list(name=tp_name)
 if not tp:
-tp_alt_name = '%s: %s branch' % (self.name, branch_name.lower())
+tp_alt_name = '%s: %s branch' % (self.plan, branch_name.lower())
 tp = self.testopia.testplan_list(name=tp_alt_name)
 
 if tp:
@@ -68,7 +72,7 @@ class Product(object):
 category_name, optional):
 summary_alts = []
 summary_alts.append('%s_%s_%s_%s' % (ttype, project_version,
-category_name, self.name))
+category_name, self.plan))
 summary_alts.append('%s_%s_%s' % (ttype, project_version,
 category_name))
 summary_alts.append('%s_%s' % (ttype, category_name))
@@ -186,7 +190,7 @@ class Product(object):
 
 return missing
 
-def get_products(testopia, opts, config, logger):
+def get_products(testopia, opts, config, logger, **kwargs):
 
 
 from . import bitbake
@@ -204,18 +208,18 @@ def get_products(testopia, opts, config, logger):
 
 products = []
 
-products.append(bitbake.BitbakeProduct(testopia, opts, logger, config))
-products.append(bsp_qemu.BSPQEMUProduct(testopia, opts, logger, config))
-products.append(meta_yocto.MetaYoctoProduct(testopia, opts, logger, 
config))
-products.append(oe_core.OECoreProduct(testopia, opts, logger, config))
-products.append(runtime.RuntimeProduct(testopia, opts, logger, config))
-products.append(toaster.ToasterProduct(testopia, opts, logger, config))
-products.append(adt.ADTProduct(testopia, opts, logger, config))
-products.append(crops.CROPSProduct(testopia, opts, logger, config))
-products.append(eclipse_plugin.EclipePluginProduct(testopia, opts, logger, 
config))
-products.append(esdk.eSDKProduct(testopia, opts, logger, config))
-products.append(kernel.KernelProduct(testopia, opts, logger, config))
-products.append(general_runtime.Genera

Re: [yocto] [meta-raspberrypi][PATCH] gstreamer1.0-omx: remove bbappend for version 1.2.0

2017-03-07 Thread Paul Barker 
On Mon,  6 Mar 2017 17:28:03 +0200
"Maxin B. John"  wrote:

> OE-Core rev: aa06a18d59eb391d1a7ace9daa0681bdf8daf17f
> removed gstreamer1.0-omx_1.2.0 recipe.
> 
> Signed-off-by: Maxin B. John 
> ---
>  ...o-acquire-buffer-when-src-pad-isn-t-activ.patch |  48 
>  .../0001-config-files-path.patch   | 137
> - .../0002-fix-decoder-flushing.patch
> |  16 --- .../0003-no-timeout-on-get-state.patch |  16 ---
>  ...erly-handle-drain-requests-while-flushing.patch |  69 ---
>  ...-gst_omx_video_dec_set_format-if-there-s-.patch |  30 -
>  ...-unref-allocator-after-getting-it-from-al.patch |  48 
>  ...mxvideodec-Use-gstglmemoryegl-for-the-RPi.patch | 115
> - .../gstreamer/gstreamer1.0-omx_1.2.0.bbappend
> |  14 --- 9 files changed, 493 deletions(-)
>  delete mode 100644
> recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0001-Don-t-try-to-acquire-buffer-when-src-pad-isn-t-activ.patch
> delete mode 100644
> recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0001-config-files-path.patch
> delete mode 100644
> recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0002-fix-decoder-flushing.patch
> delete mode 100644
> recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0003-no-timeout-on-get-state.patch
> delete mode 100644
> recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0004-Properly-handle-drain-requests-while-flushing.patch
> delete mode 100644
> recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0005-Don-t-abort-gst_omx_video_dec_set_format-if-there-s-.patch
> delete mode 100644
> recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0006-omxvideodec-unref-allocator-after-getting-it-from-al.patch
> delete mode 100644
> recipes-multimedia/gstreamer/gstreamer1.0-omx-1.2.0/0007-omxvideodec-Use-gstglmemoryegl-for-the-RPi.patch
> delete mode 100644
> recipes-multimedia/gstreamer/gstreamer1.0-omx_1.2.0.bbappend

I got a parse failure on all my scheduled builds last night. This patch
fixes the builds for me :)

Thanks,
Paul
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Not able to create a new BSP layer using yocto-bsp script

2017-03-07 Thread Eswaran Vinothkumar (BEG/PJ-IOT-EL) 
Hello,

I am trying to create a new bsp layer for a customized board.

After running the commands: Yocto-bsp create  ctp arm,

I am seeing the following errors:

evk1206@evk1206-VirtualBox:~/Projects/Yocto/build-ctp$ yocto-bsp create custom 
arm
Checking basic git connectivity...
Done.

Would you like to use the default (4.8) kernel? (y/n) [default: y] y
Do you need a new machine branch for this BSP (the alternative is to re-use an 
existing branch)? [y/n] [default: y] y
Getting branches from remote repo 
git://git.yoctoproject.org/linux-yocto-4.8.git...
Traceback (most recent call last):
  File "/home/evk1206/Projects/Yocto-CTP-2019/poky/scripts/yocto-bsp", line 
158, in 
ret = main()
  File "/home/evk1206/Projects/Yocto-CTP-2019/poky/scripts/yocto-bsp", line 
154, in main
return args.func(args)
  File "/home/evk1206/Projects/Yocto-CTP-2019/poky/scripts/yocto-bsp", line 67, 
in do_create_bsp
yocto_bsp_create(args.bspname, args.karch, scripts_path, bsp_output_dir, 
args.codedump, args.properties_file)
  File "/home/evk1206/Projects/Yocto-CTP-2019/poky/scripts/lib/bsp/engine.py", 
line 1617, in yocto_bsp_create
yocto_common_create(machine, arch, scripts_path, bsp_output_dir, codedump, 
properties_file, properties)
  File "/home/evk1206/Projects/Yocto-CTP-2019/poky/scripts/lib/bsp/engine.py", 
line 1584, in yocto_common_create
run_program_lines(program_lines, codedump)
  File "/home/evk1206/Projects/Yocto-CTP-2019/poky/scripts/lib/bsp/engine.py", 
line 1365, in run_program_lines
exec(buf)
  File "", line 82, in 
  File "/home/evk1206/Projects/Yocto-CTP-2019/poky/scripts/lib/bsp/engine.py", 
line 656, in invoke_deferred_choices
choices = input_line.gen_choices(context, checklist)
  File "/home/evk1206/Projects/Yocto-CTP-2019/poky/scripts/lib/bsp/engine.py", 
line 460, in gen_choices
choicepairs = self.gen_choices_list(context, checklist)
  File "/home/evk1206/Projects/Yocto-CTP-2019/poky/scripts/lib/bsp/engine.py", 
line 428, in gen_choices_list
choices = self.exec_listgen_fn(context)
  File "/home/evk1206/Projects/Yocto-CTP-2019/poky/scripts/lib/bsp/engine.py", 
line 380, in exec_listgen_fn
self.lineno, self.line)
  File "/home/evk1206/Projects/Yocto-CTP-2019/poky/scripts/lib/bsp/engine.py", 
line 71, in parse_error
raise SyntaxError("%s: %s" % (msg, line))
  File "", line None
SyntaxError: function specified for 'gen' property returned nothing : input 
type:"choicelist" name:"new_kbranch" gen:"bsp.kernel.all_branches" 
branches_base:"standard" prio:"20" msg:"Please choose a machine branch to base 
this BSP on:" default:"standard/base"

Couly anyone let me know how to fix the issue.

I tried using both the master and 
morty-16.0.1
  branches of poky.


Mit freundlichen Grüßen / Best regards
Vinothkumar Eswaran


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto