From: Stafford W. <sta...@gm...> - 2008-05-07 01:46:02
|
There are a large amount of messages with no replies related to this problem, or similar. Either these people worked it out themselves, or are still lost. For archiving purposes, here are my findings and eventual fix. I am a sucker for learning the hard way and have trolled this board and openembedded/bitbake docs for something ridiculous, like 5 hours, until I eventually found my sad mistake. The reason for my unexpected results was one bracer, {, missing from my .bb file. Hopefully the following information will help someone; OpenEmbedded (OE) Build System (bitbake) Notes for Newbs like me: 1) The bitbake recipe here: http://www.gumstix.net/Software/view/Build-system-overview/Hello-world-tutor ial/111.html does compile. If it does not, it is likely you have copied it incorrectly. 2) Running bitbake "name" or bitbake "name-version" will only (attempt) to build your package once. Changing the revision number inside the .bb file, will not build it again UNLESS you run bitbake -b "name-_version. 3) When bitbake finally echoes NOTE: package "name-version": completed, this does not mean your *.ipk has definitely been built. Errors in the .bb may have only built the -dev and -dbg versions which will not install your program on a gumstix. 4) These errors. ERROR: QA issue: libmudflap.la failed sanity test (reference to workdir or installed) ERROR: QA issue: libsupc++.la failed sanity test (reference to workdir or installed) ERROR: QA issue: libmudflapth.la failed sanity test (reference to workdir or installed) ERROR: QA issue: libstdc++.la failed sanity test (reference to workdir or installed) . can be disregarded. They are not affecting your build. 5) The only difference between my successful and unsuccessful bitbake build logs is the line(s) under. NOTE: the following files were installed but not shipped in any package: .which when successful, will list the expected output of the .ipk once installed on the 'stix. Finally, for the record, mine was bung because of this line: install -d ${D}$bindir}/ Bracer missing before the b :-) Cheers, Stafford. _____ From: gum...@li... [mailto:gum...@li...] On Behalf Of Stafford Williams Sent: Tuesday, 6 May 2008 12:55 p.m. To: 'General mailing list for gumstix users.' Subject: [Gumstix-users] helloworld-dev and helloworld-dbg on OE 316.Version rollback required? Hi all, Is the build system broken on OE 316? Compiling the helloworld example creates ; helloworld-dbg_1.0.0-r1_armv5te.ipk helloworld-dev_1.0.0-r1_armv5te.ipk None of which on installation on the gumstix actually installs the hello program. This has been queried before, however the solution of using bitbake -b still only creates these two files, and not the expected helloworld_1.0.0-r1_armv5te.ipk. Considering other issues I have been having lately with building on OE 316, is a possible solution to roll back to an earlier version? Is it possible/difficult to do this? Cheers, Stafford. |