I'd like to clean all of my build output so that I can rebuild with a different toolchain. What is the best way to clean without having to redownload all of my source packages again? I can see that

Attendees: LaurentiuP, Jefro, Richard, Bruce, Michael, Ross, Mark, Sean, Jeff, Tom, Darren, Gilbert, Denys, Jessica, ScottR, Saul, Paul, Jim, Ciby, Alex, Song   Gilbert is from mentor Graphics,

Well, granted that OE/Poky/Yocto is fairly complex. I've followed OE for years (though never successfully built anything with it). I had my first successful build of (Poky?, Yocto?) just

When I attempted to rebuild minimal I hit the same error you did Jim regarding kern-tools-native. This would be expected as Bruce pointed out that problem is alive in denzil. I am going to set the

No, an FAQ should not get you the expertise to create a commercial grade product. Reading the documentation should though. You don't want users to have to study source code.

I am on task 1507 of 1606 of a minimal build (from the example). No issues so far.

Fixing the license check was just a matter of me locking the SRCREV for the tools to a value that works for denzil. I just pushed a denzil branch to poky-extras that built and booted the yocto kernel

That's never been case on this list as far as I recall, folk here are pretty responsive to questions being asked. At the same time, OE/Poky/Yocto is a fairly complex framework and nobody should

that's fine, i'll at least note this shortcut. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario,

yes, but it would also need information on ordering of consultation. from bitbake.conf: require conf/abi_version.conf include conf/site.conf include conf/auto.conf include conf/local.conf include

I have thought about this - it would be great if oe-init-build-env could copy/symlink your customised version from somewhere automatically every time; however the question would be how would it know

So this situation might lend itself to a nice FAQ question.... Something like "How do I isolate site and machine specific information during a build?" And the solution can tell them how to use a

that still requires just a touch of user intervention. no totally automatic way to do that, then? it's at least an improvement over manual copying, thanks. rday --

OK, looking at the settings you've listed, I think these are the kinds of things that site.conf was invented for - stuff that is specific not to the builds you are doing but to the host machine /

and if you want major industry players to take yocto seriously, the last thing you want to do is answer their heartfelt pleas for assistance with, "i'm sorry, that's technically not a yocto

ok, that makes sense. but would it also make sense for bitbake to perhaps support another option that *does* allow personal content to, say, be effectively appended to one's local.conf. for

Thanks for adding the annotation to the WDD chart on how you compute it. :-)

Kooen's cheeky point is worth keeping in mind though; the Yocto naming semantics is not very helpful ;-) Specifically most of the questions being asked on the Yocto list are about Poky, not Yocto,

I guess it depends on what you mean by "personal content". Certain settings are really part of distro policy and if you're finding that you're setting them all the time for all of the builds that

I am going to run through the B.1 example verbatim from the "current" version of the manual and see what happens. Scott