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

[J. L.]

Right on thanks that does seem to answer a couple questions I have
come across so far especially the devshell. I will give making my
recipe another shot again today and see if I can get further with it
or even crazier get it to build correctly. Thanks again hopefully we
will see some other input to your original statement.



On Sat, Aug 14, 2010 at 10:06 AM, AJ ONeal <coolaj86 at gmail.com> wrote:
> I've been compiling some common general issues
> http://fastr.github.com/articles/Troubleshooting-bitbake.html
>
> Here's some quick-n-dirty instructions akin to using devshell:
>
>
>   1. cd ${OVEROTOP}/tmp/work/${ARCH}/${PACKAGE}_${VER}_r${REV}/${BUILD}
>      - ${ARCH} is probably armv7a-angstrom-linux-gnueabi
>      - ${BUILD} is a directory which is not NOT src or temp such as the
>      package name or git or trunk or svn
>      - ${VER} and ${REV} - duh.
>   2. `cp ../temp/run.do_compile.${OLD_PID}
>      - ${OLD_PID} is a number like 3597 or 4352
>      - do_compile could be any task - do_install, etc
>   3. vim run.do_compile.1234
>      1. comment out do_compile() (or whatever)
>      2. add bash --norc
>   4. ./run.do_compile.1234 will put you in an environment with all
>   variables set
>   5. make (or whatever) to try to build, debug issues
>   6. exit (when done to go back to shell without run.do_compile settings)
>
> This is based on the tip on openembedded wiki, but it took me a while to
> understand what theirs meant so I cleaned it up in a fashion which is
> hopefully crystal clear.
>
> AJ ONeal
>
> On Sat, Aug 14, 2010 at 10:16 AM, J. L. <vwyodapink at gmail.com> wrote:
>
>> 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
>> >
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel at lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>