On 02/24/2012 02:33 PM, Saxena, Rahul wrote:
>
>
> Had a question on Glib. The configuration script of one of the packages
> I am trying to build requires glib >= 2.31.10 ,
>
> but the Edision branch has 2.28 version. What does one generally do in
> these type of cases ?
You can backport glib
On Thu, Mar 1, 2012 at 12:30 AM, Khem Raj wrote:
> On 02/24/2012 10:04 AM, Autif Khan wrote:
>> I have a touchscreen made by AUO. It came with a driver which I have
>> written a recipe for and it seems to be compiling and when the
>> touchscreen is detected, the driver seems to be loading and
>> c
On 02/24/2012 10:04 AM, Autif Khan wrote:
> I have a touchscreen made by AUO. It came with a driver which I have
> written a recipe for and it seems to be compiling and when the
> touchscreen is detected, the driver seems to be loading and
> controlling the touchscreen. (Its not under the control o
On 02/29/2012 04:27 PM, Chris Larson wrote:
> On Wed, Feb 29, 2012 at 5:11 PM, Darren Hart wrote:
>> When a new user goes to write a recipe and add a patch or other file,
>> they need to understand FILESDIR and where to put these additional
>> files. I scanned the reference manual and the dev ma
On Wed, Feb 29, 2012 at 5:11 PM, Darren Hart wrote:
> When a new user goes to write a recipe and add a patch or other file,
> they need to understand FILESDIR and where to put these additional
> files. I scanned the reference manual and the dev manual and came up
> mostly empty handed. The one gli
From: Kishore Bodke
Hi,
This patch is to enable Cedarview config parameters and add the kernel patches
to the yocto/pvr branch in linux-yocto-3.0 and linux-yocto-3.2 tree.
Thanks
Kishore.
The following changes since commit 07e83cbd3e62a0bf91f558337aa7e37bc09f100b:
Merge commit 'v3.0.22' i
When a new user goes to write a recipe and add a patch or other file,
they need to understand FILESDIR and where to put these additional
files. I scanned the reference manual and the dev manual and came up
mostly empty handed. The one glipse of it is in section 5.1.4 of the
Reference Manual:
"
It
for unknown reasons, my host went away for a while but it's back up
now, so here's my idea for a quick start guide:
http://www.crashcourse.ca/wiki/index.php/Yocto_Project_Quick_Start
thoughts? i'm going to add a few more "advanced" sections but the
focus is on getting up and running as quickl
On 02/29/2012 03:35 PM, Gary Thomas wrote:
On 2012-02-29 13:32, jfabernathy wrote:
Just for fun, I thought I'd build meta-cedartrail today since I saw
1.2_M3 branch show up when I did a git pull today. The only thing I
did above the basic BSP was to include my
meta-jfa layer which is nothing mo
Bob,
Thanks! Do you have a branch I can cherry-pick this from? If not, I'll
just commit with attribution.
-b
On Wed, Feb 29, 2012 at 10:05 AM, Bob Cochran wrote:
> I have noticed in the nightly buildbot failure reports for ppc & mips that
> the build names are switched (e.g., nightly-mips trigg
On 02/29/2012 03:35 PM, Gary Thomas wrote:
On 2012-02-29 13:32, jfabernathy wrote:
Just for fun, I thought I'd build meta-cedartrail today since I saw
1.2_M3 branch show up when I did a git pull today. The only thing I
did above the basic BSP was to include my
meta-jfa layer which is nothing mo
On 02/29/2012 03:35 PM, Gary Thomas wrote:
On 2012-02-29 13:32, jfabernathy wrote:
Just for fun, I thought I'd build meta-cedartrail today since I saw
1.2_M3 branch show up when I did a git pull today. The only thing I
did above the basic BSP was to include my
meta-jfa layer which is nothing mo
On 2012-02-29 13:32, jfabernathy wrote:
Just for fun, I thought I'd build meta-cedartrail today since I saw 1.2_M3
branch show up when I did a git pull today. The only thing I did above the
basic BSP was to include my
meta-jfa layer which is nothing more than my hello world application and
web
Just for fun, I thought I'd build meta-cedartrail today since I saw
1.2_M3 branch show up when I did a git pull today. The only thing I did
above the basic BSP was to include my meta-jfa layer which is nothing
more than my hello world application and web-webkit, which is already in
the meta la
All,
This morning I branched poky/eclipse-poky/meta-qt3 for our 1.2_M3.rc
builds.
I am currently building 1.2_M3.rc1 with an ETA of 6pm PST. It will be
available at:
http://autobuilder.yoctoproject.org/pub/nightly/20120229-1
Please ensure that patches for rc2 are pulled to those branches as
I have noticed in the nightly buildbot failure reports for ppc & mips
that the build names are switched (e.g., nightly-mips triggers the
nightly-ppc build and vice versa).
The name and builderNames appear to be switched in yoctoABConfig.py, and
I think this patch will correct this one.
Sign
On Wednesday 29 February 2012 16:44:20 John Toomey wrote:
> You got me on the right track to fix it - apparently having a comment on
> the same line as the IMAGE_INSTALL += "..." causes it to break. I had
> all of the packates on seperate lines so I could easily comment in or
> out the ones I need
since it's easier to just write something than suggest numerous
fixes, i took less than an hour and wrote this:
http://www.crashcourse.ca/wiki/index.php/Yocto_Project_Quick_Start
it's the sort of thing that would have been perfect for me when i
first jumped into yocto.
i'm going to add a co
On 29/02/2012 16:18, Paul Eggleton wrote:
On Wednesday 29 February 2012 15:32:34 John Toomey wrote:
I am getting an error when I try to include some packages such as
logrotate, valgrind and minicom in my configuration using "IMAGE_INSTALL
+= ... "
ERROR: Nothing RPROVIDES '"minicom"' (but
On Wednesday 29 February 2012 15:32:34 John Toomey wrote:
> I am getting an error when I try to include some packages such as
> logrotate, valgrind and minicom in my configuration using "IMAGE_INSTALL
> += ... "
>
> ERROR: Nothing RPROVIDES '"minicom"' (but
> [path]/core-image-[blah].bb RD
On Wednesday 29 February 2012 10:50:30 Robert P. J. Day wrote:
> just starting to go thru the thread regarding the QS guide and i
> have to agree that there's probably too much lead-in when the people
> reading the QS guide are probably competent enough to just want the
> recipe, so it should be
This is a good idea Robert.
Scott
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Robert P. J. Day
Sent: Wednesday, February 29, 2012 9:28 AM
To: Yocto discussion list
Subject: [yocto] can someone add a README to the documentat
just starting to go thru the thread regarding the QS guide and i
have to agree that there's probably too much lead-in when the people
reading the QS guide are probably competent enough to just want the
recipe, so it should be shorter.
having said that, i think there is a note that should be *
Hello all,
I am getting an error when I try to include some packages such as
logrotate, valgrind and minicom in my configuration using "IMAGE_INSTALL
+= ... "
ERROR: Nothing RPROVIDES '"minicom"' (but
[path]/core-image-[blah].bb RDEPENDS on or otherwise requires it)
NOTE: Runtime tar
as it is, if someone new to yocto checks out the git tree and sees
the documentation/ directory, they'll immediately hop in there, see
the possible manuals and perhaps run "make" to try to build them, with
no results.
yes, the Makefile has internal documentation but, at the very least,
a READ
Thanks for noting this. What happens when we release software is that the
manuals are released as well. The released manuals become the "current"
version of the manuals. Any bugs or errors with the documentation are
addressed with the next version under development. We try our best to keep t
On Wed, 2012-02-29 at 14:46 +0800, Xu, Dongxiao wrote:
> I saw in initramfs-live-install_1.0.bb recipe, there is a line to set
> the COMPATIBLE_HOST:
>
> COMPATIBLE_HOST = "(i.86|x86_64).*-linux"
>
> But actually initramfs-live-install is set as dependency in
> core-image-minimal-initramfs.bb. Th
27 matches
Mail list logo
