Re: [Gumstix-users] oe built omap3-console-image is smaller than the gumstix prebuilt image

[Bodey B. <bod...@gm...>]

Yeah, I just stumbled accross that recipe. I figured it might be
something like that. It's also looking like I might of just screwed up
dropping or adding a '.bin' and that was my boot issue. All fixed now.
I am curious  though, I'd assume the stuff form /usr/lib/gio/ was to
do with the general IO pins and I'll be doing stuff with them soon, so
what is it actually for?

Bodey

> ------------------------------
>
> Message: 2
> Date: Sun, 11 Apr 2010 06:32:39 -0700
> From: Steve Sakoman <sa...@gm...>
> Subject: Re: [Gumstix-users] oe built omap3-console-image is smaller
>        than    the gumstix prebuilt image
> To: "General mailing list for gumstix users."
>        <gum...@li...>
> Message-ID:
>        <n2s...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Sun, Apr 11, 2010 at 4:28 AM, Bodey Baker <bod...@gm...> wrote:
>> I've been following the open embedded tutorial found here to make your
>> build environment:
>>
>> http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Setting-up-a-build-environment/111.html
>>
>> After I run bitbake omap3-console-image the resultant image in
>> ~/overo-oe/tmp/deploy/glibc/images/overo is smaller than the one's at:
>> http://www.sakoman.com/feeds/omap3/glibc/images/overo/
>>
>> Running with (presumably) up to date org.openembedded.dev directories
>> on these dates I get:
>> ?- 20100409 the binary is 27M
>> ?- 20100411 the binary is 31M
>
> The pre-built images include librabry support for the SGX 3D
> accelerator.  If you uncomment the following line in the
> omap3-console-image you should get the same size image:
>
> #  libgles-omap3 \
>
> If you don't need libgles it is fine to leave it commented out.
>
> Steve
>
>
>> Looking at the prebuilt omap3-console-image*.tar.tz2 images, over that
>> period they are all larger than 31M.
>>
>> I've done a pull of open embedded, reran the bitbake comand, come back
>> and checked there were no new files, downloaded the relevant prebuild
>> binary and then compared them. The method I used to compare them is
>> from a script with the relevant parts below:
>>
>> one=${1}.cmp.txt
>> two=${2}.cmp.txt
>> tar tvfj $1 ?| awk '{printf "%10s %s\n",$3,$6}' | sort -k 2 > ${one}
>> tar tvfj $2 ?| awk '{printf "%10s %s\n",$3,$6}' | sort -k 2 > ${two}
>> kdiff3 ${one} ${two}
>>
>> Obviously the results of this showed some minor file size changes, but
>> ignoring that, what I found it that the binary I've build is missing
>> these files (I've put stars and a some other jaz in here to avoid
>> repetition):
>>
>> ./etc/init.d/pvr-init
>> ./etc/powervr.ini
>> ./etc/rc?.d/K[3,4]0pvr-init
>> ./lib/modules/2.6.32/kernel/drivers/gpu/*
>> ./usr/bin/cputype
>> ./usr/bin/ES[2,3].0/*
>> ./usr/bin/pvrsrvinit
>> ./usr/lib/ES[2,3].0/*
>> ./usr/libexec/gam_server
>> ./usr/lib/gio/*
>> ./usr/lib/libEGL.so*
>> ./usr/lib/libfam.so.0*
>> ./usr/lib/libgamin-1.so.0*
>> ./usr/lib/libGLES*
>> ./usr/lib/libglslcompiler.so*
>> ./usr/lib/libICE.so.6*
>> ./usr/lib/libIMGegl.so*
>> ./usr/lib/libOpenVG[U].so*
>> ./usr/lib/libpvr2d.so*
>> ./usr/lib/libpvrPVR2D_*
>> ./usr/lib/libPVRScopeServices.so
>> ./usr/lib/libSM.so.6*
>> ./usr/lib/libsrv_um.so*
>> ./usr/lib/libstdc++.so.6*
>> ./usr/lib/libXt.so.6*
>> ./usr/lib/opkg/info/gamin.*
>> ./usr/lib/opkg/info/libgles-omap3.*
>> ./usr/lib/opkg/info/libice6.*
>> ./usr/lib/opkg/info/libsm6.*
>> ./usr/lib/opkg/info/libstdc++6.*
>> ./usr/lib/opkg/info/libxt6.*
>> ./usr/lib/opkg/info/omap3-sgx-modules.*
>>
>> I'm guessing this results from the above tutorial not setting up a
>> repository from org.gumstix.dev. Why does that tutorial not do that?
>> The first smaller binary seemed to load from the microSD but then
>> seemed to fail the flash to NAND, maybe because of different mounting
>> during boot up. I'm just in the process of testing the newer image,
>> but regardless of its success, I would like to know why those files
>> are missing.