Thank you.
These are interesting slides. As I was not able to attend the sessions in
Barcelona, I decided to "follow along at home" with the information posted
in this thread.
The slides pdf (ypdd_2012_barcelona_intro_hands_on_lab.pdf) describes the
first line of the contents of the meta-ypdd/rec
Okay, thanks for the comments.
I also want to highlight the change from "task-core-boot" to
"packagegroup-core-boot" for anyone wanting to try these steps on the
latest (although I'm not sure which string denzil prefers).
___
yocto mailing list
yocto@yoc
There have been many emails and lots of documentation describing how
to add a package to a build, and that's all great.
Today I was playing around with an image I had already built and
decided I wanted to add a new package to the mix: trace-cmd. I added "
trace-cmd" (with the required leading spac
e " alone
doesn't work.
On Fri, Nov 23, 2012 at 1:27 PM, Trevor Woerner wrote:
> There have been many emails and lots of documentation describing how
> to add a package to a build, and that's all great.
>
> Today I was playing around with an image I had already built
Thank you so much for having a crack at this. Your results have allowed me
to dig a bit deeper into this issue.
I'm still trying to narrow down the exact issue but here's what I have so
far.
I'm working with the git repository, but I've been playing around with this
for about a week, so I'm not 1
On Mon, Nov 26, 2012 at 6:52 PM, Trevor Woerner wrote:
> I haven't yet figured out if the "PREFERRED_PROVIDER_virtual/kernel =
> "linux-yocto-rt"" line might be the culprit.
No, it is not related, this problem doesn't need any fancy
configuration features. Th
On Tue, Nov 27, 2012 at 5:39 AM, Eric Bénard wrote:
> I confirm the problem when following this procedure step by step.
Thank you, Eric, for the confirmation.
Just to clarify for anyone following along: the problem isn't with
bash or trace-cmd themselves. If I perform the same steps but use
'ba
On Tue, Nov 27, 2012 at 12:24 PM, Robert P. J. Day
wrote:
> and ran the fetchall again. this time, no strace source was fetched,
> so it looks like an issue with simple fetching.
Thank you for your testing and observations.
But I'd like to point out that in my tests, all the relevant files
hav
This issue has been entered into the yocto bugzilla as:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=3503
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2934
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Allow vmdk images to be run through the 'runqemu' facility.
---
scripts/runqemu | 39 +--
scripts/runqemu-internal | 20
2 files changed, 45 insertions(+), 14 deletions(-)
diff --git a/scripts/runqemu b/scripts/runqemu
index fb7ac5
Hi,
Are per-image ROOTFS sizes (i.e. IMAGE_ROOTFS_SIZE_) 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
IMAGE_ROOTFS_SIZE_ext3 (which would make it appear as though they
are).
Be
Allow vmdk images to be run through the 'runqemu' facility.
Signed-off-by: Trevor Woerner
---
scripts/runqemu | 39 +--
scripts/runqemu-internal | 20
2 files changed, 45 insertions(+), 14 deletions(-)
diff --git
Hi Scott,
Thank you for reviewing my patch.
On Wed, Dec 12, 2012 at 12:55 AM, Scott Garman 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 last
contributed to a pr
Hi Darren,
On Wed, Dec 12, 2012 at 2:59 PM, Darren Hart wrote:
> On 12/11/2012 01:05 PM, Trevor Woerner wrote:
>> Are per-image ROOTFS sizes (i.e. IMAGE_ROOTFS_SIZE_) still
>> supported?
> Interesting, I haven't tried myself. Have you tried and run into an issue?
Ye
On Wed, Dec 12, 2012 at 3:19 PM, Darren Hart 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 build system in place
On Wed, Dec 12, 2012 at 3:46 PM, Robert P. J. Day 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 then shmushes these tw
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 wrote:
> now i'm interested, so ... what are your config steps? i wouldn't
> mind trying to reproduce this on my system.
My doodle layer can
Thank you, I enjoyed reading your document. I especially liked the top
part which talked about creating your own tasks (which 'turned the
light on' for how OE/Yocto use bitbake). I also wasn't aware of the
vim helpers which come as part of bitbake.
___
yo
I'm not sure if there's something about my system that is different
than what you expect, but I had to delete my 'tmp' folder before
invoking './bin/bitbake firstrecipe -vDD' after inheriting the
"autotool" versions in order to get the new, overridden tasks to run
(since there's no 'clean' tasks).
Is there a chance this can get included?
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
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
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
On Tue, Jan 15, 2013 at 2:16 PM, Zhang, Jessica wrote:
> According to bug 1614, the kernel dev packages should be
> included in sdk images. Please generate your toolchain using
> "bitbake core-image-sato-sdk -c populate_sdk" which will
> make the toolchain target sysroot matching your image's
> sy
On Thu, Jan 24, 2013 at 8:48 AM, Eddy Lai GMail wrote:
> how can I "extend" the
> target system to use the rest USB disk space? ( it's FAT file system)
> or how to modify configuration to force build the .hddimg create ~"8GB"
By default a certain amount of overhead is applied to the final im
On Tue, Jan 29, 2013 at 3:58 PM, Rifenbark, Scott M
wrote:
> Can anyone out there offer more information on this variable? Wondering
> whether this should be documented in the glossary.
By default bitbake will throw an error if there exists a *.bbappend
recipe for which there is no correspondin
Hi Frans,
On Fri, Feb 8, 2013 at 9:24 AM, Frans Meulenbroeks
wrote:
> There is also a default base_do_install() that is empty.
> Wouldn't it be more logical if the base_do_install would read:
>
> Currently people using only base, need to add a do_install to their recipe
> but no do_compile (which
Hi everyone,
I've looked at Tim's cheat sheet and Robert's FAQ but I can't seem to
figure out if there is a simple way to get bitbake to list the
packages that will be included in the build of a given image.
$ bitbake core-image-minimal
Am I overlooking something obvious?
Best regards,
Tr
Hi Pierre,
On Wed, Feb 13, 2013 at 5:09 AM, Pierre Ficheux
wrote:
> $ bitbake -g core-image-minimal
>
> result in pn-buildlist.
Thank you, that works great on master.
This must be new-ish, the bitbake from my gumstix build (HEAD at
846b7c, or roughly Oct 11, 2012) doesn't produce a pn-buildlis
On Thu, Feb 14, 2013 at 11:02 AM, Andre Bella wrote:
> is there a menuconfig on yocto where you can select the package you want to
> add before you build the image?
I would suggest giving hob a try:
$ source poky/oe-init-build-env
$ bitbake -u hob
Bitbake will compile need to download and com
On Fri, Feb 15, 2013 at 9:29 PM, Tom Zanussi wrote:
> I'm happy to announce that an updated version of the Yocto 'Hands-on
> Kernel Lab' has been released and is available here:
This is awesome, and much appreciated (especially by those of us who
can't make it out to these events).
Following the
On Sun, Feb 17, 2013 at 6:15 PM, Tom Zanussi wrote:
> I guess a bug
> should be opened for it.
I have created https://bugzilla.yoctoproject.org/show_bug.cgi?id=3898
in the hope it doesn't get dropped again.
___
yocto mailing list
yocto@yoctoproject.org
...sorry, I meant to CC the list too
-- Forwarded message --
From: Trevor Woerner
Date: Sun, Feb 17, 2013 at 9:15 PM
Subject: Re: [yocto] Updated Yocto Hands-on Kernel Lab available
To: Tom Zanussi
Hi Tom,
I can see how the kernel *.bb files get pulled in due to the
I can't figure out what I'm doing wrong, but I can't get lab3 to work.
Following the instructions in the pdf I first tried doing lab3
incrementally (build/test, build/test, build/test) and it didn't work.
Then I tried deleting (tmp, sstate, etc), trying again, and it still
didn't work.
Build Conf
On Tue, Feb 19, 2013 at 12:31 AM, Tom Zanussi wrote:
> So when you say it doesn't work, you mean the module autoload didn't
> work, but everything else did?
Yes, exactly.
> Did you do the 'bump the PR' step after
> you uncommmented the module autoload statement?
Yes, I even bumped it twice :-)
Following up on a hunch, after reading Pierre Ficheux's email from
earlier today, I realized that by default I always switch my build's
PACKAGE_CLASSES to ipk simply because this packaging takes the least
amount of build time. Sure enough, when working on lab3 I had switched
to ipk and it didn't wo
On Thu, Feb 28, 2013 at 9:43 AM, Tim O'Callaghan wrote:
> I've been digging through the documentation, and dipping into the recipes,
> but have not been able to come up with a definitive approach to managing what
> I call different build flavors. I
I believe the functionality you're looking for
Given that Greg KH has publicly stated linux-3.8 is not a long term
stable kernel, is it worth the effort to support it in Yocto?
http://www.kroah.com/log/linux/3.8-is_not_longterm_stable.html
___
yocto mailing list
yocto@yoctoproject.org
https://lists.y
Hi Paul,
I saw your email on the gumstix list but forgot to "star" it, and
therefore didn't get back to it as I would have liked, sorry about
that.
I too play around with a gumstix from time to time, as well as other
boards. In my (still learning) opinion, the gumstix stable build is
based on rea
I've been really blown away by the breadth of the Yocto Project; not
only will it help you create a distribution for a device but it can
also help you create things like a -dev image or a self-extracting
SDK.
Sometimes I like to work with a "sub-Linux" device, something that is
too small to run Li
Do you have git installed on your development machine?
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Tue, Mar 5, 2013 at 9:20 PM, Paul D. DeRocco wrote:
> So I guess the questions are these: Are ext2, ext3 and ext4 all equally
> likely to need to do an "fsck" after a disorderly shutdown? Do they
> typically take different amounts of time to do an "fsck"? Or is the
> journaling of ext3 and ext4
I don't see any reason this conversation can't be on the public
mailing list. That way others can help and/or learn from the
discussion. I hope you don't mind be bringing it back to the mailing
list.
On Wed, Mar 6, 2013 at 11:32 AM, varun bhatnagar wrote:
> YesI have...I tried running bitbake
Hi Khem,
Thanks for adding your thoughts; you were exactly who I was hoping
would have input to my question :-)
On Fri, Mar 8, 2013 at 3:59 AM, Khem Raj wrote:
>> Sometimes I like to work with a "sub-Linux" device, something that is
>> too small to run Linux, or a device on which, for whatever r
On Fri, Mar 8, 2013 at 2:07 AM, Khem Raj wrote:
> We have moved away
> from snapshots for gcc since git repo for gcc is in terabytes and
It sure would be nice if git had a feature whereby one could grab just
a specific snapshot without any history, or meta-information etc...
just the code of one
On Fri, Mar 8, 2013 at 7:08 AM, Hans Beckérus wrote:
> I
> tried going through the module.bbclass but must admit I lost it
> somewhere in the middle ;) Any guidance would be appreciated.
Have you had a chance to look at the Yocto hands-on kernel lab?
https://lists.yoctoproject.org/pipermail/yocto
On Fri, Mar 8, 2013 at 12:15 PM, Chris Tapp wrote:
> In the 7 hours it's taken this to get to the list (no ideas where it got
> stuck!)
I'm seeing emails arrive hours after their date-stamps too. In fact
this email just arrived in my inbox, but according to the date stamp,
you sent it 5 hours ag
On Mon, Mar 11, 2013 at 12:15 PM, David Mulder wrote:
> but how can I make my run my code on that core?
You can call sched_setaffinity() before fork()ing your task, or use
taskset on the cmdline.
(sorry if this has already been answered but I'm not seeing any
responses due to mailing list delays
A new version of openSuSE has been released. What's the criteria for
determining that a given version of a distribution has been validated
for Yocto? What is required in order to add it to the list of valid
distirbutions?
___
yocto mailing list
yocto@yoct
I'm not sure if this is specific to my host, but:
Build Configuration:
BB_VERSION= "1.17.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "openSUSE-project-12.3"
TARGET_SYS= "i586-poky-linux"
MACHINE = "qemux86"
DISTRO= "poky"
DISTRO_VERSION= "1.3
Yes, thanks everyone. Pulling the latest fixes the problem.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Sun, Mar 17, 2013 at 7:17 PM, Martin Jansa wrote:
> Please use better Subject next time, I was wondering what could be
> broken by my patch to icecc and your question is quite unrelated to that
> commit.
>
> Something like "neard failing to build with latest poky" would be
> better.
...which i
I have been going through the archives from this list looking for
information to not only improve my build times but to make these
builds safer (there are hints dropped here and there that these large
builds are bad on disks which has me worried seeing that I use the
same disk+partition for both my
The new autobuilder looks great! One thing that's nice is how easy it
is to look at the build and figure out from what commit the build is
based.
Clicking around in some of those builds, though, I can't seem to
figure out what the various configurations are. For example:
meta-fsl-arm has a number
On Thu, Mar 21, 2013 at 10:05 AM, Eric Bénard wrote:
> in the build log
> http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm/builds/18/steps/Building%20Images/logs/stdio
> you can see it builds for imx53qsb :
> MACHINE = "imx53qsb"
Thank you, now I see how to use those en
I have looked at the output from a couple builds (nightly-fsl-arm,
nightly-fsl-ppc, nightly-mips) and had a couple questions.
Running "poky/oe-init-build-env" will produce a
"build/conf/local.conf", but the nightly builder prefers to puts its
configurations into "build/conf/auto.conf". Obviously t
Thanks for all those answers.
On Mon, Mar 25, 2013 at 5:45 PM, Flanagan, Elizabeth
wrote:
> On Thu, Mar 21, 2013 at 8:31 AM, Trevor Woerner wrote:
>> Not all builds, but these three seem to follow similar steps:
>> 1. prepare
>> 2. configure+build core-image-sato core-i
[the following is meant to be humourous, please take it as such]
What I'm hoping to see in the next release is a better release name.
Male first names was the best suggestion? I recommend the next release
be named "Dani", a female version of "Danny", just to keep things
equal.
On Tue, Mar 26, 2013 at 2:37 PM, Burton, Ross wrote:
> Danni would be a terrible name
Of course it would be a terrible name, that's why I suggested it; I
figured it'd fit in with the others :-D
(don't forget my earlier statement about this being done in jest)
I'm kinda surprised Robert Day hasn't jumped in, I know he's got all
this straightened out :-)
On Wed, Mar 27, 2013 at 10:10 PM, ChenQi wrote:
> In your case, you could add the following line to local.conf.
> IMAGE_INSTALL_append += "samba"
I thought this was not the generally accepted notation.
If I expected that my audience would be mostly made up of people who
have been using *nix for years and are comfortable with the cmdline,
then I would show how I use Yocto/OE via the cmdline. If I expected
that most of them would be more accustomed to Eclipse/GUI-based
development, then I would try
On Thu, Mar 28, 2013 at 2:00 PM, Barros Pena, Belen
wrote:
> When we tried to define it properly, we realised that templates could be a
> few different things, and that we should find out which of them is the
> most useful. This email is my attempt to gather your thoughts on this
> templates busin
On Thu, Mar 28, 2013 at 5:35 PM, Paul D. DeRocco wrote:
> Somehow, it grates on me that underscore is used almost like an
> operator in BitBake.
You're not alone!
Because the people who did this are reading this list ;-) I'll be
polite, it is clever, but even after a year of trying to get
comfor
On Tue, Apr 2, 2013 at 6:21 AM, Barros Pena, Belen
wrote:
> But it seems to me there is
> more interesting stuff buried somewhere in your answer, so I hope it's ok
> if I dig a little deeper.
:-D
> I think I might have asked the wrong question. Let's forget about the word
> "template" for a mome
On Thu, Apr 4, 2013 at 6:42 PM, Sean Liming wrote:
> Why post-build instead of pre-build?
The idea is that you have one build, and you are manufacturing 5000 devices.
So you take this one build and load it on each of your identical
devices which you then sell to your customers. But if each devic
On Mon, Apr 8, 2013 at 5:49 PM, Sean Liming wrote:
> Is this post-build utility an active
> project for the Yocto Project or is it just getting started?
It's only in the discussion phase right now, hence the "RFC" in the
subject line.
___
yocto mailing
Hi Robert,
Since you're working your way through the labs, I was wondering if
you'd be interested in testing something out for me? When I went
through these labs I had set my PACKAGE_CLASSES to package_ipk instead
of the default package_rpm. While doing so I had discovered a bug
which I reported,
On Tue, Apr 9, 2013 at 5:29 PM, Robert P. J. Day wrote:
> does this mean PACKAGE_CLASSES should be *exclusively* ipk, or that
> ipk simply be in there?
Yes, that's how I had been testing it (exclusively package_ipk).
___
yocto mailing list
yocto@yocto
On Tue, Apr 9, 2013 at 5:46 PM, Robert P. J. Day wrote:
> ok, so what am i looking for?
I couldn't get lab3 to work fully unless I switched from package_ipk
to package_rpm. The module would get built and included in the image,
but it wasn't being loaded automatically during boot. At the time I
On Tue, Apr 9, 2013 at 6:11 PM, Tom Zanussi wrote:
> I believe I tried and couldn't reproduce it. But if someone does
> reproduce it, please file a bug detailing the *exact* steps needed to
> reproduce.
Thanks for the update, I wasn't 100% sure if you had found the time to
give it a try or not.
On Tue, Apr 9, 2013 at 6:29 PM, Robert P. J. Day wrote:
> so, did you say you were going to try to reproduce this? i don't
> want to spend time poking around this if it turns out even *you* can't
> make it happen again. :-)
Understood :-)
Yes, I'll try reproducing this and post my results.
___
On Tue, Apr 9, 2013 at 6:34 PM, Trevor Woerner wrote:
> Yes, I'll try reproducing this and post my results.
Now I've hit a snag. Since performing these tests, I have upgraded my
host system from openSUSE 12.2 to 12.3. Building qemu-native from the
HEAD (which uses qemu version 1.
On Wed, Apr 10, 2013 at 12:20 PM, Robert P. J. Day
wrote:
> p.s. i was originally going to suggest the SEAD-3 as the next MIPS
> board until he told me it cost $2K. ouch.
You clearly didn't read the marketing drivel closely enough:
"The MIPS® SEAD™ -3 System engineering and development board is
On Wed, Apr 10, 2013 at 6:48 PM, Flanagan, Elizabeth
wrote:
> Our first release candidate for dylan has been started.
>
> Repo Branch Hash
> pokydylan adb63ca02348af72a30cef2f20de2234b74a7200
I did a little bit of my own ad-hoc testing and wanted to shar
On Wed, Apr 10, 2013 at 10:41 PM, Bruce Ashfield
wrote:
> Fixed. A few hours ago.
[...]
> Known problem. And I've got a fix already tested and on it's way to
> Richard.
Wow, one certainly does get service around here! :-)
___
yocto mailing list
yocto@y
On Sat, Apr 13, 2013 at 5:59 PM, Flanagan, Elizabeth
wrote:
> The fifth milestone for the upcoming Yocto Project 1.4 release is now
> available
If I want to get an idea of what's going to be in the next release,
dylan, which branch do I use: dylan or 1.4_M5?
When I use dylan I'm able to "bitbake
On Mon, Apr 15, 2013 at 7:46 AM, Trevor Woerner wrote:
> Maybe I'm doing something wrong with git?
1.4_M5:860e758b7b7f27fbb47c645770593206c7453c1b
dylan:d80e663e209965073ff40fb775246eabc0159a44
___
yocto mailing list
yocto@yoctoproject.o
If I start with
$ bitbake core-image-minimal
and then do
$ runqemu qemux86
a new window opens and qemu runs as expected (i.e. it pops open a new
window and runs in that and not via vnc).
If I then do
$ bitbake core-image-sato
and try
$ runqemu qemux86
I then get
Could
On Tue, Apr 16, 2013 at 3:02 PM, Edward Vidal wrote:
> Are there any plans to provide a repo of pkgs where systems can be upgraded
> and new pkgs installed like other distro Fedora, CentOS, and rhel? This
> would also require yum or the new software that is replacing yum.
I doubt it. The Yocto P
On Tue, Apr 16, 2013 at 3:49 PM, Edward Vidal wrote:
> With that said how does Angstrom which uses opkg upgrades images that are
> build with Angstrom.
Angstrom is a distribution, so it can make assumptions about how to
build a set of packages that will work on your system.
__
On Wed, Apr 17, 2013 at 11:12 AM, Gary Thomas wrote:
> I also think it would be good to point out the use of := in the
> FILESEXTRAPATHS
> assignment and why it's important.
Knowing that the := operator will put your directories first is only
useful if you also know that the underlying mechanism
On Mon, Apr 15, 2013 at 11:46 PM, Trevor Woerner wrote:
> Could not initialize SDL(No available video device) - exiting
I was able to "solve" my problem by moving my SSTATE_DIR and starting
over. Conversely, clobbering my SSTATE_DIR would have solved the issue
too. That'
On Wed, Apr 17, 2013 at 11:21 PM, Rudolf Streif
wrote:
> If you do not have libsdl1.2-dev (Ubuntu) installed on your dev/host system
> then qemu will be built without video support.
I would have assumed that if something was missing from my host, then
I would not have been able to run the virtual
On Thu, Apr 18, 2013 at 12:50 AM, Rudolf Streif
wrote:
> Removing sstate triggered a rebuilt of qemu-native which also includes
> running the configure task again whose output sets the switch whether or not
> Qemu is built with video support. Apparently the first time you built it it
> could not f
Sorry if I'm asking a really stupid question, but if so, it means I'm
way off the mark :-)
On Thu, Apr 18, 2013 at 6:23 AM, Gary Thomas wrote:
> My point, which was totally unclear to me when using this line, was
> that with ':=' ${THISDIR} evaluates to the directory that contains
> the .bbappend
On Fri, Apr 19, 2013 at 8:37 AM, Robert P. J. Day wrote:
> first, it's not actually *required* that a layer name start with the
> prefix "meta-", is it? pretty sure it's not and, if it isn't, that
> should be made abundantly clear. it's fine to point out that it's a
> well-established convention
On Tue, Apr 9, 2013 at 6:11 PM, Tom Zanussi wrote:
> On Tue, 2013-04-09 at 18:06 -0400, Trevor Woerner wrote:
>> On Tue, Apr 9, 2013 at 5:46 PM, Robert P. J. Day
>> wrote:
>> > ok, so what am i looking for?
>>
>> I couldn't get lab3 to work fully
Another option is to start over again following these instructions:
https://github.com/gumstix/Gumstix-YoctoProject-Repo/blob/master/README.md
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
I'm quite sure there used to be a time when I could send a SIGTSTP to
bitbake
(usually by doing a Ctrl-Z) and it along with its children would suspend.
This
doesn't seem to be the case anymore. Maybe it just so happened that the
subprocesses finished quickly after I gave the Ctrl-Z and no new ones
On Thu, May 2, 2013 at 7:27 AM, Paul Barker wrote:
> What would be useful is a first boot task which resizes the rootfs to
> fill the SD card it's on without prompts. Should be easy to do with a
> postinst script and fdisk.
In my opinion, what would be even better:
- the build system is instruct
On Thu, May 2, 2013 at 11:52 AM, Paul Barker wrote:
> Sounds great though it may take a long time to copy files to an SD
> card (I noticed a similar opinion at
> http://www.raspbian.org/RaspbianInstaller). May be quicker to generate
> an image file with the correct size first then dd that to the c
On Thu, May 2, 2013 at 12:23 PM, Gary Thomas wrote:
> On 2013-05-02 09:52, Paul Barker wrote:
>> Sounds great though it may take a long time to copy files to an SD
>> card (I noticed a similar opinion at
>> http://www.raspbian.org/RaspbianInstaller). May be quicker to generate
>> an image file wit
On Thu, May 2, 2013 at 12:45 PM, Andrei Gherzan wrote:
>>> On 2 May 2013 16:12, Trevor Woerner wrote:
>>>> - a separate tool (which will probably need to be run as root) is used
>>>> to actually format/create the SD device (using, say, sfdisk for
>>>>
On Thu, May 2, 2013 at 11:52 AM, Paul Barker wrote:
> Sounds great though it may take a long time to copy files to an SD
> card (I noticed a similar opinion at
> http://www.raspbian.org/RaspbianInstaller). May be quicker to generate
> an image file with the correct size first then dd that to the c
If every other distribution, over the next year, switched to python-3
as their default, but (instead of updating) future versions of Ubuntu
installed a symlink called python-3 pointing back to python-2, would
that hold back Yocto from adopting python-3-isms too?
It's sad how Ubuntu has so effectiv
On Tue, May 7, 2013 at 8:45 AM, Richard Purdie
wrote:
> 1.3.2
> =
>
> I've merged a lot of queued changes that Ross prepared for 1.3.2 and
> this is now undergoing testing.
I have a patch for Danny to allow qemu-native of qemu-1.2.0 to compile
on openSuSE 12.3 (which, apparently, is also affe
On Tue, May 7, 2013 at 1:13 PM, Burton, Ross wrote:
>> I have a patch for Danny to allow qemu-native of qemu-1.2.0 to compile
>> on openSuSE 12.3 (which, apparently, is also affected by the same (or
>> a similar) DSO linking change that affects fedora). Are the queued
>> changes available somewher
On Wed, May 8, 2013 at 6:35 AM, Burton, Ross wrote:
> On 7 May 2013 18:57, Trevor Woerner wrote:
>> I've looked through the list of patches and don't seem to find
>> anything that will do what my patch needs to do in order to build
>> qemu-1.2.0 on openSuSE 12.3
Hi,
The Yocto Project Development Manual, section 3.2.2 (Source Control
Management (SCM)) states that:
"Git is a distributed system that is easy to
backup (each checkout is a backup in itself)"
I'm not 100% sure a "checkout" would be considered a backup. I think
most people would say that a "clo
After a build, the license data is found in ${TMPDIR}/deploy/licenses not
${TMPDIR}/deploy/images/licenses.
Signed-off-by: Trevor Woerner
---
documentation/dev-manual/dev-manual-newbie.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/documentation/dev-manual/dev-manual
1 - 100 of 517 matches
Mail list logo
