Hullo
I'm new to yocto, so I'm probably not going about this in the optimum way.
I'm trying to add package management to a yocto build. My preference would be
yum/rpm on a rh/centos/fedora distro (as that's the distro used elsewhere), but
I don't think that's feasible.
I've added:
[code]
On 12 December 2012 11:13, Tim Coote tim+yoctoproject@coote.org wrote:
I'm trying to add package management to a yocto build. My preference would be
yum/rpm on a rh/centos/fedora distro (as that's the distro used elsewhere),
but I don't think that's feasible.
I've added:
[code]
Thanks, Ross. That fixed that. Either I had finger trouble before when invoking
rpm or I needed to remove the ? from the ?= in PACKAGE_CLASSES ?= package_rpm
Am I right in thinking that yum isn't in the standard recipes?
Tim
On 12 Dec 2012, at 11:18, Burton, Ross ross.bur...@intel.com wrote:
On 12 December 2012 11:31, Tim Coote tim+yoctoproject@coote.org wrote:
Am I right in thinking that yum isn't in the standard recipes?
Yum, no. Zypper is in oe-core and is used when you construct a RPM-based image.
(note that Zypper is being replaced by Smart in oe-core master)
Ross
Allow vmdk images to be run through the 'runqemu' facility.
Signed-off-by: Trevor Woerner twoer...@gmail.com
---
scripts/runqemu | 39 +--
scripts/runqemu-internal | 20
2 files changed, 45 insertions(+), 14 deletions(-)
diff
Hi Scott,
Thank you for reviewing my patch.
On Wed, Dec 12, 2012 at 12:55 AM, Scott Garman scott.a.gar...@intel.com wrote:
This looks ok without having tested it personally. Could you just add a
signed-off-by line to the commit?
D'oh! Sorry about that. It has obviously been too long since I
- after creating the project, the wizard should not block waiting for the
environment to be populated and instead should be ran in the background
Signed-off-by: Ioana Grigoropol ioanax.grigoro...@intel.com
---
.../src/org/yocto/bc/bitbake/BBSession.java| 81
Hi Jessica,
I have sent a new patch that targets the downtime issue that you reported,
against windows-build current branch.
The downtime that you noticed it is due to the fact that with the current
implementation, the commands are ran synchronously, meaning that each command
must wait for the
ok. Thanks.
just spotted the split between rpm / rpm5 and yum. I suppose that the knock on
is managing multiple repos for different update managers.
don't suppose you know if there are material differences from a
packaging/dependency point of view between rpm4 and rpm5?
is there an eta for
On 12 December 2012 12:07, Tim Coote tim+yoctoproject@coote.org wrote:
don't suppose you know if there are material differences from a
packaging/dependency point of view between rpm4 and rpm5?
Not sure, I prefer opkg for Yocto and am a Debian user for my desktop.s
is there an eta for
Hi Jon,
Thanks for the clarification on which manual release you were looking at. I am
the technical writer for the project so hopefully someone from the team will
address the technical aspect of you issue. If there is a way to disable these
within a specific recipe then I can get that
On Monday 03 December 2012 10:19:00 Jon Szymaniak wrote:
Is there a simple way to disable the use of PREMIRRORS and MIRRORS
within a recipe?
(Perhaps the answer here might be worth mentioning in Section 12.23 of the
Poky Reference Manual?)
My use case for this is the situation where the
Hi,
m...@timomueller.eu wrote, On 06.12.2012 16:48:
From: Timo Mueller timo.muel...@bmw-carit.de
Hi,
since the last proposal some things have changed:
1. Eclipse help generation is now part of the yocto-docs project
(currently available in the origin/timo branch)
2. We agreed that the plugin
I just downloaded the Danny release to an Ubuntu 12.10 computer, and
pseudo failed to build. Before opening a bug, I just wanted to make sure
it's not something silly I am doing. The log file is attached and below
I've pasted the terminal output.
Thanks!
Belen
Pseudo is not present but is
On 12 December 2012 14:09, Barros Pena, Belen
belen.barros.p...@intel.com wrote:
I just downloaded the Danny release to an Ubuntu 12.10 computer, and
pseudo failed to build. Before opening a bug, I just wanted to make sure
it's not something silly I am doing. The log file is attached and below
On Wednesday 12 December 2012 14:15:50 Burton, Ross wrote:
On 12 December 2012 14:09, Barros Pena, Belen
belen.barros.p...@intel.com wrote:
I just downloaded the Danny release to an Ubuntu 12.10 computer, and
pseudo failed to build. Before opening a bug, I just wanted to make sure
it's
That totally worked. Silly me, just realised I forgot to check the quick
start guide to install the required packages.
Thanks, Ross.
Belen
On 12/12/2012 14:15, Burton, Ross ross.bur...@intel.com wrote:
On 12 December 2012 14:09, Barros Pena, Belen
belen.barros.p...@intel.com wrote:
I just
Hi all,
I am new to Yocto.
I am trying to build an environment with arm-gcc integrated since the ZYNQ
board has ARM Cortex A9 ducal core on it.
Let me know if any one has tried something similar or some pointers on how
i can proceed.
--
*Anup Kini
*Systems Engineer
*
Hi Anup,
Atleast two people on the yocto mailing list have successfully
built the toolchain and rootfile system for the ZC702, Philip Balister and
myself, using the latest yocto master.
Here are a few steps:
01. Look up the Yocto Quick Start Guide to setup your Ubuntu 12.10 x86
On Tue, 2012-10-09 at 14:26 -0600, Chris Conlon wrote:
On Sep 6, 2012, at 4:53 PM, Richard Purdie wrote:
This looks like an interesting piece of software and a quick read
through your webpages suggests there may be some interesting
applications of this within OE which I'd love to explore.
Hi Elvis,
I could not find where the arm gcc was included in this build.
I was checking the build process and took the gcc.4.4.6 while building the
core-image-minimal.
Hence i wanted to confirm if the arm-gcc can be integrated and steps to do
it.
On 12 December 2012 16:18, Elvis Dowson
Hi Anup,
On Dec 12, 2012, at 7:32 PM, Anup Kini ak...@synapticon.com wrote:
I could not find where the arm gcc was included in this build.
I was checking the build process and took the gcc.4.4.6 while building the
core-image-minimal.
Hence i wanted to confirm if the arm-gcc can be
Hi Jon,
Thanks for the clarification on which manual release you were looking
at. I am the technical writer for the project so hopefully someone from
the team will address the technical aspect of you issue. If there is a
way to disable these within a specific recipe then I can get that
On Wednesday 12 December 2012 11:32:39 Jon Szymaniak wrote:
Just to make sure I'm understanding this... so when I place PREMIRRORS =
in a recipe, I see that it doesn't affect the associated variables in other
recipes.
Is this because I'm inherently setting up PREMIRRORS_${PN}, which is
On 12/11/12 3:20 PM, Rifenbark, Scott M wrote:
I think what I am going to do is document these in general as part of the Terms section
in the YP Development Manual where the term Cross-Development Toolchain is defined.
Would putting such a high-level list in the YP documentation be
On 12/12/12 5:43 AM, Burton, Ross wrote:
On 12 December 2012 11:31, Tim Coote tim+yoctoproject@coote.org wrote:
Am I right in thinking that yum isn't in the standard recipes?
Yum, no. Zypper is in oe-core and is used when you construct a RPM-based image.
(note that Zypper is being
On 12/12/12 6:07 AM, Tim Coote wrote:
ok. Thanks.
just spotted the split between rpm / rpm5 and yum. I suppose that the knock on
is managing multiple repos for different update managers.
don't suppose you know if there are material differences from a
packaging/dependency point of view
If this is something we would not encourage in a published recipe, then it is
questionable as to documenting this simple way. Or, perhaps, document it with
the caveat that it is not something you would normally do?
Scott
-Original Message-
From: Paul Eggleton
A good read, thanks!
Dave
On 12/12/12 12:44 AM, Darren Hart dvh...@linux.intel.com wrote:
In response to much feedback on the linux-yocto recipes and the associated
kernel tools, we have made a number of improvements in an attempt to
make them
more accessible. In particular, the tools now allow
a bit more pedantry, but is there a more complete example of the use
of BBMASK than the trivial example in the ref and dev manuals?
the ref manual provides this example by way of explanation:
BBMASK = .*/meta-ti/recipes-misc/
well, ok, except you occasinally find slight variations like:
Please feel free (anyone) to provide some useful examples and a bit of
explanation for each and I will be happy to get them in the manual(s).
Scott
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Robert P. J. Day
Sent:
On Tue, 11 Dec 2012, Rudolf Streif wrote:
Hi Robert,
a basic question -- is it supported that users be able to download and
run yocto's pre-built QEMU images without having to download an entire
build system, and set up bitbake, etc? theoretically, of course, it
Thanks for the feedback Mark. I will go ahead with it.
Scott
-Original Message-
From: Mark Hatle [mailto:mark.ha...@windriver.com]
Sent: Wednesday, December 12, 2012 9:08 AM
To: Rifenbark, Scott M
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Difference of toolchain recipes
On
I can likely help with this, Scott.
On Wed, Dec 12, 2012 at 2:33 PM, Rifenbark, Scott M
scott.m.rifenb...@intel.com wrote:
Thanks for the feedback Mark. I will go ahead with it.
Scott
-Original Message-
From: Mark Hatle [mailto:mark.ha...@windriver.com]
Sent: Wednesday,
On Wed, 12 Dec 2012, Rifenbark, Scott M wrote:
Please feel free (anyone) to provide some useful examples and a bit
of explanation for each and I will be happy to get them in the
manual(s).
i forgot to mention this snippet i ran across in the meta-angstrom
layer's contrib/local.conf:
When trying to build a machine I had not built in a while, I got the
following error:
$ bitbake core-image-minimal
Pseudo is not present but is required, building this first before the
main build
NOTE: Your conf/bblayers.conf has been automatically updated. Please
re-run bitbake
.
mkdir: cannot
On Wed, Dec 12, 2012 at 11:42:41AM -0800, Tim Bird wrote:
On 12/12/2012 11:27 AM, Robert P. J. Day wrote:
a bit more pedantry, but is there a more complete example of the use
of BBMASK than the trivial example in the ref and dev manuals?
the ref manual provides this example by way
On 12/11/2012 01:05 PM, Trevor Woerner wrote:
Hi,
Are per-image ROOTFS sizes (i.e. IMAGE_ROOTFS_SIZE_image) still
supported? From this:
http://patches.openembedded.org/patch/4671/
it would appear not. However
poky-extras/meta-kernel-dev/conf/machine/example.conf contains
it's a pedantry-laden day today so i'm going to continue to whine
about aesthetics. what about a yocto style guide for coding style
recommendations? for example, consider the variations:
poky/meta/recipes-support/libcroco/libcroco_0.6.3.bb:SRC_URI_append =
file://croco.patch;apply=yes \
Hi Darren,
On Wed, Dec 12, 2012 at 2:59 PM, Darren Hart dvh...@linux.intel.com wrote:
On 12/11/2012 01:05 PM, Trevor Woerner wrote:
Are per-image ROOTFS sizes (i.e. IMAGE_ROOTFS_SIZE_image) still
supported?
Interesting, I haven't tried myself. Have you tried and run into an issue?
Yes. I
On 12/12/2012 11:53 AM, Robert P. J. Day wrote:
On Wed, 12 Dec 2012, Tim Bird wrote:
On 12/12/2012 11:27 AM, Robert P. J. Day wrote:
a bit more pedantry, but is there a more complete example of the use
of BBMASK than the trivial example in the ref and dev manuals?
the ref manual
On 12/12/2012 12:14 PM, Trevor Woerner wrote:
Hi Darren,
On Wed, Dec 12, 2012 at 2:59 PM, Darren Hart dvh...@linux.intel.com wrote:
On 12/11/2012 01:05 PM, Trevor Woerner wrote:
Are per-image ROOTFS sizes (i.e. IMAGE_ROOTFS_SIZE_image) still
supported?
Interesting, I haven't tried
On 12/12/2012 11:53 AM, Robert P. J. Day wrote:
On Wed, 12 Dec 2012, Tim Bird wrote:
I don't know if the .= with leading bar is the optimal
way to append on to BBMASK, but it seems fairly straightforward
to me. I sometimes use the leading .* and sometimes not.
it doesn't seem like the
Thanks Bill,
I will put together my draft for the section and send it your way. You can
give it a good technical review.
Scott
From: Bill Traynor [mailto:w...@alphatroop.com]
Sent: Wednesday, December 12, 2012 11:37 AM
To: Rifenbark, Scott M
Cc: Mark Hatle; yocto@yoctoproject.org
Subject: Re:
On Wed, 12 Dec 2012, Trevor Woerner wrote:
Hi Darren,
On Wed, Dec 12, 2012 at 2:59 PM, Darren Hart dvh...@linux.intel.com wrote:
On 12/11/2012 01:05 PM, Trevor Woerner wrote:
Are per-image ROOTFS sizes (i.e. IMAGE_ROOTFS_SIZE_image) still
supported?
Interesting, I haven't tried myself.
On Wed, Dec 12, 2012 at 3:19 PM, Darren Hart dvh...@linux.intel.com wrote:
What is the reason you would like to do this just for vmdk? Is it to
avoid increasing the size of all the images when it is only vmdk you
care about? That would makes sense.
Yes, that's it exactly. I have an existing
On Wed, Dec 12, 2012 at 3:46 PM, Robert P. J. Day rpj...@crashcourse.ca wrote:
so what happens if you try to set the appropriate variables above?
When Yocto creates a VMDK, it creates 2 partitions:
- an MSDOS partition for the syslinux stuff
- the ext{3,4} partition of your root image
When it
On Wed, 12 Dec 2012, Trevor Woerner wrote:
On Wed, Dec 12, 2012 at 3:46 PM, Robert P. J. Day rpj...@crashcourse.ca
wrote:
so what happens if you try to set the appropriate variables above?
When Yocto creates a VMDK, it creates 2 partitions:
- an MSDOS partition for the syslinux stuff
-
Hi Robert,
(we met at OLS last summer, I came and chatted with you briefly after
your presentation)
On Wed, Dec 12, 2012 at 5:03 PM, Robert P. J. Day rpj...@crashcourse.ca wrote:
now i'm interested, so ... what are your config steps? i wouldn't
mind trying to reproduce this on my system.
On Wed, 12 Dec 2012, Trevor Woerner wrote:
Hi Robert,
(we met at OLS last summer, I came and chatted with you briefly after
your presentation)
On Wed, Dec 12, 2012 at 5:03 PM, Robert P. J. Day rpj...@crashcourse.ca
wrote:
now i'm interested, so ... what are your config steps? i
On 12/12/2012 03:16 PM, Robert P. J. Day wrote:
On Wed, 12 Dec 2012, Trevor Woerner wrote:
On Wed, Dec 12, 2012 at 3:46 PM, Robert P. J. Day rpj...@crashcourse.ca wrote:
so what happens if you try to set the appropriate variables above?
When Yocto creates a VMDK, it creates 2 partitions:
-
51 matches
Mail list logo
