currently, the yocto/poky ref manual, Appendix A.1, Top level core
components, doesn't mention the entries meta-yocto or meta-hob. it
also lists the meta-rt layer, which has been moved to oe-core.
i also don't think it should list build, as that's a generated
artifact and is documented
(i posted something regarding this on the oe-core list, but i wanted
to post here as well with specific examples from the yocto manuals.)
from the yocto dev manual, section 4.3.1:
The other method for creating a custom image is to modify an existing
image. For example, if a developer wants
On 03/08/2012 08:04 PM, Eric Bénard wrote:
Le Thu, 08 Mar 2012 17:38:40 -0500,
jfabernathyjfaberna...@gmail.com a écrit :
So what I can get to work is the following recipe, but what I want is
not o have to specify the file extension:
you may be able to build your archive in a directory like
Hi,
I wish to create bsp for our project in which we are
using arm1136 processor. I have created a layer (meta_EB)
same as meta for our project and have made required
changes in conf file for meta_EB to get compiled.
I am trying to bitbake -v meta-toolchain-qte, but it
gives me an error
On 03/09/2012 08:43 AM, Bruce Ashfield wrote:
On 12-03-09 07:20 AM, David Nyström wrote:
Hi All,
Whats yoctos take on LTSI ?
http://git.linuxfoundation.org/?p=ltsi-kernel.git;a=summary
http://lwn.net/Articles/484337/
I've noticed that LTT-ng and other kernel patches are independently
ported
On 12-03-09 09:36 AM, Bob Cochran wrote:
On 03/09/2012 08:43 AM, Bruce Ashfield wrote:
On 12-03-09 07:20 AM, David Nyström wrote:
Hi All,
Whats yoctos take on LTSI ?
http://git.linuxfoundation.org/?p=ltsi-kernel.git;a=summary
http://lwn.net/Articles/484337/
I've noticed that LTT-ng and
Hello all
I'm having problems compiling iputils with uclibc -
| ping6.o: In function `niquery_option_subject_name_handler':
|
/tmp/work/i586-poky-linux-uclibc/iputils-s20101006-r2/iputils-s20101006/ping6.c:428:
undefined reference to `dn_comp'
| collect2: ld returned 1 exit status
| make:
On Fri, Mar 9, 2012 at 7:18 AM, John Toomey john.too...@linux.intel.com wrote:
undefined reference to `dn_comp'
add LDFLAGS_libc-uclibc_append = -lresolv to recipe.
___
yocto mailing list
yocto@yoctoproject.org
I tried the versions _append and += as well as _prepend and =+ with the
IMAGE_INSTALL and other variables. So far I have not run into any issues
where one would behave differently from the other. The only thing you have
to remember with the _append and _prepend versions is that you have to
include
I don't think that there is a difference. At least not from my experience.
Every time I have the choice I tried both variants and then examined the
resulting variable e.g.
bitbake recipe -e | grep IMAGE_INSTALL
It looked the same. My conclusion is to use += and =+ for variables and
_append and
i've decided to stop nibbling around the edges and, once and for
all, figure out OpenEmbedded from beginning to end. to that end, i've
checked out oe-core and want to focus on just the fundamentals.
the current openembedded manual here:
On 12-03-09 02:03 PM, kishore.k.bo...@intel.com wrote:
From: Kishore Bodkekishore.k.bo...@intel.com
Hi,
These addtional patches enable Cedarview hdmi and acpi.
Please pull thme to the yocto/pvr branch in linux-yocto-3.0 tree.
Looks fine. will Merge it shortly and send a confirmation.
Bruce
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
Hi all,
It's that time again. We are starting the Beta program for Yocto Project 1.2
release. This release focuses on usability of the Yocto Project. HOB2 is the
second version of our Human Oriented Builder (GUI based), which will help
developers build customized Linux image in a much more
14 matches
Mail list logo
