[Angstrom-devel] Smallest recipe to get OpenGL working?
alexander.stohr at gmx.de
Tue Dec 14 21:02:22 CET 2010
Am 2010-12-13 22:22, schrieb Darren:
> I'm new to open embedded and Angstrom. I recently purchased an Overo Fire and
> have been struggling for about a week trying to get an Angstrom image with
> OpenGL to work. Still not there, but hopefully soon.
my simplest response from a former life would be:
get the Mesa zip file, compile and install it.
this is the software only implementation that should work everywhere even on framebuffer devices.
> One thing that has surprised me is how many seemingly unrelated packages have to
> get built to create the standard omap3-console image. Stuff like gtk,
> gstreamer, cairo, docbook, various graphics libs, etc.
OE and the Angstrom on top is a handheld operating system.
it will come with a richness of GUI tools that are probably triggered.
this might be libjpeg and text mode media players or even servers.
it would be a noticeable of effort to divide some tools into their
text mode and ther gui mode versions when a standard build just
merges in anything. even a simple "login" window like libcups
might need a rather big bunch of dependencys to build and install.
as soon as X11 from Xorg is triggered you might see anything.
to my best knowledge the "hidden" build step of making the
ext3fs image exposes lots of failing(!) gui config steps.
(i might be wrong as i am mostly working on stripped versions.)
> I want to create a deeply embedded system that simply boots and runs an OpenGL
> app and gives me access to ethernet, usb, wifi, etc. Bluetooth is nice but I
> don't need a full stack with streaming audio/video. It also needs the C++
> runtime libs as my app is C++ based.
go ahead and see the "dotty" files placed in a subfolder of the images.
they unveil the dependency tree. search for something unneded and
you will find out how they are mating to other needed components.
you might want to call "man imagemagick" for dotty and related details.
> So my question is this--is there a recipe I should look at starting from that
> will eliminate these dependencies? I don't need things like man pages, XML
> parsing, ncurses etc. I not only don't want their size in my rootfs, I don't
> want to wait for them to compile, I don't want them to bloat my build
> environment and I don't want them possibly breaking the apparently very fragile
> build process for open embedded/bitbake.
man pages should not install by default in small images. same for documentation.
each recipe is able to produce a big bunch of individual "opkg" compatible packages.
they have the file ending "ipk". a list of used/installed packages should be found
in those image build result subfolder as well. see also for a complete file listing there.
alternatively there might be a folder called angstroem.../rootfs that lets you see what is in the image.
let me say i am not up to date on the hardware support state on OMAP platform
when run with whatever version Angstrom and its build results.
More information about the Angstrom-distro-devel