[oe] What to do about the poor bitbake Quality Control?

[J. L.]

I agree with you AJ, its become a serious pain to just get a built
image. I myself have only built once completely and have yet to again
since figuring out the changes I needed to make to that image. I would
like to help myself but someone like me whose not very competent in
this area finds the documentation a tad lacking to properly learn the
ways to help. I still have yet to figure out how to even get my own
program from the net to build with OE as just following the hello
world does not seem to be enough for me to grasp how to do it with an
actual problem. Which runs me into my next issue I can not properly
modify the way some programs build to get the features I want.

I have also noticed on the gumstix boards while most of the time it
seems its the same errors people get, every once in awhile you see
some people with one issue and others with another.

I am sure this wont be of much use as a post but figured I would chime
in from an inexperienced beginner trying to get a footing in here and
to actually be able to use things properly.



On Sat, Aug 14, 2010 at 8:46 AM, AJ ONeal <coolaj86 at gmail.com> wrote:
> This is about the 4th time that I've `rm -rf`-d everything and started from
> scratch and never yet got a working `bitbake omap3-console-image`
>
> Every time I `git pull` it's a different set of problems. It's never the
> same package twice, but they never all compile for the basic console image
> anywhere from 4 to 20 hours in.
>
> Fortunately, I do have a machine that did build omap3-console-image a few
> weeks ago at work. But I've never been able to get it on my machine at home
> (same os) to start playing around with.
>
> What needs to happen in order for things to git checked that they work with
> at least a few common meta-tasks before being pushed out?
> And is there anything I can do to help? (Donate some machine time to run
> tests, for example)
>
>
> Obviously, we all have our day jobs and whatnot, but this is becoming really
> frustrating for me and I'd like to see things improve.
>
> AJ ONeal
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>