This mail was sent out by Package Report System.
It will list all the recipes which can't check upstream version by script, and
will show how long it is since their last mannual version check.
You can check the detail information at
http://packages.yoctoproject.org/manuallychkinfo
PackageName
This mail was sent out by Package Report System.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade this time, they can fill in
RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this
recipe remainder until newer u
On Sat, Dec 15, 2012 at 10:53 AM, Trevor Woerner wrote:
> On Thu, Dec 13, 2012 at 10:18 AM, Rifenbark, Scott M
> wrote:
> > we are revising the BitBake manual as part of the YP 1.4 release
>
>
> Personally I think it would be great if the bitbake documentation
> could be updated to include some
On 12/14/12 21:57, Brian Hutchinson wrote:
On Fri, Dec 14, 2012 at 4:09 PM, Zhang, Jessica wrote:
Actually I talked with Richard regarding retiring the toolchain targets
(meta-toolchain and meta-toolchain-gmae) as Mark mentioned that now we can build a
toolchain matching the >image. Also, we
Hi,
I have defined the following variables defined
SOC_FAMILY = virtex-5 in my virtex-5.inc file, which is included by my
virtex-5-ml507-powerpc-440.conf machine configuration file.
I have defined MACHINE=virtex-4-ml507-powerpc-440 in my local.conf file
In my u-boot-xilinx.git recipe, I
On Thu, Dec 13, 2012 at 10:18 AM, Rifenbark, Scott M
wrote:
> we are revising the BitBake manual as part of the YP 1.4 release
Personally I think it would be great if the bitbake documentation
could be updated to include some of the information from Eren's
document as well. Eren provides a "hand
I apologize if I'm pointing out the obvious and/or something you've
already tried.
On Thu, Dec 13, 2012 at 11:22 AM, Andrea Galbusera wrote:
> After reading the manual I understand that the ${AUTOREV} method is
> not working with cvs. Is there an alternative approach to instruct the
> fetcher to
Hi,
can anybody explain to me the systematics of the git tags ysed to mark
the Yocto / Poky releases?
For example, for Yocto 1.2 and before, we have release tags like
denzil-7.0, edison-6.0, bernard-5.0, laverne-4.0, etc.
Some parts of the current 1.3 Yocto release refer to it as "Poky 8.0"
or V
Is there a chance this can get included?
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
a general observation about something i've noticed about the yocto
docs in places. here's an example from the ADT manual, section
2.1.1.1:
"The following example commands download the Poky tarball, set up the
Source Directory, set up the environment while also creating the
default Build Direct
On Fri, 14 Dec 2012, Tim Bird wrote:
> On 12/14/2012 12:45 PM, Mark Hatle wrote:
> > On 12/14/12 1:46 PM, Burton, Ross wrote:
> >> On 14 December 2012 19:43, Tim Bird wrote:
> >>> "If you need GMAE, you should use the bitbake meta-toolchain-gmae
> >>> command. The resulting installation script w
11 matches
Mail list logo
