[yocto] Can i add two git sources in one single recipe

[Vivek Per]

hi,
  Can i add two git source url in one recipe(SRC_URI).
If so how can i add and how can i give source revision for two these files
in one recipe.
Can any one overcome this iissue.
   Thanks in advance


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

Re: [yocto] Can i add two git sources in one single recipe

[Jussi Kukkonen]

On 15 October 2015 at 14:03, Vivek Per  wrote:

> hi,
>   Can i add two git source url in one recipe(SRC_URI).
> If so how can i add and how can i give source revision for two these files
> in one recipe.
>

Name the SRC_URIs, then set SRCREV_ for each of those. Example from
gstreamer1.0-omx:

SRC_URI = " \
git://
anongit.freedesktop.org/gstreamer/gst-omx;branch=master;name=gst-omx \
git://
anongit.freedesktop.org/gstreamer/common;destsuffix=git/common;branch=master;name=common
\
file://0001-omx-fixed-type-error-in-printf-call.patch \
"
SRCREV_gst-omx = "a2db76b048db278ef0aa798e106b7594264e06c0"
SRCREV_common = "5edcd857b2107cd8b78c16232dd10877513ec157"

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

[yocto] how to deploy gdbserver ?

[Valentin Le bescond]

Hi everyone,

I want to be able to debug my target machine (raspberrypi) remotely through
qtcretor on host.

I can't seem to find a way to deploy the gdbserver software though.
I built the gdb-cross-arm but don't see any gdbserver on the target with
hob (poky 1.7.2) ?

What am I missing ?

Thanks


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

Re: [yocto] how to deploy gdbserver ?

[winfried . dobbe]

> Hi everyone,
>
> I want to be able to debug my target machine (raspberrypi) remotely
> through
> qtcretor on host.
>
> I can't seem to find a way to deploy the gdbserver software though.
> I built the gdb-cross-arm but don't see any gdbserver on the target with
> hob (poky 1.7.2) ?
>
> What am I missing ?

When I build my image with

EXTRA_IMAGE_FEATURES += "tools-debug"

both gdb and gdbserver are installed in the target rootfs. Remote
debugging worked out-of-the-box with QtCreator.




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

Re: [yocto] how to deploy gdbserver ?

[Daniel.]

Works fine with emacs also.

2015-10-15 10:44 GMT-03:00 :

> > Hi everyone,
> >
> > I want to be able to debug my target machine (raspberrypi) remotely
> > through
> > qtcretor on host.
> >
> > I can't seem to find a way to deploy the gdbserver software though.
> > I built the gdb-cross-arm but don't see any gdbserver on the target with
> > hob (poky 1.7.2) ?
> >
> > What am I missing ?
>
> When I build my image with
>
> EXTRA_IMAGE_FEATURES += "tools-debug"
>
> both gdb and gdbserver are installed in the target rootfs. Remote
> debugging worked out-of-the-box with QtCreator.
>
>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
*"Do or do not. There is no try"*
  *Yoda Master*
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] how to deploy gdbserver ?

[Valentin Le bescond]

Hello

I believe tools-debug works but unfortunately I have errors building libaio
and other stuff (it says
"tmp/sysroots/raspberrypi/usr/include/gnu/stubs.h:10:29: fatal error:
gnu/stubs-hard.h: No such file or directory")

Anyway, to stick with the initial question, thanks !


Le jeu. 15 oct. 2015 à 15:58, Daniel.  a écrit :

> Works fine with emacs also.
>
> 2015-10-15 10:44 GMT-03:00 :
>
>> > Hi everyone,
>> >
>> > I want to be able to debug my target machine (raspberrypi) remotely
>> > through
>> > qtcretor on host.
>> >
>> > I can't seem to find a way to deploy the gdbserver software though.
>> > I built the gdb-cross-arm but don't see any gdbserver on the target with
>> > hob (poky 1.7.2) ?
>> >
>> > What am I missing ?
>>
>> When I build my image with
>>
>> EXTRA_IMAGE_FEATURES += "tools-debug"
>>
>> both gdb and gdbserver are installed in the target rootfs. Remote
>> debugging worked out-of-the-box with QtCreator.
>>
>
>>
>>
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
>
>
> --
> *"Do or do not. There is no try"*
>   *Yoda Master*
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
Valentin LE BESCOND
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH V4 1/5] userland: Fix install prefix and generate pkgconfigs

[Joachim Schiele]

On 13.10.2015 19:13, Andrei Gherzan wrote:
> On Tue, Oct 13, 2015 at 02:14:28AM +0200, Joachim Schiele wrote:
>> On 03.10.2015 23:53, Andrei Gherzan wrote:
>>> On Sat, Oct 03, 2015 at 02:47:24PM -0700, Khem Raj wrote:
 On Sat, Oct 3, 2015 at 2:27 PM, Andrei Gherzan  wrote:
> On Sat, Oct 03, 2015 at 10:46:07PM +0200, Andrei Gherzan wrote:
>> On Sat, Oct 03, 2015 at 10:40:50PM +0200, Andrei Gherzan wrote:
>>> On Sat, Oct 03, 2015 at 10:33:12PM +0200, Andrei Gherzan wrote:
 On Sat, Oct 03, 2015 at 01:31:24PM -0700, Khem Raj wrote:
> On Sat, Oct 3, 2015 at 1:11 PM, Andrei Gherzan  
> wrote:
>> On Sat, Oct 03, 2015 at 01:06:55PM -0700, Khem Raj wrote:
>>> On Sat, Oct 3, 2015 at 12:18 PM, Andrei Gherzan  
>>> wrote:
 I tested with and without - same result.
 DISTRO_FEATURES="alsa argp bluetooth ext2 irda largefile pcmcia 
 usbgadget
 usbhost wifi xattr nfs zeroconf pci 3g nfc x11 ipv4 ipv6 
 libc-backtrace
 libc-big-macros libc-bsd libc-cxx-tests libc-catgets libc-charsets 
 libc-crypt
 libc-crypt-ufc libc-db-aliases libc-envz libc-fcvt libc-fmtmsg 
 libc-fstab
 libc-ftraverse  libc-getlogin libc-idn 
 libc-inet-anl libc-libm
 libc-locales libc-locale-code   libc-memusage 
 libc-nis
 libc-nsswitch libc-rcmd libc-rtld-debug libc-spawn libc-streams 
 libc-sunrpc
 libc-utmp libc-utmpx libc-wordexp libc-posix-clang-wchar 
 libc-posix-regexp
 libc-posix-regexp-glibc libc-posix-wchar-io 
 largefile
 opengl ptest multiarch wayland pulseaudio sysvinit bluez5"

 No modification to the default poky distro.
>>>
>>> hmm I am using angstrom and it works there and for verification I 
>>> now
>>> tried with OE-Core ( alone ) it works there too, can you check some
>>> other parameters that are there in your sandbox ? here is my build
>>>
>>>  MACHINE=raspberrypi2 bitbake userland
>>> Parsing recipes: 100%
>>> |##|
>>> ETA:  00:00:00
>>> Parsing of 918 .bb files complete (0 cached, 918 parsed). 1350
>>> targets, 59 skipped, 0 masked, 0 errors.
>>> NOTE: Resolving any missing task queue dependencies
>>>
>>> Build Configuration:
>>> BB_VERSION= "1.28.0"
>>> BUILD_SYS = "x86_64-linux"
>>> NATIVELSBSTRING   = "Ubuntu-14.04"
>>> TARGET_SYS= "arm-oe-linux-gnueabi"
>>> MACHINE   = "raspberrypi2"
>>> DISTRO= "nodistro"
>>> DISTRO_VERSION= "nodistro.0"
>>> TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard
>>> vfpv4 cortexa7"
>>> TARGET_FPU= "vfp-vfpv4-neon"
>>> meta-raspberrypi  = 
>>> "kraj/master:a903a9cd18ae556121265da93ed74f857944a0da"
>>> meta  = 
>>> "kraj/master:602e512b92bcc78403144fedeb4211bbf56ff1c8"
>>>
>>> NOTE: Preparing RunQueue
>>> NOTE: Executing SetScene Tasks
>>> NOTE: Executing RunQueue Tasks
>>> NOTE: Tasks Summary: Attempted 454 tasks of which 315 didn't need to
>>> be rerun and all succeeded.
>>
>> Here is my build configuration.
>>
>> Build Configuration:
>> BB_VERSION= "1.28.0"
>> BUILD_SYS = "x86_64-linux"
>> NATIVELSBSTRING   = "Arch-rolling"
>> TARGET_SYS= "arm-poky-linux-gnueabi"
>> MACHINE   = "raspberrypi2"
>> DISTRO= "poky"
>> DISTRO_VERSION= "2.0"
>> TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard 
>> vfpv4
>> cortexa7"
>> TARGET_FPU= "vfp-vfpv4-neon"
>> meta
>> meta-yocto
>> meta-yocto-bsp= "master:eac61f37e36099f74485dab398b57f3812826d17"
>> meta-raspberrypi  = "master:48da0cdc5fb147a20b41a77b2dfeef4efd483b32"
>> meta-oe
>> meta-multimedia   = "master:f4533380c8a5c1d229f69ee0c2ef9d187ef8"
>>
>>
>> But anyway can you please check in your userland install dir for the 
>> header I'm
>> missing? Or in sysroot.
>
> its part of userland itself so no other package should be needed and
> not required in sysroot
>
> ./work/raspberrypi2-oe-linux-gnueabi/userland/git-r5/package/usr/src/debug/userland/git-r5/build/interface/vmcs_host/wayland-dispmanx-server-protocol.h

Re: [yocto] how to deploy gdbserver ?

[Gary Thomas]

On 2015-10-15 08:39, Valentin Le bescond wrote:

Hello

I believe tools-debug works but unfortunately I have errors building libaio and 
other stuff (it says "tmp/sysroots/raspberrypi/usr/include/gnu/stubs.h:10:29: 
fatal error:
gnu/stubs-hard.h: No such file or directory")


Can you send more details about this error (what version of Yocto meta-data you 
are using, etc)?
I just built this for the RaspberryPi and RaspberryPi2 using Poky/Yocto master 
(jethro) with no problems.



Anyway, to stick with the initial question, thanks !


Le jeu. 15 oct. 2015 à 15:58, Daniel. mailto:danielhi...@gmail.com>> a écrit :

Works fine with emacs also.

2015-10-15 10:44 GMT-03:00 mailto:winfried.do...@xmsnet.nl>>:

> Hi everyone,
>
> I want to be able to debug my target machine (raspberrypi) remotely
> through
> qtcretor on host.
>
> I can't seem to find a way to deploy the gdbserver software though.
> I built the gdb-cross-arm but don't see any gdbserver on the target 
with
> hob (poky 1.7.2) ?
>
> What am I missing ?

When I build my image with

EXTRA_IMAGE_FEATURES += "tools-debug"

both gdb and gdbserver are installed in the target rootfs. Remote
debugging worked out-of-the-box with QtCreator.





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




--
/"Do or do not. There is no try"/
///*Yoda Master*/
--
___
yocto mailing list
yocto@yoctoproject.org 
https://lists.yoctoproject.org/listinfo/yocto

--
Valentin LE BESCOND




--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

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

Re: [yocto] how to deploy gdbserver ?

[Valentin Le bescond]

sure !

something like this ?

Build Configuration:
BB_VERSION = "1.24.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Fedora-22"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "raspberrypi"
DISTRO = "poky"
DISTRO_VERSION = "1.7.2"
TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"
TARGET_FPU = "vfp"
meta
meta-yocto
meta-yocto-bsp = "dizzy:85f6cf736b5ecf3af6d1596b782dae81b9ac1f11"
meta-raspberrypi = "fido:b896a7da70dd7a16ba7ffd664f7747cb37e1d142"
meta-networking
meta-ruby
meta-oe
meta-python = "dizzy:5b6f39ce325d490fc382d5d59c5b8b9d5fa38b38"



Le jeu. 15 oct. 2015 à 17:10, Gary Thomas  a écrit :

> On 2015-10-15 08:39, Valentin Le bescond wrote:
> > Hello
> >
> > I believe tools-debug works but unfortunately I have errors building
> libaio and other stuff (it says
> "tmp/sysroots/raspberrypi/usr/include/gnu/stubs.h:10:29: fatal error:
> > gnu/stubs-hard.h: No such file or directory")
>
> Can you send more details about this error (what version of Yocto
> meta-data you are using, etc)?
> I just built this for the RaspberryPi and RaspberryPi2 using Poky/Yocto
> master (jethro) with no problems.
>
> >
> > Anyway, to stick with the initial question, thanks !
> >
> >
> > Le jeu. 15 oct. 2015 à 15:58, Daniel.  danielhi...@gmail.com>> a écrit :
> >
> > Works fine with emacs also.
> >
> > 2015-10-15 10:44 GMT-03:00  winfried.do...@xmsnet.nl>>:
> >
> > > Hi everyone,
> > >
> > > I want to be able to debug my target machine (raspberrypi)
> remotely
> > > through
> > > qtcretor on host.
> > >
> > > I can't seem to find a way to deploy the gdbserver software
> though.
> > > I built the gdb-cross-arm but don't see any gdbserver on the
> target with
> > > hob (poky 1.7.2) ?
> > >
> > > What am I missing ?
> >
> > When I build my image with
> >
> > EXTRA_IMAGE_FEATURES += "tools-debug"
> >
> > both gdb and gdbserver are installed in the target rootfs. Remote
> > debugging worked out-of-the-box with QtCreator.
> >
> >
> >
> >
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org 
> > https://lists.yoctoproject.org/listinfo/yocto
> >
> >
> >
> >
> > --
> > /"Do or do not. There is no try"/
> > ///*Yoda Master*/
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org 
> > https://lists.yoctoproject.org/listinfo/yocto
> >
> > --
> > Valentin LE BESCOND
> >
> >
>
> --
> 
> Gary Thomas |  Consulting for the
> MLB Associates  |Embedded world
> 
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
Valentin LE BESCOND
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] how to deploy gdbserver ?

[Gary Thomas]

On 2015-10-15 09:16, Valentin Le bescond wrote:

sure !

something like this ?

Build Configuration:
BB_VERSION = "1.24.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Fedora-22"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "raspberrypi"
DISTRO = "poky"
DISTRO_VERSION = "1.7.2"
TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"
TARGET_FPU = "vfp"
meta
meta-yocto
meta-yocto-bsp = "dizzy:85f6cf736b5ecf3af6d1596b782dae81b9ac1f11"
meta-raspberrypi = "fido:b896a7da70dd7a16ba7ffd664f7747cb37e1d142"
meta-networking
meta-ruby
meta-oe
meta-python = "dizzy:5b6f39ce325d490fc382d5d59c5b8b9d5fa38b38"


I think you'd be better off by updating to later branches and also you should 
try
to use corresponding branches (e.g. mixing dizzy and fido is probably a source
for problems).





Le jeu. 15 oct. 2015 à 17:10, Gary Thomas mailto:g...@mlbassoc.com>> a écrit :

On 2015-10-15 08:39, Valentin Le bescond wrote:
> Hello
>
> I believe tools-debug works but unfortunately I have errors building libaio 
and other stuff (it says "tmp/sysroots/raspberrypi/usr/include/gnu/stubs.h:10:29: 
fatal error:
> gnu/stubs-hard.h: No such file or directory")

Can you send more details about this error (what version of Yocto meta-data 
you are using, etc)?
I just built this for the RaspberryPi and RaspberryPi2 using Poky/Yocto 
master (jethro) with no problems.

>
> Anyway, to stick with the initial question, thanks !
>
>
> Le jeu. 15 oct. 2015 à 15:58, Daniel. mailto:danielhi...@gmail.com> >> a écrit :
>
> Works fine with emacs also.
>
> 2015-10-15 10:44 GMT-03:00 mailto:winfried.do...@xmsnet.nl> >>:
>
> > Hi everyone,
> >
> > I want to be able to debug my target machine (raspberrypi) 
remotely
> > through
> > qtcretor on host.
> >
> > I can't seem to find a way to deploy the gdbserver software 
though.
> > I built the gdb-cross-arm but don't see any gdbserver on the 
target with
> > hob (poky 1.7.2) ?
> >
> > What am I missing ?
>
> When I build my image with
>
> EXTRA_IMAGE_FEATURES += "tools-debug"
>
> both gdb and gdbserver are installed in the target rootfs. Remote
> debugging worked out-of-the-box with QtCreator.
>
>
>
>
>
> --
> ___
> yocto mailing list
>yocto@yoctoproject.org  
>
>https://lists.yoctoproject.org/listinfo/yocto
>
>
>
>
> --
> /"Do or do not. There is no try"/
> ///*Yoda Master*/
> --
> ___
> yocto mailing list
>yocto@yoctoproject.org  
>
>https://lists.yoctoproject.org/listinfo/yocto
>
> --
> Valentin LE BESCOND
>
>

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

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

--
Valentin LE BESCOND


--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

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

Re: [yocto] how to deploy gdbserver ?

[Valentin Le bescond]

Good point.

But so far my experience with yocto forced me to go back and forth the 1.6
1.7 and 1.8 branches depending on the layers.

So I kind of stopped where it worked... without worrying about gdb that's
true.

I won't go updating everything for testing purpose right now so I'll leave
it like that

Thanks !


Le jeu. 15 oct. 2015 à 17:31, Gary Thomas  a écrit :

> On 2015-10-15 09:16, Valentin Le bescond wrote:
> > sure !
> >
> > something like this ?
> >
> > Build Configuration:
> > BB_VERSION = "1.24.0"
> > BUILD_SYS = "x86_64-linux"
> > NATIVELSBSTRING = "Fedora-22"
> > TARGET_SYS = "arm-poky-linux-gnueabi"
> > MACHINE = "raspberrypi"
> > DISTRO = "poky"
> > DISTRO_VERSION = "1.7.2"
> > TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"
> > TARGET_FPU = "vfp"
> > meta
> > meta-yocto
> > meta-yocto-bsp = "dizzy:85f6cf736b5ecf3af6d1596b782dae81b9ac1f11"
> > meta-raspberrypi = "fido:b896a7da70dd7a16ba7ffd664f7747cb37e1d142"
> > meta-networking
> > meta-ruby
> > meta-oe
> > meta-python = "dizzy:5b6f39ce325d490fc382d5d59c5b8b9d5fa38b38"
>
> I think you'd be better off by updating to later branches and also you
> should try
> to use corresponding branches (e.g. mixing dizzy and fido is probably a
> source
> for problems).
>
> >
> >
> >
> > Le jeu. 15 oct. 2015 à 17:10, Gary Thomas  g...@mlbassoc.com>> a écrit :
> >
> > On 2015-10-15 08:39, Valentin Le bescond wrote:
> > > Hello
> > >
> > > I believe tools-debug works but unfortunately I have errors
> building libaio and other stuff (it says
> "tmp/sysroots/raspberrypi/usr/include/gnu/stubs.h:10:29: fatal error:
> > > gnu/stubs-hard.h: No such file or directory")
> >
> > Can you send more details about this error (what version of Yocto
> meta-data you are using, etc)?
> > I just built this for the RaspberryPi and RaspberryPi2 using
> Poky/Yocto master (jethro) with no problems.
> >
> > >
> > > Anyway, to stick with the initial question, thanks !
> > >
> > >
> > > Le jeu. 15 oct. 2015 à 15:58, Daniel.   >> a écrit :
> > >
> > > Works fine with emacs also.
> > >
> > > 2015-10-15 10:44 GMT-03:00  winfried.do...@xmsnet.nl> >>:
> > >
> > > > Hi everyone,
> > > >
> > > > I want to be able to debug my target machine
> (raspberrypi) remotely
> > > > through
> > > > qtcretor on host.
> > > >
> > > > I can't seem to find a way to deploy the gdbserver
> software though.
> > > > I built the gdb-cross-arm but don't see any gdbserver on
> the target with
> > > > hob (poky 1.7.2) ?
> > > >
> > > > What am I missing ?
> > >
> > > When I build my image with
> > >
> > > EXTRA_IMAGE_FEATURES += "tools-debug"
> > >
> > > both gdb and gdbserver are installed in the target rootfs.
> Remote
> > > debugging worked out-of-the-box with QtCreator.
> > >
> > >
> > >
> > >
> > >
> > > --
> > > ___
> > > yocto mailing list
> > >yocto@yoctoproject.org   yocto@yoctoproject.org >
> > >https://lists.yoctoproject.org/listinfo/yocto
> > >
> > >
> > >
> > >
> > > --
> > > /"Do or do not. There is no try"/
> > > ///*Yoda Master*/
> > > --
> > > ___
> > > yocto mailing list
> > >yocto@yoctoproject.org   yocto@yoctoproject.org >
> > >https://lists.yoctoproject.org/listinfo/yocto
> > >
> > > --
> > > Valentin LE BESCOND
> > >
> > >
> >
> > --
> > 
> > Gary Thomas |  Consulting for the
> > MLB Associates  |Embedded world
> > 
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org 
> > https://lists.yoctoproject.org/listinfo/yocto
> >
> > --
> > Valentin LE BESCOND
>
> --
> 
> Gary Thomas |  Consulting for the
> MLB Associates  |Embedded world
> 
>
-- 
Valentin LE BESCOND
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] RFC: Yocto LTS?

[Philip Balister]

On 10/14/2015 12:26 PM, Chris Simmonds wrote:
> 
> On 14/10/15 17:27, Mark Hatle wrote:
>> On 10/14/15 8:28 AM, Chris Simmonds wrote:
>>> Hi,
>>>
>>> Is there a statement about the period of support for a Yocto release?
>>> Looking through the updates, it seems that 12 months is typical, a was
>>> the case for 1.4, 1.5 and 1.6 for example, but I cannot see a
>>> declaration anywhere that this is the expected norm.
>>>
>>> Leading on from that, is 12 months enough? Most projects have a
>>> lifecycle that is much longer. Is there an argument for an LTS Yocto
>>> release, maybe once a year? If not, what is the recommended way for a
>>> project developer to keep a distribution up to date in the light of the
>>> several well-publicised security flaws that have been discovered over
>>> the last year or so and the new ones that will no doubt be discovered in
>>> the future?
>>
>> https://wiki.yoctoproject.org/wiki/FAQ#What_is_the_overall_support_plan_for_the_Yocto_Project.3F
>>
>> =What is the release cycle of the Yocto Project?=
>> Each release of the Yocto Project is subject to its own release schedule
>> according to the community-maintained Project Planning Guide. It is generally
>> expected that a new version of the Yocto Project will be released every six 
>> months.
>>
>> =What is the overall support plan for the Yocto Project?=
>> Security patches and critical bug fixes are supplied one release back. No
>> toolchain or kernel changes are allowed for these updates. Support for longer
>> periods of time can be supplied by commercial OSVs.
>>
>>
>>
>> Effectively this means that support is on the last two releases.  Releases 
>> are
>> typically released every 6 months.  After that point it is usually supported 
>> by
>> OSVs, or others that offer commercial services.  In the past we have done a 
>> few
>> very late security fixes past the 'last two releases' point, however that has
>> been for unique situations.
>>
>> You should consider keeping current with the Yocto Project releases or 
>> consider
>> commercial support if you need more then an approx 12 - 18 month support 
>> cycle.
>>
>> --Mark
>>
> 
> Thanks, that is all clear now.

We wouldn't be opposed to a group of people supporting a release for
longer. But they would need to provide the people to do the work. LTS
work is hard.

Philip

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

[yocto] meta-raspberrypi no soud output

[Edward Vidal]

Hello All,Does any have snd working on Raspberry Pi 2B?
I have tried aplay speech_dft.wavPLAYING WAVE: 'speech_dft.wav' :  Signed 16 
bit Little Endian, rate 22050 Hz Monowith ear plugs or speaker no snd.Any and 
all help appreciated.
Regards.
 Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Package inclusion

[Carlos Sánchez de La Lama]

Hi all,

I have some doubts on how package inclusion in images is determined. For
example, when building core-image-base, I would say that both

kernel-module-uvesafb
kernel-module-input

are recommended (through RRECOMENDS in packagegroup-base).

However, -uvesafb makes it to the final image, whereas -input does not.
I double-checked on the running system under QEMU *and* reading the
image manifest at
tmp/deploy/images/qemux86/core-image-base-qemux86.manifest

I must be missing something. Can someone give me a pointer?

Thanks a lot, BR

Carlos

-- 
-Debemos anhelar no sólo la verdad, sino también la virtud -sentenció
Pitágoras-. El conocimiento que se obtiene mediante oro, y no a través de un
merecimiento virtuoso, puede apartarnos del camino recto y ser nefasto para
nosotros y para nuestro entorno.

Marcos Chicot, "El asesinato de Pitágoras" (2013)
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] RFC: Yocto LTS?

[Chris Simmonds]

On 15/10/15 16:49, Philip Balister wrote:
> On 10/14/2015 12:26 PM, Chris Simmonds wrote:
>>
>> On 14/10/15 17:27, Mark Hatle wrote:
>>> On 10/14/15 8:28 AM, Chris Simmonds wrote:
 Hi,

 Is there a statement about the period of support for a Yocto release?
 Looking through the updates, it seems that 12 months is typical, a was
 the case for 1.4, 1.5 and 1.6 for example, but I cannot see a
 declaration anywhere that this is the expected norm.

 Leading on from that, is 12 months enough? Most projects have a
 lifecycle that is much longer. Is there an argument for an LTS Yocto
 release, maybe once a year? If not, what is the recommended way for a
 project developer to keep a distribution up to date in the light of the
 several well-publicised security flaws that have been discovered over
 the last year or so and the new ones that will no doubt be discovered in
 the future?
>>>
>>> https://wiki.yoctoproject.org/wiki/FAQ#What_is_the_overall_support_plan_for_the_Yocto_Project.3F
>>>
>>> =What is the release cycle of the Yocto Project?=
>>> Each release of the Yocto Project is subject to its own release schedule
>>> according to the community-maintained Project Planning Guide. It is 
>>> generally
>>> expected that a new version of the Yocto Project will be released every six 
>>> months.
>>>
>>> =What is the overall support plan for the Yocto Project?=
>>> Security patches and critical bug fixes are supplied one release back. No
>>> toolchain or kernel changes are allowed for these updates. Support for 
>>> longer
>>> periods of time can be supplied by commercial OSVs.
>>>
>>>
>>>
>>> Effectively this means that support is on the last two releases.  Releases 
>>> are
>>> typically released every 6 months.  After that point it is usually 
>>> supported by
>>> OSVs, or others that offer commercial services.  In the past we have done a 
>>> few
>>> very late security fixes past the 'last two releases' point, however that 
>>> has
>>> been for unique situations.
>>>
>>> You should consider keeping current with the Yocto Project releases or 
>>> consider
>>> commercial support if you need more then an approx 12 - 18 month support 
>>> cycle.
>>>
>>> --Mark
>>>
>>
>> Thanks, that is all clear now.
> 
> We wouldn't be opposed to a group of people supporting a release for
> longer. But they would need to provide the people to do the work. LTS
> work is hard.
> 
> Philip
> 
>>
>> Chris
>>
> 

Indeed, it is hard work. But there is a community out there with the
expertise and many very profitable corporations that depend on Yocto
Project (in addition to Intel, I mean, since they put a lot of resource
in already). It would be really nice if someone neutral - Linux
Foundation for example - could bring them together to make LTS work for
everybody.

Chris.


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