On Fri, 2012-04-27 at 22:44 -0700, Darren Hart wrote:
>
> On 04/27/2012 05:25 PM, tom.zanu...@intel.com wrote:
> > From: Tom Zanussi
> >
> > The current yocto-bsp help assumes knowledge that the meta-intel layer
> > needs to be cloned before it's put into the BBLAYERS. Avoid the
> > guesswork a
On 04/27/2012 05:25 PM, tom.zanu...@intel.com wrote:
> From: Tom Zanussi
>
> The current yocto-bsp help assumes knowledge that the meta-intel layer
> needs to be cloned before it's put into the BBLAYERS. Avoid the
> guesswork and state the details explicitly in the help.
>
> Also, the shorter
On 04/27/2012 05:25 PM, tom.zanu...@intel.com wrote:
> From: Tom Zanussi
>
> The current code assumes that builddir == srcdir/build, which it
> obviously isn't sometimes. Use BUILDDIR to get the actual builddir
> being used.
>
> Fixes [YOCTO #2219].
>
> Signed-off-by: Tom Zanussi
Acked-by:
On Fri, 2012-04-27 at 17:01 -0700, Darren Hart wrote:
>
> On 04/27/2012 12:00 PM, tom.zanu...@intel.com wrote:
> > From: Tom Zanussi
> >
> > The current yocto-bsp help assumes knowledge that the meta-intel layer
> > needs to be cloned before it's put into the BBLAYERS. Avoid the
> > guesswork a
From: Tom Zanussi
The current yocto-bsp help assumes knowledge that the meta-intel layer
needs to be cloned before it's put into the BBLAYERS. Avoid the
guesswork and state the details explicitly in the help.
Also, the shorter 'usage' string doesn't mention it at all; it would
help to at minimu
From: Tom Zanussi
The current code assumes that builddir == srcdir/build, which it
obviously isn't sometimes. Use BUILDDIR to get the actual builddir
being used.
Fixes [YOCTO #2219].
Signed-off-by: Tom Zanussi
---
scripts/lib/bsp/kernel.py |7 ++-
1 files changed, 6 insertions(+), 1
From: Tom Zanussi
Fixes for a couple yocto-bsp bugs.
v2: fixed up the yocto-bsp help text as suggested by Darren Hart.
The following changes since commit c47a869308cb0cccde0b1aee9a001352c99a8395:
Richard Purdie (1):
netbase: Correctly set FILESEXTRAPATHS to include the version
are av
On 04/27/2012 12:00 PM, tom.zanu...@intel.com wrote:
> From: Tom Zanussi
>
> The current yocto-bsp help assumes knowledge that the meta-intel layer
> needs to be cloned before it's put into the BBLAYERS. Avoid the
> guesswork and state the details explicitly in the help.
>
> Also, the shorter
On 04/27/2012 12:00 PM, tom.zanu...@intel.com wrote:
> From: Tom Zanussi
>
> The current code assumes that builddir == srcdir/build, which it
> obviously isn't sometimes. Use BUILDDIR to get the actual builddir
> being used.
>
> Fixes [YOCTO #2219].
>
> Signed-off-by: Tom Zanussi
> ---
> s
a potential training client of mine would like an intro embedded
linux course ideally on a MIPS-based dev kit. i'm aware that the
reference BSP for that in yocto is the routerstation pro, but i just
learned today that it's "end of life" so i'd rather get something
newer.
any recommendations
On Fri, Apr 27, 2012 at 4:18 PM, Thomas Fitzsimmons wrote:
> Hi,
>
> Are there plans in the Yocto roadmap to make the meta/scripts/kgit tools
> generally usable?
>
> I like the organization of the Yocto kernel repository and for my
> embedded project I'm considering using the Yocto build system al
On 01/10/2012 05:32 AM, Martin Donnelly wrote:
This patch fixes the following Augeas configure error.
| checking for LIBXML... no
| configure: error: Package requirements (libxml-2.0) were not met:
|
| No package 'libxml-2.0' found
|
| Consider adjusting the PKG_CONFIG_PATH environment variable
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:16010101T02000
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:16010101T02000
Hi,
Are there plans in the Yocto roadmap to make the meta/scripts/kgit tools
generally usable?
I like the organization of the Yocto kernel repository and for my
embedded project I'm considering using the Yocto build system along with
a Yocto-style kernel tree instead of maintaining my kernel patc
There was a possible error during the Bugzilla upgrade today. We have
rolled back to the current version out of caution. Total downtime was 9
minutes. No data was affected.
We are rescheduling to run the upgrade again in 48 hours.
Bugzilla will temporarily go offline on Sunday April 29th 2012 at
On 04/27/2012 11:39 AM, McClintock Matthew-B29882 wrote:
On Fri, Apr 27, 2012 at 9:15 AM, jfabernathy wrote:
Over the past 6 months, I've learned a lot about what I should do to work
with Yocto successfully, However, the area of biggest confusion for me is
what to do when I want to rebuild some
On Fri, Apr 27, 2012 at 9:15 AM, jfabernathy wrote:
> Over the past 6 months, I've learned a lot about what I should do to work
> with Yocto successfully, However, the area of biggest confusion for me is
> what to do when I want to rebuild something.
>
> I generally work from Master repository and
Over the past 6 months, I've learned a lot about what I should do to
work with Yocto successfully, However, the area of biggest confusion for
me is what to do when I want to rebuild something.
I generally work from Master repository and when I see significant
changes while doing git pull, I tr
Op 27 apr. 2012, om 08:39 heeft Koen Kooi het volgende geschreven:
>
> Op 26 apr. 2012, om 20:52 heeft Martin Jansa het volgende geschreven:
>
>> On Thu, Apr 26, 2012 at 06:21:45PM +0200, Koen Kooi wrote:
>>>
>>> Op 26 apr. 2012, om 12:43 heeft Richard Purdie het volgende geschreven:
>>>
Hi,
Is there a preferred way to build an image with a read-only rootfs using
Yocto (poky-edison-6.0.1)? Are there recipes available which can be used?
I use a custom image by inheriting from image.bbclass and defining a
couple of custom tasks.
Best Regards,
Johannes
_
21 matches
Mail list logo