[yocto] SquashFs Root with Writable OverlayFS ?

2016-02-22 Thread Albert K 
Dear all,

I have read the online yocto documentation and still quite confused as to
how to go about doing this?  I am working on X86 SOC with 16GB msata SSD

1) How do I build the SquashFS?
2) Do I need to have one partition to store the SquashFS and another for
the OverlayFS
3) Is there a step by step tutorial anywhere?

Thank you for assisting.

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

[linux-yocto] Error creating core-image-sato

2016-02-22 Thread winiston 
Dear,
 
I tried to build core-image-sato. It spits out the following error.
 
winiston@winiston-VirtualBox:~/poky/build$ bitbake core-image-sato
Parsing recipes: 100% |###| ETA:  00:00:00
Parsing of 1060 .bb files complete (0 cached, 1060 parsed). 1496 targets,
138 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'xf86-input-tslib' (but
/home/winiston/poky/meta/recipes-graphics/packagegroups/packagegroup-core-
x11-xserver.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'xf86-input-tslib' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xf86-input-tslib']
NOTE: Runtime target 'packagegroup-core-x11-xserver' is unbuildable,
removing...
Missing or unbuildable dependency chain was:
['packagegroup-core-x11-xserver', 'xf86-input-tslib']
NOTE: Runtime target 'packagegroup-core-x11-base' is unbuildable,
removing...
Missing or unbuildable dependency chain was:
['packagegroup-core-x11-base', 'packagegroup-core-x11-xserver',
'xf86-input-tslib']
ERROR: Required build target 'core-image-sato' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-sato',
'packagegroup-core-x11-base', 'packagegroup-core-x11-xserver',
'xf86-input-tslib']
 
Summary: There were 2 ERROR messages shown, returning a non-zero exit
code.
winiston@winiston-VirtualBox:~/poky/build$
 
How do I resolve this error?
 
Host system: Ubuntu 14.04 (Virtual machine )
Target system :  AM437x-evm 


Regards,
Winiston.P
Futura Automation Pvt Ltd.

Ph :91-80-28375290 / 28375295
Fax :91-80-28375291
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[yocto] Yocto Project Technical Team Meeting

2016-02-22 Thread Jolley, Stephen K 
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Jolley, Stephen K":MAILTO:stephen.k.jol...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=yocto@yoct
 oproject.org:MAILTO:yocto@yoctoproject.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Wold, Saul"
 :MAILTO:saul.w...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Purdie, Ri
 chard":MAILTO:richard.pur...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Dumitru, A
 lin":MAILTO:alin.dumi...@intel.com
ATTACH:CID:55DF18CB1CD4E148A2DB3900603BD8E2@intel.com
DESCRIPTION;LANGUAGE=en-US:We encourage people attending the meeting to log
 on and announce themselves on the Yocto Project IRC chancel during the mee
 ting (optional):\n\nYocto IRC: http://webchat.freenode.net/?channels=#yoct
 o\nIRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html\n\nhttps:
 //www.yoctoproject.org/tools-resources/community/weekly-technical-call\n\n
 Conference Details:\nCompany:   WIND RIVER SYS\nReady-Access Numbe
 r: 8007302996/9139049836\nAccess Code: 2705751\n\n\n\n\n\n\n
SUMMARY;LANGUAGE=en-US:Yocto Project Technical Team Meeting
DTSTART;TZID=Pacific Standard Time:20160308T08
DTEND;TZID=Pacific Standard Time:20160308T083000
UID:04008200E00074C5B7101A82E008508FEA35138ACF01000
 01000EACF2162F2449944802D21AEE6A84568
RECURRENCE-ID;TZID=Pacific Standard Time:20160301T08
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20160222T184915Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:24
LOCATION;LANGUAGE=en-US:Bridge Info Enclosed.
X-MICROSOFT-CDO-APPT-SEQUENCE:24
X-MICROSOFT-CDO-OWNERAPPTID:-1374591010
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Post Generation of debug information

2016-02-22 Thread Khem Raj 
On Mon, Feb 22, 2016 at 7:41 AM, Oliver  wrote:
> I have the need to generate some scripts for a debugger tool. As a first
> approach, these generated scripts could contain paths on where specific
> binary files are stored on the file system.
>
> Such purpose has been partially fulfilled with a recipe implementing the
> do_compile task to generate those files, assuming not implementing the
> deploying tasks, nothing gets integrated in the final image.
>
> Therefore the debugger tool could go to build/work/temp/…/myrecipe/…
> (WORKDIR of the recipe) as a startpoint for such scripts.
>
> 2 Questions:
>
> -  There would be a better solution for this task?
> -  The task has not been as successfully as expected. Ideally I
> would access variables of other recipes to know where they are their
> output/intermediate files. E.g. location of an elf file for u-boot. Is there
> any way around this?
>

There are ways implemented e.g. you can generate an image tarball in two pieces
1. binaries
2. Associated debug info and symbols

The untar both in same place.

Point your cross gdb to this location via setting appropriate sysroot
in .gdbinit
and that will be it.

However its not clear if thats what you are looking for. If you want to point to
components build directory instead of a full rootfs then you have to enhacne
the .gdbinit a bit more.

I am assuming that gdb is the debugging tool you are trying to use

> Regards
>
> --
> ___
> 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] Bitbake does not apply changes and sometimes it removes the kernel-source directory

2016-02-22 Thread Khem Raj 
On Mon, Feb 22, 2016 at 1:16 AM, simo  wrote:
> Hi all,
>
> I am using a 'poky fido 13.0.1' Yocto distribution and I am experiencing
> some problem after modifying the Linux kernel code and recompiling it.
>
> Bitbake is not applying the changes and sometimes deletes the source
> folder (but I have a backup, of course).
>
> From yocto environment shell, I execute:
>
> ~$ bitbake linux-gumstix -c compile -f
>
> and then to create an image and having a kernel file compiled available:
>
> ~$ bitbake core-image-base
>
> What is the best way to recompile an edited source with bitbake from
> shell ? And why it removes the kernel-source directory ?

you can use devtool to setup an component sandbox and make changes
there that would
be preferred approach.

http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#using-devtool-in-your-workflow

second option is to use quilt based workflow where you use quilt in
the workdir to generate the patch
and then ship it into metadata and apply it as a patch via SRC_URI

http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#using-a-quilt-workflow

>
> Thank you in advance for your help.
>
> Regards,
> Simon
>
> --
> ___
> 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] Qt5browser-problem

2016-02-22 Thread Khem Raj 
On Sun, Feb 21, 2016 at 11:12 PM, Surya  wrote:
> Hello,
>
> Is there any qt5 webbrowser based on qtwebkit or webengine ,which works with
> audio video application? I have worked on otter-browser,snowshoe ,but in all
> cases i can only access normal pages like google.com etc.,,but streaming is
> not possible.I cant see youtube videos or any video application. Any
> suggestion on this ..

IIRC there is a sample browser called fancybrowser that can be
installed allong with qtwebkit


>
>
>
> Thanks
> Surya
> --
> ___
> 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] [meta-chip][PATCH] added md5 for ntc's modified u-boot Licences/README file.

2016-02-22 Thread Khem Raj 
On Sun, Feb 21, 2016 at 4:30 AM, Valentin Le bescond
 wrote:
> Hi, sorry it was my first (tiny) try at a contribution ... Should I have
> explained more in the title ?
>
> Next Thing Co changed the Licences/README file in their repo.
> And in the u-boot.inc file used by u-boot-chip, this file is chekced with
> LIC_FILES_CHKSUM. And so it doesn't build without a modification of the md5.
> That's it !
>

hmmm ok.

>
> Le sam. 20 févr. 2016 à 20:09, Khem Raj  a écrit :
>>
>> On Sat, Feb 20, 2016 at 8:25 AM, Valentin LE BESCOND
>>  wrote:
>> > From: Nitnelav 
>> >
>> > Signed-off-by: Nitnelav 
>> > ---
>> >  recipes-bsp/u-boot/u-boot-chip_git.bb | 2 ++
>> >  1 file changed, 2 insertions(+)
>> >
>> > diff --git a/recipes-bsp/u-boot/u-boot-chip_git.bb
>> > b/recipes-bsp/u-boot/u-boot-chip_git.bb
>> > index 2342478..0b9032f 100644
>> > --- a/recipes-bsp/u-boot/u-boot-chip_git.bb
>> > +++ b/recipes-bsp/u-boot/u-boot-chip_git.bb
>> > @@ -8,6 +8,8 @@ PROVIDES += "u-boot"
>> >  UBOOT_VERSION ?= "2015.07"
>> >  PV = "${UBOOT_VERSION}+git${SRCPV}"
>> >
>> > +LIC_FILES_CHKSUM =
>> > "file://Licenses/README;md5=0507cd7da8e7ad6d6701926ec9b84c95"
>> > +
>>
>> while checksumming more is merrier, it would be good to know why we
>> should check for this one ?
>>
>> >  SRCREV ?= "854d5fcc641d8d8914c03a69d7172815d5b81a99"
>> >  BRANCH ?= "chip/stable"
>> >  SRC_URI =
>> > "git://github.com/NextThingCo/CHIP-u-boot.git;branch=${BRANCH}"
>> > --
>> > 1.9.1
>> >
>> > --
>> > ___
>> > 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] [meta-selinux][PATCH] swig is in meta-oe, remove this copy

2016-02-22 Thread Mark Hatle 
On 2/22/16 10:19 AM, Martin Jansa wrote:
> On Mon, Feb 22, 2016 at 03:58:44PM +, Burton, Ross wrote:
>> On 22 February 2016 at 15:33, Joe MacDonald 
>> wrote:
>>
>>> I'm also not against removing the local copy (I don't think it adds
>>> anything to the layer and occasionally causes headaches), but I really
>>> don't want to make meta-selinux dependent on meta-oe components, so I
>>> guess I'm voting for keeping it.
>>>
>>
>> Luckily it's also in oe-core (meta/recipes-devtools/swig/swig_3.0.8.bb).
> 
> And it was removed from meta-oe couple months ago:
> 
> commit 02f98d1bc7dc585538df5c96c2b0ccdd857ec46f
> Author: Wenzong Fan 
> AuthorDate: Thu Oct 8 01:31:36 2015 -0400
> Commit: Martin Jansa 
> CommitDate: Tue Oct 13 12:28:17 2015 +0200
> 
> swig: remove package
> 
> swig 3.0.6 has been moved to oe-croe:
>   66923c6776da13bd4513a73c3f7c5e60d74eb0f3
> 
> Signed-off-by: Wenzong Fan 
> Signed-off-by: Martin Jansa 
> 
> 
> 

Yup.. lets yank it then from meta-selinux, no reason to keep carrying it 
forward.

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

Re: [yocto] [meta-selinux][PATCH] swig is in meta-oe, remove this copy

2016-02-22 Thread Martin Jansa 
On Mon, Feb 22, 2016 at 03:58:44PM +, Burton, Ross wrote:
> On 22 February 2016 at 15:33, Joe MacDonald 
> wrote:
> 
> > I'm also not against removing the local copy (I don't think it adds
> > anything to the layer and occasionally causes headaches), but I really
> > don't want to make meta-selinux dependent on meta-oe components, so I
> > guess I'm voting for keeping it.
> >
> 
> Luckily it's also in oe-core (meta/recipes-devtools/swig/swig_3.0.8.bb).

And it was removed from meta-oe couple months ago:

commit 02f98d1bc7dc585538df5c96c2b0ccdd857ec46f
Author: Wenzong Fan 
AuthorDate: Thu Oct 8 01:31:36 2015 -0400
Commit: Martin Jansa 
CommitDate: Tue Oct 13 12:28:17 2015 +0200

swig: remove package

swig 3.0.6 has been moved to oe-croe:
  66923c6776da13bd4513a73c3f7c5e60d74eb0f3

Signed-off-by: Wenzong Fan 
Signed-off-by: Martin Jansa 

-- 
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com


signature.asc
Description: Digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][PATCH] swig is in meta-oe, remove this copy

2016-02-22 Thread Philip Balister 
On 02/22/2016 10:33 AM, Joe MacDonald wrote:
> [Re: [meta-selinux][PATCH] swig is in meta-oe, remove this copy] On 16.02.22 
> (Mon 08:40) Mark Hatle wrote:
> 
>> On 2/19/16 4:59 PM, T.O. Radzy Radzykewycz wrote:
>>> A more recent version of swig is in meta-oe, and the local
>>> version does not seem to provide any additional functionality or
>>> security features.  So best to just use the one in meta-oe and
>>> eliminate duplication.
>>>
>>> Signed-off-by: T.O. Radzy Radzykewycz 
>>
>> In the past we carried our own version of swig to break any dependency on 
>> meta-oe.
>>
>> I'm not sure if we want to keep doing that or not -- but if we do keep our 
>> own
>> version, we need to make sure it stays in sync w/ meta-oe (and the needs of 
>> the
>> selinux components).
>>
>> Joe/Philip, any comments?
>>
>> (I'm not against removing the local copy, but I want to make sure it makes 
>> sense
>> first.)
> 
> I'm also not against removing the local copy (I don't think it adds
> anything to the layer and occasionally causes headaches), but I really
> don't want to make meta-selinux dependent on meta-oe components, so I
> guess I'm voting for keeping it.

Should we talk about moving swig to oe-core then? GNURadio uses it in
meta-sdr, meta-selinux uses it, and several recipes in meta-oe do. If
layers are using a component from meta-oe, it is time to talk about
moving the recipe to oe-core.

Philip, the original one.

> 
> -J.
> 
>>
>> --Mark
>>
>>> ---
>>>  recipes-devtools/swig/swig.inc | 59 --
>>>  ...lf-exe-for-swig-swiglib-on-non-Win32-plat.patch | 69 
>>> --
>>>  ...nfigure-use-pkg-config-for-pcre-detection.patch | 65 
>>> 
>>>  recipes-devtools/swig/swig_2.0.10.bb   | 11 
>>>  4 files changed, 204 deletions(-)
>>>  delete mode 100644 recipes-devtools/swig/swig.inc
>>>  delete mode 100644 
>>> recipes-devtools/swig/swig/0001-Use-proc-self-exe-for-swig-swiglib-on-non-Win32-plat.patch
>>>  delete mode 100644 
>>> recipes-devtools/swig/swig/0001-configure-use-pkg-config-for-pcre-detection.patch
>>>  delete mode 100644 recipes-devtools/swig/swig_2.0.10.bb
>>>
>>> diff --git a/recipes-devtools/swig/swig.inc b/recipes-devtools/swig/swig.inc
>>> deleted file mode 100644
>>> index 74ce5064fe37..
>>> --- a/recipes-devtools/swig/swig.inc
>>> +++ /dev/null
>>> @@ -1,59 +0,0 @@
>>> -DESCRIPTION = "SWIG - Simplified Wrapper and Interface Generator"
>>> -HOMEPAGE = "http://swig.sourceforge.net/;
>>> -LICENSE = "BSD & GPLv3"
>>> -LIC_FILES_CHKSUM = "file://LICENSE;md5=e7807a6282784a7dde4c846626b08fc6 \
>>> -
>>> file://LICENSE-GPL;md5=d32239bcb673463ab874e80d47fae504 \
>>> -
>>> file://LICENSE-UNIVERSITIES;md5=8ce9dcc8f7c994de4a408b205c72ba08"
>>> -
>>> -SECTION = "devel"
>>> -INC_PR = "r3"
>>> -
>>> -DEPENDS = "libpcre python"
>>> -
>>> -SRC_URI = "${SOURCEFORGE_MIRROR}/${BPN}/${BPN}-${PV}.tar.gz"
>>> -
>>> -inherit autotools pythonnative
>>> -
>>> -EXTRA_OECONF = " \
>>> ---with-python=${PYTHON} \
>>> ---without-allegrocl \
>>> ---without-android \
>>> ---without-boost \
>>> ---without-chicken \
>>> ---without-clisp \
>>> ---without-csharp \
>>> ---without-d \
>>> ---without-gcj \
>>> ---without-go \
>>> ---without-guile \
>>> ---without-java \
>>> ---without-lua \
>>> ---without-mzscheme \
>>> ---without-ocaml \
>>> ---without-octave \
>>> ---without-perl5 \
>>> ---without-pike \
>>> ---without-php \
>>> ---without-python3 \
>>> ---without-r \
>>> ---without-ruby \
>>> ---without-tcl \
>>> -"
>>> -
>>> -BBCLASSEXTEND = "native nativesdk"
>>> -
>>> -do_configure() {
>>> -install -m 0755 ${STAGING_DATADIR_NATIVE}/gnu-config/config.guess 
>>> ${S}/Tools/config
>>> -install -m 0755 ${STAGING_DATADIR_NATIVE}/gnu-config/config.sub 
>>> ${S}/Tools/config
>>> -install -m 0755 ${STAGING_DATADIR_NATIVE}/gnu-config/config.guess ${S}
>>> -install -m 0755 ${STAGING_DATADIR_NATIVE}/gnu-config/config.sub ${S}
>>> -oe_runconf
>>> -}
>>> -
>>> -def swiglib_relpath(d):
>>> -swiglib = d.getVar('datadir', True) + "/" + d.getVar('BPN', True) + 
>>> "/" + d.getVar('PV', True)
>>> -return os.path.relpath(swiglib, d.getVar('bindir', True))
>>> -
>>> -do_install_append_class-native() {
>>> -   create_wrapper ${D}${bindir}/swig SWIG_LIB='`dirname 
>>> $''realpath`'/${@swiglib_relpath(d)}
>>> -}
>>> diff --git 
>>> a/recipes-devtools/swig/swig/0001-Use-proc-self-exe-for-swig-swiglib-on-non-Win32-plat.patch
>>>  
>>> b/recipes-devtools/swig/swig/0001-Use-proc-self-exe-for-swig-swiglib-on-non-Win32-plat.patch
>>> deleted file mode 100644
>>> index 81df3e264f52..
>>> --- 
>>> a/recipes-devtools/swig/swig/0001-Use-proc-self-exe-for-swig-swiglib-on-non-Win32-plat.patch
>>> +++ /dev/null
>>> @@ -1,69 +0,0 @@
>>> -From a4a0440a644c6c5e5da096efe3cf05ba309a284f

Re: [yocto] [meta-selinux][PATCH] swig is in meta-oe, remove this copy

2016-02-22 Thread Burton, Ross 
On 22 February 2016 at 15:33, Joe MacDonald 
wrote:

> I'm also not against removing the local copy (I don't think it adds
> anything to the layer and occasionally causes headaches), but I really
> don't want to make meta-selinux dependent on meta-oe components, so I
> guess I'm voting for keeping it.
>

Luckily it's also in oe-core (meta/recipes-devtools/swig/swig_3.0.8.bb).

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

Re: [yocto] [[PATCHv2][autobuilder] 4/4] buildset-config.toaster: Remove unused template toaster-build.

2016-02-22 Thread Aníbal Limón 
Agree.


On 02/22/2016 09:37 AM, Flanagan, Elizabeth wrote:
> I'm going to pull all but this patch (4/4), because I'll eventually
> need this configuration.
> 
> -b
> 
> On 22 February 2016 at 15:15, Aníbal Limón  
> wrote:
>> Signed-off-by: Aníbal Limón 
>> ---
>>  buildset-config.toaster/toaster-build.conf | 29 
>> -
>>  1 file changed, 29 deletions(-)
>>  delete mode 100644 buildset-config.toaster/toaster-build.conf
>>
>> diff --git a/buildset-config.toaster/toaster-build.conf 
>> b/buildset-config.toaster/toaster-build.conf
>> deleted file mode 100644
>> index 09a03e2..000
>> --- a/buildset-config.toaster/toaster-build.conf
>> +++ /dev/null
>> @@ -1,29 +0,0 @@
>> -[toaster-build]
>> -builders: 'example-worker'
>> -props: [{'atext':{'prop_type':'StringParameter',
>> -   'size': 15,
>> -   'name': 'atext',
>> -   'default': '',
>> -   'label':' auto.conf:'}},
>> -{'bbtext':{'prop_type':'StringParameter',
>> -   'size': 15,
>> -   'name': 'bbtext',
>> -   'default': '',
>> -   'label':' bblayers.conf:'}},
>> -{'images':{'prop_type':'StringParameter',
>> -   'size': 15,
>> -   'name': 'images',
>> -   'default': '',
>> -   'label':' images:'}},
>> -{'layers':{'prop_type':'StringParameter',
>> -   'size': 15,
>> -   'name': 'layers',
>> -   'default': '',
>> -   'label':' repo string (ast):'}}]
>> -steps: [{'SetDest':{}},
>> -{'CheckOutToasterLayers': {}},
>> -{'RunPreamble': {}},
>> -{'GetDistroVersion' : {'distro': 'poky'}},
>> -{'CreateAutoConf': {'atext' : '#TOASTER'}},
>> -{'CreateBBLayersConf': {'bbtext' : '#TOASTER'}},
>> -{'BuildImages': {'images': '#TOASTER'}}]
>> --
>> 2.1.4
>>
> 
> 
> 



signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Post Generation of debug information

2016-02-22 Thread Oliver 
I have the need to generate some scripts for a debuggertool. As a first 
approach, these generated scripts could contain paths on wherespecific binary 
files are stored on the file system. 


 
Such purpose has been partially fulfilled with a recipe implementingthe 
do_compile task to generate those files, assuming not implementing thedeploying 
tasks, nothing gets integrated in the final image. 


 
Therefore the debugger tool could go to build/work/temp/…/myrecipe/… (WORKDIR 
of the recipe) as a startpointfor such scripts.


 
2 Questions:


 
- There would be a better solution for this task?

- The task has not been as successfully asexpected. Ideally I would 
access variables of other recipes to know where theyare their 
output/intermediate files. E.g. location of an elf file for u-boot.Is there any 
way around this?


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

Re: [yocto] [[PATCHv2][autobuilder] 4/4] buildset-config.toaster: Remove unused template toaster-build.

2016-02-22 Thread Flanagan, Elizabeth 
I'm going to pull all but this patch (4/4), because I'll eventually
need this configuration.

-b

On 22 February 2016 at 15:15, Aníbal Limón  wrote:
> Signed-off-by: Aníbal Limón 
> ---
>  buildset-config.toaster/toaster-build.conf | 29 -
>  1 file changed, 29 deletions(-)
>  delete mode 100644 buildset-config.toaster/toaster-build.conf
>
> diff --git a/buildset-config.toaster/toaster-build.conf 
> b/buildset-config.toaster/toaster-build.conf
> deleted file mode 100644
> index 09a03e2..000
> --- a/buildset-config.toaster/toaster-build.conf
> +++ /dev/null
> @@ -1,29 +0,0 @@
> -[toaster-build]
> -builders: 'example-worker'
> -props: [{'atext':{'prop_type':'StringParameter',
> -   'size': 15,
> -   'name': 'atext',
> -   'default': '',
> -   'label':' auto.conf:'}},
> -{'bbtext':{'prop_type':'StringParameter',
> -   'size': 15,
> -   'name': 'bbtext',
> -   'default': '',
> -   'label':' bblayers.conf:'}},
> -{'images':{'prop_type':'StringParameter',
> -   'size': 15,
> -   'name': 'images',
> -   'default': '',
> -   'label':' images:'}},
> -{'layers':{'prop_type':'StringParameter',
> -   'size': 15,
> -   'name': 'layers',
> -   'default': '',
> -   'label':' repo string (ast):'}}]
> -steps: [{'SetDest':{}},
> -{'CheckOutToasterLayers': {}},
> -{'RunPreamble': {}},
> -{'GetDistroVersion' : {'distro': 'poky'}},
> -{'CreateAutoConf': {'atext' : '#TOASTER'}},
> -{'CreateBBLayersConf': {'bbtext' : '#TOASTER'}},
> -{'BuildImages': {'images': '#TOASTER'}}]
> --
> 2.1.4
>



-- 
Elizabeth Flanagan
Yocto Project
Build and Release
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][PATCH] swig is in meta-oe, remove this copy

2016-02-22 Thread Joe MacDonald 
[Re: [meta-selinux][PATCH] swig is in meta-oe, remove this copy] On 16.02.22 
(Mon 08:40) Mark Hatle wrote:

> On 2/19/16 4:59 PM, T.O. Radzy Radzykewycz wrote:
> > A more recent version of swig is in meta-oe, and the local
> > version does not seem to provide any additional functionality or
> > security features.  So best to just use the one in meta-oe and
> > eliminate duplication.
> > 
> > Signed-off-by: T.O. Radzy Radzykewycz 
> 
> In the past we carried our own version of swig to break any dependency on 
> meta-oe.
> 
> I'm not sure if we want to keep doing that or not -- but if we do keep our own
> version, we need to make sure it stays in sync w/ meta-oe (and the needs of 
> the
> selinux components).
> 
> Joe/Philip, any comments?
> 
> (I'm not against removing the local copy, but I want to make sure it makes 
> sense
> first.)

I'm also not against removing the local copy (I don't think it adds
anything to the layer and occasionally causes headaches), but I really
don't want to make meta-selinux dependent on meta-oe components, so I
guess I'm voting for keeping it.

-J.

> 
> --Mark
> 
> > ---
> >  recipes-devtools/swig/swig.inc | 59 --
> >  ...lf-exe-for-swig-swiglib-on-non-Win32-plat.patch | 69 
> > --
> >  ...nfigure-use-pkg-config-for-pcre-detection.patch | 65 
> > 
> >  recipes-devtools/swig/swig_2.0.10.bb   | 11 
> >  4 files changed, 204 deletions(-)
> >  delete mode 100644 recipes-devtools/swig/swig.inc
> >  delete mode 100644 
> > recipes-devtools/swig/swig/0001-Use-proc-self-exe-for-swig-swiglib-on-non-Win32-plat.patch
> >  delete mode 100644 
> > recipes-devtools/swig/swig/0001-configure-use-pkg-config-for-pcre-detection.patch
> >  delete mode 100644 recipes-devtools/swig/swig_2.0.10.bb
> > 
> > diff --git a/recipes-devtools/swig/swig.inc b/recipes-devtools/swig/swig.inc
> > deleted file mode 100644
> > index 74ce5064fe37..
> > --- a/recipes-devtools/swig/swig.inc
> > +++ /dev/null
> > @@ -1,59 +0,0 @@
> > -DESCRIPTION = "SWIG - Simplified Wrapper and Interface Generator"
> > -HOMEPAGE = "http://swig.sourceforge.net/;
> > -LICENSE = "BSD & GPLv3"
> > -LIC_FILES_CHKSUM = "file://LICENSE;md5=e7807a6282784a7dde4c846626b08fc6 \
> > -
> > file://LICENSE-GPL;md5=d32239bcb673463ab874e80d47fae504 \
> > -
> > file://LICENSE-UNIVERSITIES;md5=8ce9dcc8f7c994de4a408b205c72ba08"
> > -
> > -SECTION = "devel"
> > -INC_PR = "r3"
> > -
> > -DEPENDS = "libpcre python"
> > -
> > -SRC_URI = "${SOURCEFORGE_MIRROR}/${BPN}/${BPN}-${PV}.tar.gz"
> > -
> > -inherit autotools pythonnative
> > -
> > -EXTRA_OECONF = " \
> > ---with-python=${PYTHON} \
> > ---without-allegrocl \
> > ---without-android \
> > ---without-boost \
> > ---without-chicken \
> > ---without-clisp \
> > ---without-csharp \
> > ---without-d \
> > ---without-gcj \
> > ---without-go \
> > ---without-guile \
> > ---without-java \
> > ---without-lua \
> > ---without-mzscheme \
> > ---without-ocaml \
> > ---without-octave \
> > ---without-perl5 \
> > ---without-pike \
> > ---without-php \
> > ---without-python3 \
> > ---without-r \
> > ---without-ruby \
> > ---without-tcl \
> > -"
> > -
> > -BBCLASSEXTEND = "native nativesdk"
> > -
> > -do_configure() {
> > -install -m 0755 ${STAGING_DATADIR_NATIVE}/gnu-config/config.guess 
> > ${S}/Tools/config
> > -install -m 0755 ${STAGING_DATADIR_NATIVE}/gnu-config/config.sub 
> > ${S}/Tools/config
> > -install -m 0755 ${STAGING_DATADIR_NATIVE}/gnu-config/config.guess ${S}
> > -install -m 0755 ${STAGING_DATADIR_NATIVE}/gnu-config/config.sub ${S}
> > -oe_runconf
> > -}
> > -
> > -def swiglib_relpath(d):
> > -swiglib = d.getVar('datadir', True) + "/" + d.getVar('BPN', True) + 
> > "/" + d.getVar('PV', True)
> > -return os.path.relpath(swiglib, d.getVar('bindir', True))
> > -
> > -do_install_append_class-native() {
> > -   create_wrapper ${D}${bindir}/swig SWIG_LIB='`dirname 
> > $''realpath`'/${@swiglib_relpath(d)}
> > -}
> > diff --git 
> > a/recipes-devtools/swig/swig/0001-Use-proc-self-exe-for-swig-swiglib-on-non-Win32-plat.patch
> >  
> > b/recipes-devtools/swig/swig/0001-Use-proc-self-exe-for-swig-swiglib-on-non-Win32-plat.patch
> > deleted file mode 100644
> > index 81df3e264f52..
> > --- 
> > a/recipes-devtools/swig/swig/0001-Use-proc-self-exe-for-swig-swiglib-on-non-Win32-plat.patch
> > +++ /dev/null
> > @@ -1,69 +0,0 @@
> > -From a4a0440a644c6c5e5da096efe3cf05ba309a284f Mon Sep 17 00:00:00 2001
> > -From: "NODA, Kai" 
> > -Date: Sun, 22 Apr 2012 17:01:02 +0900
> > -Subject: [PATCH] Use /proc/self/exe for "swig -swiglib" on non-Win32
> > - platforms.
> > -
> > -If it wasn't found, then fall back to a fixed string just as before.
> > -
> > -Upstream-Status: Submitted
> >

[yocto] [[PATCHv2][autobuilder] 3/4] buildset-config.toaster: Add toaster-tests.conf buildset.

2016-02-22 Thread Aníbal Limón 
The toaster-tests buildset contains steps for run toaster tests
in a clean way, a Sleep step is needed after setup toaster for
give certain time to let toaster ends setup.

Signed-off-by: Aníbal Limón 
---
 buildset-config.toaster/toaster-tests.conf | 21 +
 buildset-config.toaster/yoctoAB.conf   |  2 +-
 2 files changed, 22 insertions(+), 1 deletion(-)
 create mode 100644 buildset-config.toaster/toaster-tests.conf

diff --git a/buildset-config.toaster/toaster-tests.conf 
b/buildset-config.toaster/toaster-tests.conf
new file mode 100644
index 000..0aa6b46
--- /dev/null
+++ b/buildset-config.toaster/toaster-tests.conf
@@ -0,0 +1,21 @@
+[toaster-tests]
+builders: 'example-worker'
+repos: [{'poky':
+{'repourl':'git://git.yoctoproject.org/poky',
+ 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp', 
'yocto':'meta-yocto', 'poky':'meta-poky'},
+ 'branch':'master' }}]
+steps: [{'SetDest':{}},
+{'CheckOutLayers': {}},
+{'RunPreamble': {}},
+{'GetDistroVersion' : {'distro': 'poky'}},
+{'CreateAutoConf': {'machine': 'qemux86', 'SDKMACHINE' : 'i686',
+'distro': 'poky', 'buildhistory' : True}},
+{'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
+{'SyncPersistDB' : {'distro' : 'poky'}},
+{'GetBitbakeVersion': {}},
+   {'ToasterSetupVenv': {}},
+   {'ToasterStart': {}},
+   {'Sleep': {'time': '120'}},
+   {'ToasterRunTests': {}},
+   {'ToasterStop': {}},
+   ]
diff --git a/buildset-config.toaster/yoctoAB.conf 
b/buildset-config.toaster/yoctoAB.conf
index 4f3fa00..614e39c 100644
--- a/buildset-config.toaster/yoctoAB.conf
+++ b/buildset-config.toaster/yoctoAB.conf
@@ -1,2 +1,2 @@
 [BuildSets]
-order: [] 
+order: ['toaster-tests']
-- 
2.1.4

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

[yocto] [[PATCHv2][autobuilder] 4/4] buildset-config.toaster: Remove unused template toaster-build.

2016-02-22 Thread Aníbal Limón 
Signed-off-by: Aníbal Limón 
---
 buildset-config.toaster/toaster-build.conf | 29 -
 1 file changed, 29 deletions(-)
 delete mode 100644 buildset-config.toaster/toaster-build.conf

diff --git a/buildset-config.toaster/toaster-build.conf 
b/buildset-config.toaster/toaster-build.conf
deleted file mode 100644
index 09a03e2..000
--- a/buildset-config.toaster/toaster-build.conf
+++ /dev/null
@@ -1,29 +0,0 @@
-[toaster-build]
-builders: 'example-worker'
-props: [{'atext':{'prop_type':'StringParameter',
-   'size': 15,
-   'name': 'atext',
-   'default': '',
-   'label':' auto.conf:'}},
-{'bbtext':{'prop_type':'StringParameter',
-   'size': 15,
-   'name': 'bbtext',
-   'default': '',
-   'label':' bblayers.conf:'}},
-{'images':{'prop_type':'StringParameter',
-   'size': 15,
-   'name': 'images',
-   'default': '',
-   'label':' images:'}},
-{'layers':{'prop_type':'StringParameter',
-   'size': 15,
-   'name': 'layers',
-   'default': '',
-   'label':' repo string (ast):'}}]
-steps: [{'SetDest':{}},
-{'CheckOutToasterLayers': {}},
-{'RunPreamble': {}},
-{'GetDistroVersion' : {'distro': 'poky'}},
-{'CreateAutoConf': {'atext' : '#TOASTER'}},
-{'CreateBBLayersConf': {'bbtext' : '#TOASTER'}},
-{'BuildImages': {'images': '#TOASTER'}}]
-- 
2.1.4

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

[yocto] [[PATCHv2][autobuilder] 1/4] autobuilder/lib: Add buildsteps module for provide helpers

2016-02-22 Thread Aníbal Limón 
Add ShellCommandCleanEnv helper for run command in a clean
enviroment a shell for run the command can be specified also
the variables to preserve in the new enviroment.

Signed-off-by: Aníbal Limón 
---
 .../site-packages/autobuilder/lib/buildsteps.py| 42 ++
 1 file changed, 42 insertions(+)
 create mode 100644 lib/python2.7/site-packages/autobuilder/lib/buildsteps.py

diff --git a/lib/python2.7/site-packages/autobuilder/lib/buildsteps.py 
b/lib/python2.7/site-packages/autobuilder/lib/buildsteps.py
new file mode 100644
index 000..3693a7a
--- /dev/null
+++ b/lib/python2.7/site-packages/autobuilder/lib/buildsteps.py
@@ -0,0 +1,42 @@
+'''
+Created on Feb 15, 2016
+
+__author__ = "Anibal (alimon) Limon"
+__copyright__ = "Copyright 2016, Intel Corp."
+__credits__ = ["Anibal Limon"]
+__license__ = "GPL"
+__version__ = "2.0"
+__maintainer__ = "Anibal Limon"
+__email__ = "anibal.li...@linux.intel.com"
+'''
+
+import os
+from buildbot.steps.shell import ShellCommand
+
+DEFAULT_SHELL = 'bash'
+
+class ShellCommandCleanEnv(ShellCommand):
+def __init__(self, factory, argdict=None, **kwargs):
+shell = DEFAULT_SHELL
+if 'SHELL' in kwargs:
+shell = kwargs['SHELL']
+del kwargs['SHELL']
+
+if 'PENV' in kwargs:
+preserve_env = kwargs['PENV']
+del kwargs['PENV']
+else:
+preserve_env = ['HOME', 'PWD', 'PATH',
+'http_proxy', 'https_proxy',
+'ftp_proxy', 'no_proxy', 'GIT_PROXY_COMMAND']
+
+env_command = self._get_env_cleaned_command(shell, preserve_env)
+self.command = "%s \'%s\'" % (env_command, self.command)
+ShellCommand.__init__(self, **kwargs)
+
+def _get_env_cleaned_command(self, shell, preserve_env):
+pe_cmd = ''
+for pe in preserve_env:
+pe_cmd += "%s=\"$%s\" " % (pe, pe)
+
+return "env -i %s %s -c " % (pe_cmd, shell)
-- 
2.1.4

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

[yocto] [[PATCHv2][autobuilder] 2/4] autobuilder/buildsteps: Add Toaster buildsteps.

2016-02-22 Thread Aníbal Limón 
Adds Toaster buildsteps for setup toaster environment (installs
requirements), start/stop a toaster instance and run tests.

Signed-off-by: Aníbal Limón 
---
 .../autobuilder/buildsteps/ToasterRunTests.py  | 31 
 .../autobuilder/buildsteps/ToasterSetupVenv.py | 31 
 .../autobuilder/buildsteps/ToasterStart.py | 32 +
 .../autobuilder/buildsteps/ToasterStop.py  | 33 ++
 4 files changed, 127 insertions(+)
 create mode 100644 
lib/python2.7/site-packages/autobuilder/buildsteps/ToasterRunTests.py
 create mode 100644 
lib/python2.7/site-packages/autobuilder/buildsteps/ToasterSetupVenv.py
 create mode 100644 
lib/python2.7/site-packages/autobuilder/buildsteps/ToasterStart.py
 create mode 100644 
lib/python2.7/site-packages/autobuilder/buildsteps/ToasterStop.py

diff --git 
a/lib/python2.7/site-packages/autobuilder/buildsteps/ToasterRunTests.py 
b/lib/python2.7/site-packages/autobuilder/buildsteps/ToasterRunTests.py
new file mode 100644
index 000..141768c
--- /dev/null
+++ b/lib/python2.7/site-packages/autobuilder/buildsteps/ToasterRunTests.py
@@ -0,0 +1,31 @@
+'''
+Created on Feb 15, 2016
+
+__author__ = "Anibal (alimon) Limon"
+__copyright__ = "Copyright 2016, Intel Corp."
+__credits__ = ["Anibal Limon"]
+__license__ = "GPL"
+__version__ = "2.0"
+__maintainer__ = "Anibal Limon"
+__email__ = "anibal.li...@linux.intel.com"
+'''
+
+from lib.buildsteps import ShellCommandCleanEnv
+import os
+
+class ToasterRunTests(ShellCommandCleanEnv):
+haltOnFailure = True
+flunkOnFailure = True
+name = "ToasterRunTests"
+
+def __init__(self, factory, argdict=None, **kwargs):
+self.factory = factory
+self.description = "Running toaster tests..."
+
+oe_cmd = "source ./oe-init-build-env;"
+venv_cmd = "source venv/bin/activate;"
+cmd = "DISPLAY=:1 toaster-test --run-all-tests --verbose"
+
+self.command = oe_cmd + venv_cmd + cmd
+
+ShellCommandCleanEnv.__init__(self, factory, argdict, **kwargs)
diff --git 
a/lib/python2.7/site-packages/autobuilder/buildsteps/ToasterSetupVenv.py 
b/lib/python2.7/site-packages/autobuilder/buildsteps/ToasterSetupVenv.py
new file mode 100644
index 000..54cf1e7
--- /dev/null
+++ b/lib/python2.7/site-packages/autobuilder/buildsteps/ToasterSetupVenv.py
@@ -0,0 +1,31 @@
+'''
+Created on Feb 15, 2016
+
+__author__ = "Anibal (alimon) Limon"
+__copyright__ = "Copyright 2016, Intel Corp."
+__credits__ = ["Anibal Limon"]
+__license__ = "GPL"
+__version__ = "2.0"
+__maintainer__ = "Anibal Limon"
+__email__ = "anibal.li...@linux.intel.com"
+'''
+
+from lib.buildsteps import ShellCommandCleanEnv
+
+class ToasterSetupVenv(ShellCommandCleanEnv):
+haltOnFailure = True
+flunkOnFailure = True
+name = "ToasterSetupVenv"
+
+def __init__(self, factory, argdict=None, **kwargs):
+self.factory = factory
+self.description = "Creating virtualenv..."
+
+oe_cmd = "source ./oe-init-build-env;"
+venv_cmd = "virtualenv venv; source venv/bin/activate;"
+install_cmd = "pip install -r ../bitbake/toaster-requirements.txt;"
+install_tests_cmd = "pip install -r 
../bitbake/toaster-tests-requirements.txt;"
+
+self.command = oe_cmd + venv_cmd + install_cmd + install_tests_cmd 
+
+ShellCommandCleanEnv.__init__(self, factory, argdict, **kwargs)
diff --git a/lib/python2.7/site-packages/autobuilder/buildsteps/ToasterStart.py 
b/lib/python2.7/site-packages/autobuilder/buildsteps/ToasterStart.py
new file mode 100644
index 000..14cf9db3
--- /dev/null
+++ b/lib/python2.7/site-packages/autobuilder/buildsteps/ToasterStart.py
@@ -0,0 +1,32 @@
+'''
+Created on Feb 15, 2016
+
+__author__ = "Anibal (alimon) Limon"
+__copyright__ = "Copyright 2016, Intel Corp."
+__credits__ = ["Anibal Limon"]
+__license__ = "GPL"
+__version__ = "2.0"
+__maintainer__ = "Anibal Limon"
+__email__ = "anibal.li...@linux.intel.com"
+'''
+
+from lib.buildsteps import ShellCommandCleanEnv
+import os
+
+class ToasterStart(ShellCommandCleanEnv):
+haltOnFailure = True
+flunkOnFailure = True
+name = "ToasterStart"
+
+def __init__(self, factory, argdict=None, **kwargs):
+self.factory = factory
+self.description = "Starting toaster..."
+
+oe_cmd = "source ./oe-init-build-env;"
+venv_cmd = "source venv/bin/activate;"
+start_cmd = "../bitbake/lib/toaster/tests/helpers.py -a start" \
+" -d $(readlink -e ../)"
+
+self.command = oe_cmd + venv_cmd + start_cmd
+
+ShellCommandCleanEnv.__init__(self, factory, argdict, **kwargs)
diff --git a/lib/python2.7/site-packages/autobuilder/buildsteps/ToasterStop.py 
b/lib/python2.7/site-packages/autobuilder/buildsteps/ToasterStop.py
new file mode 100644
index 000..6fda0e8
--- /dev/null
+++ b/lib/python2.7/site-packages/autobuilder/buildsteps/ToasterStop.py
@@ -0,0 +1,33 @@

Re: [yocto] [meta-chip][PATCH] added md5 for ntc's modified u-boot Licences/README file.

2016-02-22 Thread Oliver 
I faced the same problem locally, the u-boot.inc tends to check the in a file 
which is not present anymore in the repository of Next Thing Co.
Though I just check for the header of the file:
+LIC_FILES_CHKSUM = 
"file://README;beginline=1;endline=22;md5=2687c5ebfd9cb284491c3204b726ea29"

    
 

El Domingo 21 de febrero de 2016 13:30, Valentin Le bescond 
 escribió:
 

 

Hi, sorry it was my first (tiny) try at a contribution ... Should I have 
explained more in the title ?

Next Thing Co changed the Licences/README file in their repo.
And in the u-boot.inc file used by u-boot-chip, this file is chekced with 
LIC_FILES_CHKSUM. And so it doesn't build without a modification of the md5.
That's it !


Le sam. 20 févr. 2016 à 20:09, Khem Raj  a écrit :

On Sat, Feb 20, 2016 at 8:25 AM, Valentin LE BESCOND
 wrote:
> From: Nitnelav 
>
> Signed-off-by: Nitnelav 
> ---
>  recipes-bsp/u-boot/u-boot-chip_git.bb | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/recipes-bsp/u-boot/u-boot-chip_git.bb 
> b/recipes-bsp/u-boot/u-boot-chip_git.bb
> index 2342478..0b9032f 100644
> --- a/recipes-bsp/u-boot/u-boot-chip_git.bb
> +++ b/recipes-bsp/u-boot/u-boot-chip_git.bb
> @@ -8,6 +8,8 @@ PROVIDES += "u-boot"
>  UBOOT_VERSION ?= "2015.07"
>  PV = "${UBOOT_VERSION}+git${SRCPV}"
>
> +LIC_FILES_CHKSUM = 
> "file://Licenses/README;md5=0507cd7da8e7ad6d6701926ec9b84c95"
> +

while checksumming more is merrier, it would be good to know why we
should check for this one ?

>  SRCREV ?= "854d5fcc641d8d8914c03a69d7172815d5b81a99"
>  BRANCH ?= "chip/stable"
>  SRC_URI = "git://github.com/NextThingCo/CHIP-u-boot.git;branch=${BRANCH}"
> --
> 1.9.1
>
> --
> ___
> 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 mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][PATCH] swig is in meta-oe, remove this copy

2016-02-22 Thread Mark Hatle 
On 2/19/16 4:59 PM, T.O. Radzy Radzykewycz wrote:
> A more recent version of swig is in meta-oe, and the local
> version does not seem to provide any additional functionality or
> security features.  So best to just use the one in meta-oe and
> eliminate duplication.
> 
> Signed-off-by: T.O. Radzy Radzykewycz 

In the past we carried our own version of swig to break any dependency on 
meta-oe.

I'm not sure if we want to keep doing that or not -- but if we do keep our own
version, we need to make sure it stays in sync w/ meta-oe (and the needs of the
selinux components).

Joe/Philip, any comments?

(I'm not against removing the local copy, but I want to make sure it makes sense
first.)

--Mark

> ---
>  recipes-devtools/swig/swig.inc | 59 --
>  ...lf-exe-for-swig-swiglib-on-non-Win32-plat.patch | 69 
> --
>  ...nfigure-use-pkg-config-for-pcre-detection.patch | 65 
>  recipes-devtools/swig/swig_2.0.10.bb   | 11 
>  4 files changed, 204 deletions(-)
>  delete mode 100644 recipes-devtools/swig/swig.inc
>  delete mode 100644 
> recipes-devtools/swig/swig/0001-Use-proc-self-exe-for-swig-swiglib-on-non-Win32-plat.patch
>  delete mode 100644 
> recipes-devtools/swig/swig/0001-configure-use-pkg-config-for-pcre-detection.patch
>  delete mode 100644 recipes-devtools/swig/swig_2.0.10.bb
> 
> diff --git a/recipes-devtools/swig/swig.inc b/recipes-devtools/swig/swig.inc
> deleted file mode 100644
> index 74ce5064fe37..
> --- a/recipes-devtools/swig/swig.inc
> +++ /dev/null
> @@ -1,59 +0,0 @@
> -DESCRIPTION = "SWIG - Simplified Wrapper and Interface Generator"
> -HOMEPAGE = "http://swig.sourceforge.net/;
> -LICENSE = "BSD & GPLv3"
> -LIC_FILES_CHKSUM = "file://LICENSE;md5=e7807a6282784a7dde4c846626b08fc6 \
> -file://LICENSE-GPL;md5=d32239bcb673463ab874e80d47fae504 \
> -
> file://LICENSE-UNIVERSITIES;md5=8ce9dcc8f7c994de4a408b205c72ba08"
> -
> -SECTION = "devel"
> -INC_PR = "r3"
> -
> -DEPENDS = "libpcre python"
> -
> -SRC_URI = "${SOURCEFORGE_MIRROR}/${BPN}/${BPN}-${PV}.tar.gz"
> -
> -inherit autotools pythonnative
> -
> -EXTRA_OECONF = " \
> ---with-python=${PYTHON} \
> ---without-allegrocl \
> ---without-android \
> ---without-boost \
> ---without-chicken \
> ---without-clisp \
> ---without-csharp \
> ---without-d \
> ---without-gcj \
> ---without-go \
> ---without-guile \
> ---without-java \
> ---without-lua \
> ---without-mzscheme \
> ---without-ocaml \
> ---without-octave \
> ---without-perl5 \
> ---without-pike \
> ---without-php \
> ---without-python3 \
> ---without-r \
> ---without-ruby \
> ---without-tcl \
> -"
> -
> -BBCLASSEXTEND = "native nativesdk"
> -
> -do_configure() {
> -install -m 0755 ${STAGING_DATADIR_NATIVE}/gnu-config/config.guess 
> ${S}/Tools/config
> -install -m 0755 ${STAGING_DATADIR_NATIVE}/gnu-config/config.sub 
> ${S}/Tools/config
> -install -m 0755 ${STAGING_DATADIR_NATIVE}/gnu-config/config.guess ${S}
> -install -m 0755 ${STAGING_DATADIR_NATIVE}/gnu-config/config.sub ${S}
> -oe_runconf
> -}
> -
> -def swiglib_relpath(d):
> -swiglib = d.getVar('datadir', True) + "/" + d.getVar('BPN', True) + "/" 
> + d.getVar('PV', True)
> -return os.path.relpath(swiglib, d.getVar('bindir', True))
> -
> -do_install_append_class-native() {
> - create_wrapper ${D}${bindir}/swig SWIG_LIB='`dirname 
> $''realpath`'/${@swiglib_relpath(d)}
> -}
> diff --git 
> a/recipes-devtools/swig/swig/0001-Use-proc-self-exe-for-swig-swiglib-on-non-Win32-plat.patch
>  
> b/recipes-devtools/swig/swig/0001-Use-proc-self-exe-for-swig-swiglib-on-non-Win32-plat.patch
> deleted file mode 100644
> index 81df3e264f52..
> --- 
> a/recipes-devtools/swig/swig/0001-Use-proc-self-exe-for-swig-swiglib-on-non-Win32-plat.patch
> +++ /dev/null
> @@ -1,69 +0,0 @@
> -From a4a0440a644c6c5e5da096efe3cf05ba309a284f Mon Sep 17 00:00:00 2001
> -From: "NODA, Kai" 
> -Date: Sun, 22 Apr 2012 17:01:02 +0900
> -Subject: [PATCH] Use /proc/self/exe for "swig -swiglib" on non-Win32
> - platforms.
> -
> -If it wasn't found, then fall back to a fixed string just as before.
> -
> -Upstream-Status: Submitted
> -http://sourceforge.net/mailarchive/message.php?msg_id=29179733
> -
> 
> - Source/Modules/main.cxx |   24 ++--
> - 1 file changed, 22 insertions(+), 2 deletions(-)
> -
> -diff --git a/Source/Modules/main.cxx b/Source/Modules/main.cxx
> -index d2f5d3b..cbb0a12 100644
>  a/Source/Modules/main.cxx
> -+++ b/Source/Modules/main.cxx
> -@@ -26,6 +26,11 @@ char cvsroot_main_cxx[] = "$Id$";
> - #include "cparse.h"
> - #include 
> - #include  // for INT_MAX
> -+#ifndef _WIN32
> -+#include 
> -+#include  // for readlink
> -+#include// for stat
> -+#endif
> - 
> - // Global variables
> - 
> -@@

Re: [yocto] [meta-selinux][PATCH] MAINTAINERS: Update maintainers file

2016-02-22 Thread Joe MacDonald 
[Re: [yocto] [meta-selinux][PATCH] MAINTAINERS: Update maintainers file] On 
16.02.20 (Sat 20:24) Philip Tricca wrote:

> On 02/17/2016 06:41 PM, Joe MacDonald wrote:
> > Adding Philip Tricca as a common layer maintainer and marking Pascal as
> > away.
> 
> While the admins upstream get my ssh key in place I did a pass over the
> pending patches and the current state of the repo. There isn't a lot to
> do in the actual meta-selinux layer beyond what's already on the list.
> There was only one fix needed to get the build working again:
> 
> The xattr patches to e2fsprogs have been superseded by the work that
> WindRiver has been doing in upstream e2fsprogs. There's a bug in their
> implementation though and the root directory on the rootfs image doesn't
> get labeled. I've sent a fix to the upstream maintainer. In the meantime
> the current patches can just be dropped and replaced with this one.
> 
> There's also one fix required to get a login shell working. In
> openembedded-core, commit
> http://git.openembedded.org/openembedded-core/commit/?id=b93369a7943949f51057e0a704f5524ab7682fe6
> breaks the login process when the SELinux policy is enforced. I've sent
> a patch upstream to fix this:
> http://article.gmane.org/gmane.comp.handhelds.openembedded.core/76599
> 
> When I can commit these changes they're ready to go. After that I'll do
> another pass over the list and pick up the remaining patches that
> weren't required to get basic functionality back.

Awesome, thanks Philip.  I've pushed the change to the repo this morning
that lists you in the maintainers file, but if you haven't got access yet
to push to the repo yourself I'll be happy to take a PR from  you and
merge it myself.  I think I'm finally getting my head above water today.

Also, Michael, we talked last summer about getting meta-selinux added to
the list of projects monitored by Patchwork at patchwork.openembedded.org
and everyone seemed in favour of it but we didn't seem to close the loop
on it.  What's needed from Philip / Mark / myself to make that happen?

-- 
-Joe MacDonald.
:wq


signature.asc
Description: Digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Package Level Dependencies

2016-02-22 Thread Philip Balister 
On 02/22/2016 08:00 AM, sebastian.ro...@tu-dortmund.de wrote:
> Hi Rudolf,
> 
> Thnx for your input! I guess I can see your point. In particular I wasn't 
> thinking so much on using ".inc" files.
> Due to the fact that I will be having like 10-20 different test123-config-xxx 
> packages managing this using "RCONFLICTS" might be tedious.
> I guess this is what virtual packages (say test123-config-xxx has something 
> like PROVIDES=virtual/test123-config and test123 has a RDEPENDS on 
> virtual/test123-config) are for and I will try to follow this path for now.
> 
> For a couple of reasons, the configuration files are in the same git 
> repository as the source code of "test123". Is there a way of sharing working 
> directories between (at least all config-package recipes, such as I don't net 
> to checkout the whole git repository for each of my 10-20 config packages?

Would selecting the conf file with a MACHINE override help here?

Philip

> 
> Regards,
> Sebastian
> 
> -Ursprüngliche Nachricht-
> Von: Rudolf J Streif [mailto:rudolf.str...@gmail.com]
> Gesendet: Montag, 22. Februar 2016 02:38
> An: yocto@yoctoproject.org
> Cc: Rohde, Sebastian 
> Betreff: Re: [yocto] Package Level Dependencies
> 
> Hi Sebastian,
> 
>> I have a recipe (say: "test123") that provides a complex piece of
>> software (cmake-based). The software needs some configuration file
>> (say "test123.conf"). There are multiple variants of the configuration
>> file, sharing the same name, i.e. "test123.conf" exists in different
>> variants for multiple hardware configurations.
>>
>> My aim would be to have multiple packages like "test123-config-XXX"
>> and "test123-config-YYY", that cannot be installed at the same time,
>> while having one of the packages is a dependency for the main package 
>> "test123".
> 
> These are two conflicting packages.
> 
>>
>> Is there a way to achieve this? From my current understanding,
>> dependencies are "per-recipe" and not "per-package". Is there any way
>> to achieve package level dependencies? I would like to avoid having
>> multiple recipes as there are many configuration file options which
>> are currently located in the same large source repository as the main 
>> software.
> 
> Look at it from the perspective of conflicting packages.
> 
> My approach to this would be the following:
> 
> 1. Write an include file test123.inc that includes all of the guts of your 
> recipe.
> 
> 2. Write the two recipes test123-config-XXX_1.0.bb and test123-config-
> YYY_1.0.bb:
> 
> test123-config-XXX_1.0.bb
> 
> require test123.inc
> 
> SRC_URI += "test123-XXX.conf"
> 
> do_install_append() {
># install config file here
>install 544 test123-XXX.conf ${D}/ }
> 
> RCONFLICTS_${PN} = "test123-config-YYY"
> 
> Analog for test123-config-YYY_1.0.bb
> 
> 
> You are essentially sharing all of the recipe through the test123.inc and 
> only add the config file to the respective target recipe. The 
> RCONFLICTS_${PN} directive will flag an error if both conflicting packages 
> are attempted to be installed.
> 
> BR,
> Rudi
> 
> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist 
> ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese 
> E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und 
> vernichten Sie diese Mail. Vielen Dank.
> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
> ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform 
> (mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen 
> Schriftstücks per Telefax erfolgen.
> 
> Important note: The information included in this e-mail is confidential. It 
> is solely intended for the recipient. If you are not the intended recipient 
> of this e-mail please contact the sender and delete this message. Thank you. 
> Without prejudice of e-mail correspondence, our statements are only legally 
> binding when they are made in the conventional written form (with personal 
> signature) or when such documents are sent by fax.
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Package Level Dependencies

2016-02-22 Thread sebastian.ro...@tu-dortmund.de 
Hi Rudolf,

Thnx for your input! I guess I can see your point. In particular I wasn't 
thinking so much on using ".inc" files.
Due to the fact that I will be having like 10-20 different test123-config-xxx 
packages managing this using "RCONFLICTS" might be tedious.
I guess this is what virtual packages (say test123-config-xxx has something 
like PROVIDES=virtual/test123-config and test123 has a RDEPENDS on 
virtual/test123-config) are for and I will try to follow this path for now.

For a couple of reasons, the configuration files are in the same git repository 
as the source code of "test123". Is there a way of sharing working directories 
between (at least all config-package recipes, such as I don't net to checkout 
the whole git repository for each of my 10-20 config packages?

Regards,
Sebastian

-Ursprüngliche Nachricht-
Von: Rudolf J Streif [mailto:rudolf.str...@gmail.com]
Gesendet: Montag, 22. Februar 2016 02:38
An: yocto@yoctoproject.org
Cc: Rohde, Sebastian 
Betreff: Re: [yocto] Package Level Dependencies

Hi Sebastian,

> I have a recipe (say: "test123") that provides a complex piece of
> software (cmake-based). The software needs some configuration file
> (say "test123.conf"). There are multiple variants of the configuration
> file, sharing the same name, i.e. "test123.conf" exists in different
> variants for multiple hardware configurations.
>
> My aim would be to have multiple packages like "test123-config-XXX"
> and "test123-config-YYY", that cannot be installed at the same time,
> while having one of the packages is a dependency for the main package 
> "test123".

These are two conflicting packages.

>
> Is there a way to achieve this? From my current understanding,
> dependencies are "per-recipe" and not "per-package". Is there any way
> to achieve package level dependencies? I would like to avoid having
> multiple recipes as there are many configuration file options which
> are currently located in the same large source repository as the main 
> software.

Look at it from the perspective of conflicting packages.

My approach to this would be the following:

1. Write an include file test123.inc that includes all of the guts of your 
recipe.

2. Write the two recipes test123-config-XXX_1.0.bb and test123-config-
YYY_1.0.bb:

test123-config-XXX_1.0.bb

require test123.inc

SRC_URI += "test123-XXX.conf"

do_install_append() {
   # install config file here
   install 544 test123-XXX.conf ${D}/ }

RCONFLICTS_${PN} = "test123-config-YYY"

Analog for test123-config-YYY_1.0.bb


You are essentially sharing all of the recipe through the test123.inc and only 
add the config file to the respective target recipe. The RCONFLICTS_${PN} 
directive will flag an error if both conflicting packages are attempted to be 
installed.

BR,
Rudi

Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist 
ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese 
E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und 
vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform 
(mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen 
Schriftstücks per Telefax erfolgen.

Important note: The information included in this e-mail is confidential. It is 
solely intended for the recipient. If you are not the intended recipient of 
this e-mail please contact the sender and delete this message. Thank you. 
Without prejudice of e-mail correspondence, our statements are only legally 
binding when they are made in the conventional written form (with personal 
signature) or when such documents are sent by fax.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Bitbake does not apply changes and sometimes it removes the kernel-source directory

2016-02-22 Thread simo 
Hi all,

I am using a 'poky fido 13.0.1' Yocto distribution and I am experiencing
some problem after modifying the Linux kernel code and recompiling it.

Bitbake is not applying the changes and sometimes deletes the source
folder (but I have a backup, of course).

>From yocto environment shell, I execute:

~$ bitbake linux-gumstix -c compile -f

and then to create an image and having a kernel file compiled available:

~$ bitbake core-image-base

What is the best way to recompile an edited source with bitbake from
shell ? And why it removes the kernel-source directory ?

Thank you in advance for your help.

Regards,
Simon

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

[yocto] Qt5browser-problem

2016-02-22 Thread Surya 

Hello,

Is there any qt5 webbrowser based on qtwebkit or webengine ,which works 
with audio video application? I have worked on otter-browser,snowshoe 
,but in all cases i can only access normal pages like google.com 
etc.,,but streaming is not possible.I cant see youtube videos or any 
video application. Any suggestion on this ..




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