From: cinda <vid...@gm...> - 2010-07-08 01:51:31
|
Hello all, I am newbie to gumstix and just finished building the image using the bitbake. Now,I want to install python, gstreamer and clutter on the gumstix overo board. I see recipes for these in the /overo-oe/org.openembedded.dev/recipes folder. I tried the following: bitbake python - it compiled well and made the .ipk files in the .../armv7a folder. Likewise bitbake gstreamer also worked. Now I can transfer these .ipk to gumstix and install there using ipkg command. Is my understanding right? Is there any other better way to install packages on gumstix? However my problem is bitbake clutter is not going through. The fetch is failing. None of the alternate sources are working. fetch http://install.source.dir.local/OMAP35x_Graphics_SDK_setuplinux_3_01_00_02.bin --2010-07-07 18:38:51-- http://install.source.dir.local/OMAP35x_Graphics_SDK_setuplinux_3_01_00_02.bin Resolving install.source.dir.local... failed: Name or service not known. wget: unable to resolve host address `install.source.dir.local' NOTE: fetch http://mirrors.openembedded.org//OMAP35x_Graphics_SDK_setuplinux_3_01_00_02.bin --2010-07-07 18:38:56-- http://mirrors.openembedded.org//OMAP35x_Graphics_SDK_setuplinux_3_01_00_02.bin Resolving mirrors.openembedded.org... 82.197.159.157 Connecting to mirrors.openembedded.org|82.197.159.157|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2010-07-07 18:38:57 ERROR 404: Not Found. -- View this message in context: http://old.nabble.com/install-clutter-on-gumstix-tp29100012p29100012.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dustin H. <du...@ho...> - 2010-07-08 04:31:48
|
On Wed, Jul 7, 2010 at 9:42 PM, cinda <vid...@gm...> wrote: > http://install.source.dir.local/OMAP35x_Graphics_SDK_setuplinux_3_01_00_02.bin As far as I am aware, this is a file you need to fetch manually (my apologies, I do not have the link handy) - I think that URL is a very subtle hint; it may also be a way to specify to bitbake that it should look for a file with that name but bitbake only accepts URLs (that seems like suspect logic to me, but it is plausible :P) Hopefully somebody can chime in with the link to the OMAP35xx Graphics SDK - you may be able to find it yourself before then, though. -- Dustin L. Howett |
From: Andreas M. <sch...@gm...> - 2010-07-08 06:05:27
|
Follow the instructions in recipes/powervr-drivers libgles-omap3.inc. Andreas |
From: Vidya M. <vid...@gm...> - 2010-07-08 21:37:22
|
NOTE: Running task 1418 of 1998 (ID: 9, /home/vidya/overo-oe/org.openembedded.dev/recipes/clutter/clutter_0.8+git.bb, do_compile) ERROR: function do_compile failed ERROR: log data follows (/home/vidya/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-0.8.8-r1.0+gitraf16378899699376fe7e84c7c11eb3bb5c4668cd/temp/log.do_compile.19051) | NOTE: make | make all-recursive | make[1]: Entering directory `/home/vidya/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-0.8.8-r1.0+gitraf16378899699376fe7e84c7c11eb3bb5c4668cd/git' | Making all in clutter | make[2]: Entering directory `/home/vidya/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-0.8.8-r1.0+gitraf16378899699376fe7e84c7c11eb3bb5c4668cd/git/clutter' | /home/vidya/overo-oe/tmp/sysroots/i686-linux/usr/bin/glib-genmarshal \ | --prefix=clutter_marshal \ | --header \ | ./clutter-marshal.list > xgen-cmh \ | && (cmp -s xgen-cmh clutter-marshal.h || cp xgen-cmh clutter-marshal.h ) \ | && rm -f xgen-cmh \ | && echo timestamp > stamp-clutter-marshal.h | ( echo "#include \"clutter-marshal.h\"" ; \ | /home/vidya/overo-oe/tmp/sysroots/i686-linux/usr/bin/glib-genmarshal \ | --prefix=clutter_marshal \ | --body \ | ./clutter-marshal.list --body ) >> xgen-cmc \ | && cp xgen-cmc clutter-marshal.c \ | && rm -f xgen-cmc | ( /home/vidya/overo-oe/tmp/sysroots/i686-linux/usr/bin/glib-mkenums \ | --template ./clutter-enum-types.h.in \ | ./clutter-actor.h ./clutter-alpha.h ./clutter-backend.h ./clutter-behaviour.h ./clutter-behaviour-bspline.h ./clutter-behaviour-depth.h ./clutter-behaviour-ellipse.h ./clutter-behaviour-opacity.h ./clutter-behaviour-path.h ./clutter-behaviour-rotate.h ./clutter-behaviour-scale.h ./clutter-child-meta.h ./clutter-clone-texture.h ./clutter-color.h ./clutter-container.h ./clutter-deprecated.h ./clutter-effect.h ./clutter-entry.h ./clutter-event.h ./clutter-feature.h ./clutter-fixed.h ./clutter-frame-source.h ./clutter-group.h ./clutter-keysyms.h ./clutter-label.h ./clutter-list-model.h ./clutter-main.h ./clutter-media.h ./clutter-model.h ./clutter-rectangle.h ./clutter-score.h ./clutter-script.h ./clutter-scriptable.h ./clutter-shader.h ./clutter-stage.h ./clutter-stage-manager.h ./clutter-texture.h ./clutter-timeline.h ./clutter-timeout-pool.h ./clutter-types.h ./clutter-units.h ./clutter-util.h ../clutter/clutter-version.h ) >> xgen-ceth && \ | (cmp xgen-ceth clutter-enum-types.h || cp xgen-ceth clutter-enum-types.h) && \ | rm -f xgen-ceth && \ | echo timestamp > stamp-clutter-enum-types.h | cmp: clutter-enum-types.h: No such file or directory | ( /home/vidya/overo-oe/tmp/sysroots/i686-linux/usr/bin/glib-mkenums \ | --template ./clutter-enum-types.c.in \ | ./clutter-actor.h ./clutter-alpha.h ./clutter-backend.h ./clutter-behaviour.h ./clutter-behaviour-bspline.h ./clutter-behaviour-depth.h ./clutter-behaviour-ellipse.h ./clutter-behaviour-opacity.h ./clutter-behaviour-path.h ./clutter-behaviour-rotate.h ./clutter-behaviour-scale.h ./clutter-child-meta.h ./clutter-clone-texture.h ./clutter-color.h ./clutter-container.h ./clutter-deprecated.h ./clutter-effect.h ./clutter-entry.h ./clutter-event.h ./clutter-feature.h ./clutter-fixed.h ./clutter-frame-source.h ./clutter-group.h ./clutter-keysyms.h ./clutter-label.h ./clutter-list-model.h ./clutter-main.h ./clutter-media.h ./clutter-model.h ./clutter-rectangle.h ./clutter-score.h ./clutter-script.h ./clutter-scriptable.h ./clutter-shader.h ./clutter-stage.h ./clutter-stage-manager.h ./clutter-texture.h ./clutter-timeline.h ./clutter-timeout-pool.h ./clutter-types.h ./clutter-units.h ./clutter-util.h ../clutter/clutter-version.h ) >> xgen-cetc && \ | cp xgen-cetc clutter-enum-types.c && \ | rm -f xgen-cetc | make all-recursive | make[3]: Entering directory `/home/vidya/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-0.8.8-r1.0+gitraf16378899699376fe7e84c7c11eb3bb5c4668cd/git/clutter' | Making all in cogl | make[4]: Entering directory `/home/vidya/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-0.8.8-r1.0+gitraf16378899699376fe7e84c7c11eb3bb5c4668cd/git/clutter/cogl' | Making all in common | make[5]: Entering directory `/home/vidya/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-0.8.8-r1.0+gitraf16378899699376fe7e84c7c11eb3bb5c4668cd/git/clutter/cogl/common' | /bin/sh ../../../arm-angstrom-linux-gnueabi-libtool --tag=CC --mode=compile ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../clutter -I../../../clutter/cogl -I../../../clutter/cogl/gles -I../../../clutter -I../../../clutter/cogl -DG_LOG_DOMAIN=\"Cogl\" -pthread -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/pango-1.0 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/cairo -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/glib-2.0 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/glib-2.0/include -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/pixman-1 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/freetype2 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/libpng12 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/gtk-2.0 -DCLUTTER_ENABLE_DEBUG -DG_DISABLE_CAST_CHECKS -g -Wall -isystem/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -isystem/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2 -ggdb3 -MT cogl-util.lo -MD -MP -MF .deps/cogl-util.Tpo -c -o cogl-util.lo cogl-util.c | arm-angstrom-linux-gnueabi-libtool: compile: ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../clutter -I../../../clutter/cogl -I../../../clutter/cogl/gles -I../../../clutter -I../../../clutter/cogl -DG_LOG_DOMAIN=\"Cogl\" -pthread -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/pango-1.0 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/cairo -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/glib-2.0 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/glib-2.0/include -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/pixman-1 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/freetype2 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/libpng12 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/gtk-2.0 -DCLUTTER_ENABLE_DEBUG -DG_DISABLE_CAST_CHECKS -g -Wall -isystem/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -isystem/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2 -ggdb3 -MT cogl-util.lo -MD -MP -MF .deps/cogl-util.Tpo -c cogl-util.c -fPIC -DPIC -o .libs/cogl-util.o | mv -f .deps/cogl-util.Tpo .deps/cogl-util.Plo | /bin/sh ../../../arm-angstrom-linux-gnueabi-libtool --tag=CC --mode=compile ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../clutter -I../../../clutter/cogl -I../../../clutter/cogl/gles -I../../../clutter -I../../../clutter/cogl -DG_LOG_DOMAIN=\"Cogl\" -pthread -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/pango-1.0 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/cairo -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/glib-2.0 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/glib-2.0/include -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/pixman-1 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/freetype2 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/libpng12 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/gtk-2.0 -DCLUTTER_ENABLE_DEBUG -DG_DISABLE_CAST_CHECKS -g -Wall -isystem/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -isystem/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2 -ggdb3 -MT cogl-bitmap.lo -MD -MP -MF .deps/cogl-bitmap.Tpo -c -o cogl-bitmap.lo cogl-bitmap.c | arm-angstrom-linux-gnueabi-libtool: compile: ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../clutter -I../../../clutter/cogl -I../../../clutter/cogl/gles -I../../../clutter -I../../../clutter/cogl -DG_LOG_DOMAIN=\"Cogl\" -pthread -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/pango-1.0 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/cairo -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/glib-2.0 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/glib-2.0/include -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/pixman-1 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/freetype2 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/libpng12 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/gtk-2.0 -DCLUTTER_ENABLE_DEBUG -DG_DISABLE_CAST_CHECKS -g -Wall -isystem/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -isystem/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2 -ggdb3 -MT cogl-bitmap.lo -MD -MP -MF .deps/cogl-bitmap.Tpo -c cogl-bitmap.c -fPIC -DPIC -o .libs/cogl-bitmap.o | mv -f .deps/cogl-bitmap.Tpo .deps/cogl-bitmap.Plo | /bin/sh ../../../arm-angstrom-linux-gnueabi-libtool --tag=CC --mode=compile ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../clutter -I../../../clutter/cogl -I../../../clutter/cogl/gles -I../../../clutter -I../../../clutter/cogl -DG_LOG_DOMAIN=\"Cogl\" -pthread -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/pango-1.0 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/cairo -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/glib-2.0 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/glib-2.0/include -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/pixman-1 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/freetype2 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/libpng12 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/gtk-2.0 -DCLUTTER_ENABLE_DEBUG -DG_DISABLE_CAST_CHECKS -g -Wall -isystem/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -isystem/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2 -ggdb3 -MT cogl-bitmap-fallback.lo -MD -MP -MF .deps/cogl-bitmap-fallback.Tpo -c -o cogl-bitmap-fallback.lo cogl-bitmap-fallback.c | arm-angstrom-linux-gnueabi-libtool: compile: ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../clutter -I../../../clutter/cogl -I../../../clutter/cogl/gles -I../../../clutter -I../../../clutter/cogl -DG_LOG_DOMAIN=\"Cogl\" -pthread -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/pango-1.0 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/cairo -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/glib-2.0 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/glib-2.0/include -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/pixman-1 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/freetype2 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/libpng12 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/gtk-2.0 -DCLUTTER_ENABLE_DEBUG -DG_DISABLE_CAST_CHECKS -g -Wall -isystem/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -isystem/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2 -ggdb3 -MT cogl-bitmap-fallback.lo -MD -MP -MF .deps/cogl-bitmap-fallback.Tpo -c cogl-bitmap-fallback.c -fPIC -DPIC -o .libs/cogl-bitmap-fallback.o | mv -f .deps/cogl-bitmap-fallback.Tpo .deps/cogl-bitmap-fallback.Plo | /bin/sh ../../../arm-angstrom-linux-gnueabi-libtool --tag=CC --mode=compile ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../clutter -I../../../clutter/cogl -I../../../clutter/cogl/gles -I../../../clutter -I../../../clutter/cogl -DG_LOG_DOMAIN=\"Cogl\" -pthread -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/pango-1.0 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/cairo -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/glib-2.0 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/glib-2.0/include -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/pixman-1 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/freetype2 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/libpng12 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/gtk-2.0 -DCLUTTER_ENABLE_DEBUG -DG_DISABLE_CAST_CHECKS -g -Wall -isystem/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -isystem/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2 -ggdb3 -MT cogl-primitives.lo -MD -MP -MF .deps/cogl-primitives.Tpo -c -o cogl-primitives.lo cogl-primitives.c | arm-angstrom-linux-gnueabi-libtool: compile: ccache arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../clutter -I../../../clutter/cogl -I../../../clutter/cogl/gles -I../../../clutter -I../../../clutter/cogl -DG_LOG_DOMAIN=\"Cogl\" -pthread -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/pango-1.0 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/cairo -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/glib-2.0 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/glib-2.0/include -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/pixman-1 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/freetype2 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/libpng12 -I/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/gtk-2.0 -DCLUTTER_ENABLE_DEBUG -DG_DISABLE_CAST_CHECKS -g -Wall -isystem/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -isystem/home/vidya/overo-oe/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2 -ggdb3 -MT cogl-primitives.lo -MD -MP -MF .deps/cogl-primitives.Tpo -c cogl-primitives.c -fPIC -DPIC -o .libs/cogl-primitives.o | In file included from ../../../clutter/cogl/gles/cogl-context.h:32, | from cogl-primitives.c:33: | ../../../clutter/cogl/gles/cogl-gles2-wrapper.h:203: error: expected ')' before 'r' | ../../../clutter/cogl/gles/cogl-gles2-wrapper.h:237: error: expected ')' before 'r' | make[5]: *** [cogl-primitives.lo] Error 1 | make[5]: Leaving directory `/home/vidya/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-0.8.8-r1.0+gitraf16378899699376fe7e84c7c11eb3bb5c4668cd/git/clutter/cogl/common' | make[4]: *** [all-recursive] Error 1 | make[4]: Leaving directory `/home/vidya/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-0.8.8-r1.0+gitraf16378899699376fe7e84c7c11eb3bb5c4668cd/git/clutter/cogl' | make[3]: *** [all-recursive] Error 1 | make[3]: Leaving directory `/home/vidya/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-0.8.8-r1.0+gitraf16378899699376fe7e84c7c11eb3bb5c4668cd/git/clutter' | make[2]: *** [all] Error 2 | make[2]: Leaving directory `/home/vidya/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-0.8.8-r1.0+gitraf16378899699376fe7e84c7c11eb3bb5c4668cd/git/clutter' | make[1]: *** [all-recursive] Error 1 | make[1]: Leaving directory `/home/vidya/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-0.8.8-r1.0+gitraf16378899699376fe7e84c7c11eb3bb5c4668cd/git' | make: *** [all] Error 2 | FATAL: oe_runmake failed NOTE: Task failed: /home/vidya/overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-0.8.8-r1.0+gitraf16378899699376fe7e84c7c11eb3bb5c4668cd/temp/log.do_compile.19051 ERROR: TaskFailed event exception, aborting ERROR: Build of /home/vidya/overo-oe/org.openembedded.dev/recipes/clutter/clutter_0.8+git.bb do_compile failed ERROR: Task 9 (/home/vidya/overo-oe/org.openembedded.dev/recipes/clutter/clutter_0.8+git.bb, do_compile) failed NOTE: Tasks Summary: Attempted 1417 tasks of which 1413 didn't need to be rerun and 1 failed. ERROR: '/home/vidya/overo-oe/org.openembedded.dev/recipes/clutter/clutter_0.8+git.bb' failed |
From: Vidya M. <vid...@gm...> - 2010-07-09 03:51:30
|
I realised hat I can call a different .bb version by specifying that while calling the bitbake command. -- View this message in context: http://old.nabble.com/install-clutter-on-gumstix-tp29100012p29113985.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Andreas M. <sch...@gm...> - 2010-07-09 07:19:12
|
DESCRIPTION = "Clutter graphics library" HOMEPAGE = "http://www.clutter-project.org/" LICENSE = "LGPL" COMPATIBLE_MACHINE = "(zylonite|mx31litekit|omap-3430ldp|omap-3430sdp|mx31ads|qemuarm|qemux86|ipodtouch|am3517-evm|dm3730-am3715-evm|beagleboard|overo|omap3evm|omap5912osk)" STDDEPENDS = "virtual/libx11 pango glib-2.0 libxfixes gtk+ cairo" BASE_CONF = "--disable-docs --disable-gtk-doc --enable-conform ${@get_clutter_fpu_setting(bb, d)}" DEPENDS = "${STDDEPENDS} virtual/libgl" EXTRA_OECONF = "${BASE_CONF} --with-flavour=glx" DEPENDS_zylonite = "${STDDEPENDS} libgles-zylonite tslib" EXTRA_OECONF_zylonite = "${BASE_CONF} --with-flavour=eglnative" PACKAGE_ARCH_zylonite = "${MACHINE_ARCH}" LDFLAGS_append_zylonite = " -lnws -lstdc++ " DEPENDS_mx31litekit = "${STDDEPENDS} libgles-mx31 tslib" EXTRA_OECONF_mx31litekit = "${BASE_CONF} --with-flavour=eglnative" PACKAGE_ARCH_mx31litekit = "${MACHINE_ARCH}" LDFLAGS_append_mx31litekit = " -lpvrNULLWSEGL -lstdc++ " DEPENDS_armv7a = "${STDDEPENDS} libgles-omap3 tslib" EXTRA_OECONF_armv7a = "${BASE_CONF} --with-flavour=eglx --with-gles=2.0" PACKAGE_ARCH_armv7a = "${MACHINE_ARCH}" DEPENDS_omap-3430ldp = "${STDDEPENDS} libgles-omap3 tslib" EXTRA_OECONF_omap-3430ldp = "${BASE_CONF} --with-flavour=eglx" PACKAGE_ARCH_omap-3430ldp = "${MACHINE_ARCH}" DEPENDS_omap-3430sdp = "${STDDEPENDS} libgles-omap3 tslib" EXTRA_OECONF_omap-3430sdp = "${BASE_CONF} --with-flavour=eglx" PACKAGE_ARCH_omap-3430sdp = "${MACHINE_ARCH}" DEPENDS_mx31ads = "${STDDEPENDS} libgles-mx31 tslib" EXTRA_OECONF_mx31ads = "${BASE_CONF} --with-flavour=eglnative" PACKAGE_ARCH_mx31ads = "${MACHINE_ARCH}" LDFLAGS_append_mx31ads = " -lpvrNULLWSEGL -lstdc++ " INC_PR = "r2" inherit autotools pkgconfig #clutter tests are not (yet?) prepared for install! #PACKAGES =+ "clutter-tests" #FILES_clutter-tests = "${bindir}/tests ${pkgdatadir}/redhand.png" #check for TARGET_FPU=soft and inform configure of the result so it can disable some floating points require clutter-fpu.inc do_configure_prepend() { # Fix up 'Requires' entries in *.pc.in to prevent from bb-notes for i in $(find ${S} -name '*.pc.in') ; do sed -i s:'${requires}':'@CLUTTER_REQUIRES@':g $i done #Fix up some weirdness in the docs # if [ -e ${WORKDIR}/gtk-doc.make ] ; then # cp ${WORKDIR}/gtk-doc.make ${S}/gtk-doc.make # else # touch ${S}/gtk-doc.make # fi # sed -i s:doc/reference/Makefile::g ${S}/configure.ac # sed -i s:doc::g ${S}/Makefile.am } |
From: Vidya M. <vid...@gm...> - 2010-07-09 08:42:11
|
That explains why bitbake was taking libgles-omap3_3.01.00.02.bb. Thanks. I did see the /recipe/libgles-omap3_3.01.00.06.bb.I commented off the contents of the default one and pasted the contnts of libgles-omap3_3.01.00.06.bb into it. Likewise for libgles-sgx-modules*.bb. So in effect I have used libgles-omap3_3.01.00.06.bb recipe. I can see ../OMAP35x_Graphics_SDK_3_01_00_06/ and OMAP35x_Graphics_SDK_setuplinux_3_01_00_06.bin inside ../overo-oe/tmp/work/overo-angstrom-linux-gnueabi/omap3-sgx-modules-1.4.14.2616-r80/ . So it seems to have got installed. That said I didn't understand what you meant by : "With ' git-blame -L 1,1 recipes/powervr-drivers/libgles-omap3_3.01.00.06.bb' and git-log 2a48b671 you get:powervr-drivers: disable build using 3_01_00_06 release since it won't build for 2.6.33". Can you please expand this for me. Since I have already used libgles-omap3_3.01.00.06.bb, will cleaning and rebuilding make any difference? I can rebuild and let you know in any case. You seem to be working on the later clutter versions. I am very new to embedded dev and gumstix, still to try out building own packages with dependencies. I will try your recipes and let you know if it builds for me. Thanks, Vidya. On Fri, Jul 9, 2010 at 12:13 AM, Andreas Mueller <sch...@gm...>wrote: > On Thursday 08 July 2010 11:37:15 pm Vidya Menon wrote: > > > 1) It was again looking for the older version. So replaced the contents > of > > > libgles-omap3_3.01.00.02.bb with that of libgles-omap3_3.01.00.06.bb and > the > > > contents of omap3-sgx-modules_1.4.14.2514.bb with the that of > > > omap3-sgx-modules_1.4.14.2616.bb > > > Instead is there a way to specify which recipe to choose. (that is choose > > > libgles-omap3_3.01.00.06.bb instead of libgles-omap3_3.01.00.02.bb). > > > Although the installation of SDK went without errors, I hope I didn't > screw > > > up anything by doing this. Please confirm. > > If you take a look in recipes/powervr-drivers there is already a recipe > libgles-omap3_3.01.00.06.bb. This is disabled by DEFAULT_PREFERENCE = > "-1". With ' git-blame -L 1,1 recipes/powervr-drivers/ > libgles-omap3_3.01.00.06.bb' and git-log 2a48b671 you get: > > powervr-drivers: disable build using 3_01_00_06 release since it won't > build for 2.6.33 > > So I suggest: clean libgles & omap3-sgx-modules, comment out > DEFAULT_PREFERENCE = "-1" in libgles-omap3_3.01.00.06.bb and rebuild (let > us know the result). > > > 2) Going further, I am facing some errors.I have attached the error log > > > .According to which the error is in these two lines in the file > > > > ...../overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-0.8.8-r1.0+gitraf16378899699376fe7e84c7c11eb3bb5c4668cd/git/clutter/cogl/cogl-gles2-wrapper.h > > > > > > void cogl_wrap_glClearColorx (GLclampx r, GLclampx g, GLclampx b, > GLclampx > > > a); > > > void cogl_wrap_glColor4x (GLclampx r, GLclampx g, GLclampx b, GLclampx > a); > > > > > > expected ')' before 'r'. Am I missing something? > > It seems that all the clutter stuff is in a very early experimental state. > I am currently working on this. If you want you can try the recipes in the > attachment. They build for me, but there are some issues to sort out (I > would like to have the clutter tests build in a seperate package). Therefore > I did not yet send them to OE-devel. No experience yet if they do run - > feedback welcome... > > Andreas > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Vidya M. <vid...@gm...> - 2010-07-09 09:10:35
|
[edit] Files inside../overo-oe/tmp/work/overo-angstrom-linux-gnueabi/omap3-sgx-modules-1.4.14.2616-r80/ . doesn't necessarily mean that it got installed right! On Fri, Jul 9, 2010 at 1:42 AM, Vidya Menon <vid...@gm...> wrote: > That explains why bitbake was taking libgles-omap3_3.01.00.02.bb. Thanks. > I did see the /recipe/libgles-omap3_3.01.00.06.bb.I commented off the > contents of the default one and pasted the contnts of > libgles-omap3_3.01.00.06.bb into it. Likewise for libgles-sgx-modules*.bb. > So in effect I have used libgles-omap3_3.01.00.06.bb recipe. I can see > ../OMAP35x_Graphics_SDK_3_01_00_06/ and > OMAP35x_Graphics_SDK_setuplinux_3_01_00_06.bin inside > ../overo-oe/tmp/work/overo-angstrom-linux-gnueabi/omap3-sgx-modules-1.4.14.2616-r80/ > . So it seems to have got installed. > > That said I didn't understand what you meant by : > > "With ' git-blame -L 1,1 recipes/powervr-drivers/ > libgles-omap3_3.01.00.06.bb' and git-log 2a48b671 > you get:powervr-drivers: disable build using 3_01_00_06 release since it > won't build for 2.6.33". > Can you please expand this for me. > > Since I have already used libgles-omap3_3.01.00.06.bb, will cleaning and > rebuilding make any difference? I can rebuild and let you know in any case. > > You seem to be working on the later clutter versions. I am very new to > embedded dev and gumstix, still to try out building own packages with > dependencies. I will try your recipes and let you know if it builds for me. > > Thanks, > Vidya. > > > On Fri, Jul 9, 2010 at 12:13 AM, Andreas Mueller <sch...@gm...>wrote: > >> On Thursday 08 July 2010 11:37:15 pm Vidya Menon wrote: >> >> > 1) It was again looking for the older version. So replaced the contents >> of >> >> > libgles-omap3_3.01.00.02.bb with that of libgles-omap3_3.01.00.06.bband the >> >> > contents of omap3-sgx-modules_1.4.14.2514.bb with the that of >> >> > omap3-sgx-modules_1.4.14.2616.bb >> >> > Instead is there a way to specify which recipe to choose. (that is >> choose >> >> > libgles-omap3_3.01.00.06.bb instead of libgles-omap3_3.01.00.02.bb). >> >> > Although the installation of SDK went without errors, I hope I didn't >> screw >> >> > up anything by doing this. Please confirm. >> >> If you take a look in recipes/powervr-drivers there is already a recipe >> libgles-omap3_3.01.00.06.bb. This is disabled by DEFAULT_PREFERENCE = >> "-1". With ' git-blame -L 1,1 recipes/powervr-drivers/ >> libgles-omap3_3.01.00.06.bb' and git-log 2a48b671 you get: >> >> powervr-drivers: disable build using 3_01_00_06 release since it won't >> build for 2.6.33 >> >> So I suggest: clean libgles & omap3-sgx-modules, comment out >> DEFAULT_PREFERENCE = "-1" in libgles-omap3_3.01.00.06.bb and rebuild (let >> us know the result). >> >> > 2) Going further, I am facing some errors.I have attached the error log >> >> > .According to which the error is in these two lines in the file >> >> > >> ...../overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-0.8.8-r1.0+gitraf16378899699376fe7e84c7c11eb3bb5c4668cd/git/clutter/cogl/cogl-gles2-wrapper.h >> >> > >> >> > void cogl_wrap_glClearColorx (GLclampx r, GLclampx g, GLclampx b, >> GLclampx >> >> > a); >> >> > void cogl_wrap_glColor4x (GLclampx r, GLclampx g, GLclampx b, GLclampx >> a); >> >> > >> >> > expected ')' before 'r'. Am I missing something? >> >> It seems that all the clutter stuff is in a very early experimental state. >> I am currently working on this. If you want you can try the recipes in the >> attachment. They build for me, but there are some issues to sort out (I >> would like to have the clutter tests build in a seperate package). Therefore >> I did not yet send them to OE-devel. No experience yet if they do run - >> feedback welcome... >> >> Andreas >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > |
From: Andreas M. <sch...@gm...> - 2010-07-09 09:28:03
|
On Friday 09 July 2010 10:42:03 am Vidya Menon wrote: > That said I didn't understand what you meant by : > "With ' git-blame -L 1,1 recipes/powervr-drivers/libgles-omap3_3.01.00.06.bb' > and git-log 2a48b671 > you get:powervr-drivers: disable build using 3_01_00_06 release since it > won't build for 2.6.33". > Can you please expand this for me. git-blame is a very strong tool to check who has changed a certain (part of) file. It outputs the commit ID (maybe there is an option to get additional commit information). The commit ID for this issue was 2a48b671. With git-log you get more information of the commit. Try 'man git-blame' or 'man git-log' for more information. > Since I have already used libgles-omap3_3.01.00.06.bb, will cleaning and > rebuilding make any difference? I can rebuild and let you know in any case. Yes all files created are handled under version 3_01_00_02 although they come from 3_01_00_06. I don't know if this causes trouble but removing DEFAULT_PREFERENCE = "-1" is the more clean approach. Andreas |
From: Vidya M. <vid...@gm...> - 2010-07-10 07:36:34
|
-- I cleaned and did the rebuild. Installation got completed with libgles-omap3_3.01.00.06.bb. -- I tried building the clutter recipes. It compiled. But omap3-sgx-modules_1.4.14.2616.bb do_package has errors and do_compile failed. I have attached the error log. Did you complete building it with the *.02 version? http://old.nabble.com/file/p29124560/log_clutter.txt log_clutter.txt Thanks, Vidya. -- View this message in context: http://old.nabble.com/install-clutter-on-gumstix-tp29100012p29124560.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Andreas M. <sch...@gm...> - 2010-07-11 07:21:37
|
On Saturday 10 July 2010 09:36:28 am Vidya Menon wrote: > -- I tried building the clutter recipes. It compiled. But > omap3-sgx-modules_1.4.14.2616.bb do_package has errors and do_compile > failed. I have attached the error log. Did you complete building it with the > *.02 version? I had success with *.02 TI stuff Andreas |
From: Vidya M. <vid...@gm...> - 2010-07-12 20:27:57
|
Hi, I tried to go back to previous kernel version. It didn't work. Now trying with the *.02 TI bin. I am getting error with the omap3-sgx-modules_1.4.14.2514.bb. NOTE: Running task 1387 of 1998 (ID: 321, /home/vidya/overo-oe/org.openembedded.dev/recipes/powervr-drivers/omap3-sgx-modules_1.4.14.2514.bb, do_fetch) NOTE: Task failed: Malformed URL: 3_01_00_02.bin ERROR: TaskFailed event exception, aborting ERROR: Build of /home/vidya/overo-oe/org.openembedded.dev/recipes/powervr-drivers/omap3-sgx-modules_1.4.14.2514.bb do_fetch failed ERROR: Task 321 (/home/vidya/overo-oe/org.openembedded.dev/recipes/powervr-drivers/omap3-sgx-modules_1.4.14.2514.bb, do_fetch) failed NOTE: Tasks Summary: Attempted 1386 tasks of which 1386 didn't need to be rerun and 1 failed. ERROR: '/home/vidya/overo-oe/org.openembedded.dev/recipes/powervr-drivers/omap3-sgx-modules_1.4.14.2514.bb' failed. Please help. Thanks Vidya. Schnitzeltony wrote: > > On Saturday 10 July 2010 09:36:28 am Vidya Menon wrote: >> -- I tried building the clutter recipes. It compiled. But >> omap3-sgx-modules_1.4.14.2616.bb do_package has errors and do_compile >> failed. I have attached the error log. Did you complete building it with >> the >> *.02 version? > > I had success with *.02 TI stuff > > Andreas > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/install-clutter-on-gumstix-tp29100012p29143597.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Andreas M. <sch...@gm...> - 2010-07-12 21:03:15
|
On Monday 12 July 2010 10:27:51 pm Vidya Menon wrote: > > Hi, > > I tried to go back to previous kernel version. It didn't work. > Now trying with the *.02 TI bin. I am getting error with the > omap3-sgx-modules_1.4.14.2514.bb. > > NOTE: Running task 1387 of 1998 (ID: 321, > /home/vidya/overo-oe/org.openembedded.dev/recipes/powervr-drivers/omap3-sgx-modules_1.4.14.2514.bb, > do_fetch) > NOTE: Task failed: Malformed URL: 3_01_00_02.bin > ERROR: TaskFailed event exception, aborting > ERROR: Build of > /home/vidya/overo-oe/org.openembedded.dev/recipes/powervr-drivers/omap3-sgx-modules_1.4.14.2514.bb > do_fetch failed > ERROR: Task 321 > (/home/vidya/overo-oe/org.openembedded.dev/recipes/powervr-drivers/omap3-sgx-modules_1.4.14.2514.bb, > do_fetch) failed > NOTE: Tasks Summary: Attempted 1386 tasks of which 1386 didn't need to be > rerun and 1 failed. > ERROR: > '/home/vidya/overo-oe/org.openembedded.dev/recipes/powervr-drivers/omap3-sgx-modules_1.4.14.2514.bb' > failed. > > Please help. > > Thanks > Vidya. Hm one question: Is it possible that you started your first build (especially for omap3-sgx-modules) with a different version of OE - or with other words - did you git-pull without full rebuild (deleting tmp)? If yes: I think you are a victim of the error in current gumstix-OE in base.bbclass / decodeurl. For further details see: http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-July/021324.html or http://old.nabble.com/Angstrom-version-error-td29072187.html If no: Check your changes with git-status. |
From: Vidya M. <vid...@gm...> - 2010-07-12 21:37:18
|
I think I tampered with it while trying to change the SRC_URI to and fro. I downloaded a new copy from http://gitorious.org/gumstix-oe/mainline/blobs/3c35f58e2f488034007c07e77d3a467ae46a601a/recipes/powervr-drivers/omap3-sgx-modules_1.4.14.2514.bband it installed fine. The recipe that you had posted ( clutter_1.2.10.bb ) build fine. But how do I install this on gumstix. I don't see any new ipks formed for clutter. Are you working on building the other clutter modules for 1.2 version for gumstix? Also, do I have to install any new git package if I have to use the git utilities. I have installed only git-core. vidya@vidya-laptop:~$ git-status git-status: command not found vidya@vidya-laptop:~$ git-blame -L 1,1 recipes/powervr-drivers/ libgles-omap3_3.01.00.06.bb git-blame: command not found vidya@vidya-laptop:~$ git blame -L 1,1 recipes/powervr-drivers/ libgles-omap3_3.01.00.06.bb fatal: Not a git repository (or any of the parent directories): .git Thanks a lot!! Vidya. On Mon, Jul 12, 2010 at 1:56 PM, Andreas Mueller <sch...@gm...>wrote: > On Monday 12 July 2010 10:27:51 pm Vidya Menon wrote: > > > > Hi, > > > > I tried to go back to previous kernel version. It didn't work. > > Now trying with the *.02 TI bin. I am getting error with the > > omap3-sgx-modules_1.4.14.2514.bb. > > > > NOTE: Running task 1387 of 1998 (ID: 321, > > /home/vidya/overo-oe/org.openembedded.dev/recipes/powervr-drivers/ > omap3-sgx-modules_1.4.14.2514.bb, > > do_fetch) > > NOTE: Task failed: Malformed URL: 3_01_00_02.bin > > ERROR: TaskFailed event exception, aborting > > ERROR: Build of > > /home/vidya/overo-oe/org.openembedded.dev/recipes/powervr-drivers/ > omap3-sgx-modules_1.4.14.2514.bb > > do_fetch failed > > ERROR: Task 321 > > (/home/vidya/overo-oe/org.openembedded.dev/recipes/powervr-drivers/ > omap3-sgx-modules_1.4.14.2514.bb, > > do_fetch) failed > > NOTE: Tasks Summary: Attempted 1386 tasks of which 1386 didn't need to be > > rerun and 1 failed. > > ERROR: > > '/home/vidya/overo-oe/org.openembedded.dev/recipes/powervr-drivers/ > omap3-sgx-modules_1.4.14.2514.bb' > > failed. > > > > Please help. > > > > Thanks > > Vidya. > > Hm one question: > > Is it possible that you started your first build (especially for > omap3-sgx-modules) with a different version of OE - or with other words - > did you git-pull without full rebuild (deleting tmp)? > > If yes: I think you are a victim of the error in current gumstix-OE in > base.bbclass / decodeurl. > > For further details see: > > http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-July/021324.htmlor > http://old.nabble.com/Angstrom-version-error-td29072187.html > > If no: Check your changes with git-status. > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Andreas M. <sch...@gm...> - 2010-07-12 22:43:05
|
On Monday 12 July 2010 11:37:11 pm Vidya Menon wrote: > I think I tampered with it while trying to change the SRC_URI to and fro. I > downloaded a new copy from > http://gitorious.org/gumstix-oe/mainline/blobs/3c35f58e2f488034007c07e77d3a467ae46a601a/recipes/powervr-drivers/omap3-sgx-modules_1.4.14.2514.bband > it installed fine. The recipe that you had posted ( > clutter_1.2.10.bb ) build fine. But how do I install this on gumstix. I > don't see any new ipks formed for clutter. Are you working on building the > other clutter modules for 1.2 version for gumstix? yes but right now I am in trouble with mutter and clutter-gst. It seems that both do not compile due to clutter not properly configured/installed when the machine uses gles2. I checked: When forcing gl instead of gles2 by commenting out EXTRA_OECONF_armv7a = "${BASE_CONF} --with-flavour=eglx --with-gles=2.0" in clutter.inc both compile successfully... > > Also, do I have to install any new git package if I have to use the git > utilities. I have installed only git-core. Have you seen http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Setting-up-a-build-environment/111.html ? |
From: Vidya M. <vid...@gm...> - 2010-07-13 20:24:26
|
Hi Andreas, Reg: Building own packages. I am trying to add more .bb to this set. But I have couple of doubts. After I run the clutter-1.2.10 bitbake, I dont have a /overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-1.2.10-r2.0/install directory and its not getting packaged. I see the default functions being executed. Also, say I have mulitple .bb files inside the clutter directory - clutter-gst.bb, pyclutter.bb etc. Does bitbake automatically execute and install all of them? Say inside pyclutter.bb I can state DEPENDS = "clutter-1.2.10" , but how does pyclutter.bb get executed in the first place.I don't understand/see any explicit lines in clutter.inc ( in the clutter-0.9 from the repository) for doing this. Thanks, Vidya. On Mon, Jul 12, 2010 at 3:36 PM, Andreas Mueller <sch...@gm...>wrote: > On Monday 12 July 2010 11:37:11 pm Vidya Menon wrote: > > I think I tampered with it while trying to change the SRC_URI to and fro. > I > > downloaded a new copy from > > > http://gitorious.org/gumstix-oe/mainline/blobs/3c35f58e2f488034007c07e77d3a467ae46a601a/recipes/powervr-drivers/omap3-sgx-modules_1.4.14.2514.bband > > it installed fine. The recipe that you had posted ( > > clutter_1.2.10.bb ) build fine. But how do I install this on gumstix. I > > don't see any new ipks formed for clutter. Are you working on building > the > > other clutter modules for 1.2 version for gumstix? > yes but right now I am in trouble with mutter and clutter-gst. It seems > that both do not compile due to clutter not properly configured/installed > when the machine uses gles2. I checked: When > forcing gl instead of gles2 by commenting out > > EXTRA_OECONF_armv7a = "${BASE_CONF} --with-flavour=eglx --with-gles=2.0" > > in clutter.inc both compile successfully... > > > > > Also, do I have to install any new git package if I have to use the git > > utilities. I have installed only git-core. > Have you seen > http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Setting-up-a-build-environment/111.html? > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Andreas M. <sch...@gm...> - 2010-07-13 22:10:56
|
On Tuesday 13 July 2010 10:24:19 pm Vidya Menon wrote: > I am trying to add more .bb to this set. But I have couple of doubts. After > I run the clutter-1.2.10 bitbake, I dont have a > /overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-1.2.10-r2.0/install > directory and its not getting packaged. I see the default functions being > executed. see: http://docs.openembedded.org/usermanual/usermanual.html#usage_tasks http://docs.openembedded.org/usermanual/usermanual.html#directories_installation > Also, say I have mulitple .bb files inside the clutter directory - > clutter-gst.bb, pyclutter.bb etc. Does bitbake automatically execute and > install all of them? Say inside pyclutter.bb I can state DEPENDS = > "clutter-1.2.10" , but how does pyclutter.bb get executed in the first > place.I don't understand/see any explicit lines in clutter.inc ( in the > clutter-0.9 from the repository) for doing this. There are (at least) two possible things to build: - Images: All you need for a running system (bootloader/kernel/rootfs..) is build by images. Prepared are found at <oe_base>/recipes/images. - Single packages: If there is no preferred version set by the distribution (for us <oe_base>/conf/distro/angstrom-2008.1.conf and the files included by 'require') or the machine (for us <oe_base>/conf/overo.conf and the files included by 'require') the file name with the maximum version is build. see: http://docs.openembedded.org/usermanual/usermanual.html#recipes_versioning http://docs.openembedded.org/usermanual/usermanual.html#recipes_package_relationships |
From: Vidya M. <vid...@gm...> - 2010-07-14 02:44:45
|
Hi Andreas, Thanks! Sorry, I am using the recipes that you had posted as my entry point. If you don't mind that. So the overo specific packages (.ipk) are installed into /overo-oe/tmp/deploy/glibc/ipk/overo/ and the packages are split into : libclutter-glx-1.0-0_1.2.10-r2.0.5_overo.ipk, libclutter-glx-1.0-dbg_1.2.10-r2.0.5_overo.ipk, libclutter-glx-1.0-dev_1.2.10-r2.0.5_overo.ipk, libclutter-glx-1.0-doc_1.2.10-r2.0.5_overo.ipk right? I didn't notice them before as I was looking for packages starting with clutter* . So just wanted to confirm that these are the packages in question. I understand that the maximum version gets build if it is not specified. However, I have put them in the user.collection/recipes folder so that it will override the other recipes with the same name. My second question was slightly different: Say for example take python recipe in the /recipes/python folder. When I run 'bitbake python' it uses the python_2.6.4.bb recipe to build python. However, if the user knows that he would also require, python-gst ( python-gst_0.10.10.bb which is also present in the /recipes/python folder, how will he build that also. RRECOMMENDS can only recommend a package right? Is it possible that it will get build. Context of my question: Right now we have clutter, clutter-gtk, clutter-gst etc to build. Is there a case where all are build at the same time. Not rushing into it. Just curious to know how to build interested recipes which comes inside the same folder. Otherwise why would the module be split into different packages ( like for python : it has got split into many packages. Initially I confused this with each recipe inside the same folder(eg /recipes/python/) resulting in a package ! Thanks a lot for your time! Regards, Vidya. On Tue, Jul 13, 2010 at 3:03 PM, Andreas Mueller <sch...@gm...>wrote: > On Tuesday 13 July 2010 10:24:19 pm Vidya Menon wrote: > > I am trying to add more .bb to this set. But I have couple of doubts. > After > > I run the clutter-1.2.10 bitbake, I dont have a > > > /overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-1.2.10-r2.0/install > > directory and its not getting packaged. I see the default functions > being > > executed. > > see: > http://docs.openembedded.org/usermanual/usermanual.html#usage_tasks > > http://docs.openembedded.org/usermanual/usermanual.html#directories_installation > > > Also, say I have mulitple .bb files inside the clutter directory - > > clutter-gst.bb, pyclutter.bb etc. Does bitbake automatically execute and > > install all of them? Say inside pyclutter.bb I can state DEPENDS = > > "clutter-1.2.10" , but how does pyclutter.bb get executed in the first > > place.I don't understand/see any explicit lines in clutter.inc ( in the > > clutter-0.9 from the repository) for doing this. > There are (at least) two possible things to build: > > - Images: All you need for a running system (bootloader/kernel/rootfs..) is > build by images. Prepared are found at <oe_base>/recipes/images. > - Single packages: If there is no preferred version set by the distribution > (for us <oe_base>/conf/distro/angstrom-2008.1.conf and the files included by > 'require') or the machine (for us > <oe_base>/conf/overo.conf and the files included by 'require') the file > name with the maximum version is build. > > see: > http://docs.openembedded.org/usermanual/usermanual.html#recipes_versioning > > http://docs.openembedded.org/usermanual/usermanual.html#recipes_package_relationships > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Vidya M. <vid...@gm...> - 2010-07-14 03:28:51
|
Update: I think I got a probable answer. If I run python-gst*.bb directly then it will build all the packages (using the corresponding .bb) recursively specified in the DEPENDS field. Back-ward dependency (ie building python-gst when we call for python) would just be an overhead. Correct me if I am wrong. Thanks, Vidya. On Tue, Jul 13, 2010 at 7:44 PM, Vidya Menon <vid...@gm...> wrote: > Hi Andreas, > > Thanks! > > Sorry, I am using the recipes that you had posted as my entry point. If you > don't mind that. > So the overo specific packages (.ipk) are installed into > /overo-oe/tmp/deploy/glibc/ipk/overo/ > and the packages are split into : > libclutter-glx-1.0-0_1.2.10-r2.0.5_overo.ipk, > libclutter-glx-1.0-dbg_1.2.10-r2.0.5_overo.ipk, > libclutter-glx-1.0-dev_1.2.10-r2.0.5_overo.ipk, > libclutter-glx-1.0-doc_1.2.10-r2.0.5_overo.ipk right? I didn't notice them > before as I was looking for packages starting with clutter* . So just wanted > to confirm that these are the packages in question. > > I understand that the maximum version gets build if it is not specified. > However, I have put them in the user.collection/recipes folder so that it > will override the other recipes with the same name. > My second question was slightly different: > Say for example take python recipe in the /recipes/python folder. When I > run 'bitbake python' it uses the python_2.6.4.bb recipe to build python. > However, if the user knows that he would also require, python-gst ( > python-gst_0.10.10.bb which is also present in the /recipes/python folder, > how will he build that also. RRECOMMENDS can only recommend a package right? > Is it possible that it will get build. > > Context of my question: Right now we have clutter, clutter-gtk, clutter-gst > etc to build. Is there a case where all are build at the same time. Not > rushing into it. Just curious to know how to build interested recipes which > comes inside the same folder. Otherwise why would the module be split into > different packages ( like for python : it has got split into many packages. > Initially I confused this with each recipe inside the same folder(eg > /recipes/python/) resulting in a package ! > > Thanks a lot for your time! > Regards, > Vidya. > > > > > On Tue, Jul 13, 2010 at 3:03 PM, Andreas Mueller <sch...@gm...>wrote: > >> On Tuesday 13 July 2010 10:24:19 pm Vidya Menon wrote: >> > I am trying to add more .bb to this set. But I have couple of doubts. >> After >> > I run the clutter-1.2.10 bitbake, I dont have a >> > >> /overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-1.2.10-r2.0/install >> > directory and its not getting packaged. I see the default functions >> being >> > executed. >> >> see: >> http://docs.openembedded.org/usermanual/usermanual.html#usage_tasks >> >> http://docs.openembedded.org/usermanual/usermanual.html#directories_installation >> >> > Also, say I have mulitple .bb files inside the clutter directory - >> > clutter-gst.bb, pyclutter.bb etc. Does bitbake automatically execute >> and >> > install all of them? Say inside pyclutter.bb I can state DEPENDS = >> > "clutter-1.2.10" , but how does pyclutter.bb get executed in the first >> > place.I don't understand/see any explicit lines in clutter.inc ( in the >> > clutter-0.9 from the repository) for doing this. >> There are (at least) two possible things to build: >> >> - Images: All you need for a running system (bootloader/kernel/rootfs..) >> is build by images. Prepared are found at <oe_base>/recipes/images. >> - Single packages: If there is no preferred version set by the >> distribution (for us <oe_base>/conf/distro/angstrom-2008.1.conf and the >> files included by 'require') or the machine (for us >> <oe_base>/conf/overo.conf and the files included by 'require') the file >> name with the maximum version is build. >> >> see: >> http://docs.openembedded.org/usermanual/usermanual.html#recipes_versioning >> >> http://docs.openembedded.org/usermanual/usermanual.html#recipes_package_relationships >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > |
From: Vidya M. <vid...@gm...> - 2010-07-14 08:43:17
|
Hi, I wrote a new recipe for clutter-gst to use the latest version. As you said, it builds fine on forcing gl. But I am facing some issues with the clutter-gst-video-sink.c for gles2. ./clutter-gst-video-sink.c: At top level: | ./clutter-gst-video-sink.c:138: error: expected ')' before 'GLUNIFORM1IPROC' | ./clutter-gst-video-sink.c:140: error: expected ')' before 'GLGENPROGRAMSPROC' | ./clutter-gst-video-sink.c:141: error: expected ')' before 'GLBINDPROGRAMPROC' | ./clutter-gst-video-sink.c:142: error: expected ')' before 'GLPROGRAMSTRINGPROC' | ./clutter-gst-video-sink.c:147: error: expected specifier-qualifier-list before 'GLGENPROGRAMSPROC' 'APIENTRYP' itself is not defined anywhere. Could that be the problem? I noticed that clutter-gst is dependent on gst-plugins-base and ran bitbake gst-plugins-base*.bb also. But still I am having these errors. Could you build it successfully? Also, what restrictions would it have if gl is forced? Thanks, Vidya. On Tue, Jul 13, 2010 at 8:28 PM, Vidya Menon <vid...@gm...> wrote: > Update: > I think I got a probable answer. > If I run python-gst*.bb directly then it will build all the packages (using > the corresponding .bb) recursively specified in the DEPENDS field. Back-ward > dependency (ie building python-gst when we call for python) would just be an > overhead. Correct me if I am wrong. > > Thanks, > Vidya. > > > > On Tue, Jul 13, 2010 at 7:44 PM, Vidya Menon <vid...@gm...> wrote: > >> Hi Andreas, >> >> Thanks! >> >> Sorry, I am using the recipes that you had posted as my entry point. If >> you don't mind that. >> So the overo specific packages (.ipk) are installed into >> /overo-oe/tmp/deploy/glibc/ipk/overo/ >> and the packages are split into : >> libclutter-glx-1.0-0_1.2.10-r2.0.5_overo.ipk, >> libclutter-glx-1.0-dbg_1.2.10-r2.0.5_overo.ipk, >> libclutter-glx-1.0-dev_1.2.10-r2.0.5_overo.ipk, >> libclutter-glx-1.0-doc_1.2.10-r2.0.5_overo.ipk right? I didn't notice them >> before as I was looking for packages starting with clutter* . So just wanted >> to confirm that these are the packages in question. >> >> I understand that the maximum version gets build if it is not specified. >> However, I have put them in the user.collection/recipes folder so that it >> will override the other recipes with the same name. >> My second question was slightly different: >> Say for example take python recipe in the /recipes/python folder. When I >> run 'bitbake python' it uses the python_2.6.4.bb recipe to build python. >> However, if the user knows that he would also require, python-gst ( >> python-gst_0.10.10.bb which is also present in the /recipes/python >> folder, how will he build that also. RRECOMMENDS can only recommend a >> package right? Is it possible that it will get build. >> >> Context of my question: Right now we have clutter, clutter-gtk, >> clutter-gst etc to build. Is there a case where all are build at the same >> time. Not rushing into it. Just curious to know how to build interested >> recipes which comes inside the same folder. Otherwise why would the module >> be split into different packages ( like for python : it has got split into >> many packages. Initially I confused this with each recipe inside the same >> folder(eg /recipes/python/) resulting in a package ! >> >> Thanks a lot for your time! >> Regards, >> Vidya. >> >> >> >> >> On Tue, Jul 13, 2010 at 3:03 PM, Andreas Mueller <sch...@gm...>wrote: >> >>> On Tuesday 13 July 2010 10:24:19 pm Vidya Menon wrote: >>> > I am trying to add more .bb to this set. But I have couple of doubts. >>> After >>> > I run the clutter-1.2.10 bitbake, I dont have a >>> > >>> /overo-oe/tmp/work/overo-angstrom-linux-gnueabi/clutter-1.2.10-r2.0/install >>> > directory and its not getting packaged. I see the default functions >>> being >>> > executed. >>> >>> see: >>> http://docs.openembedded.org/usermanual/usermanual.html#usage_tasks >>> >>> http://docs.openembedded.org/usermanual/usermanual.html#directories_installation >>> >>> > Also, say I have mulitple .bb files inside the clutter directory - >>> > clutter-gst.bb, pyclutter.bb etc. Does bitbake automatically execute >>> and >>> > install all of them? Say inside pyclutter.bb I can state DEPENDS = >>> > "clutter-1.2.10" , but how does pyclutter.bb get executed in the first >>> > place.I don't understand/see any explicit lines in clutter.inc ( in the >>> > clutter-0.9 from the repository) for doing this. >>> There are (at least) two possible things to build: >>> >>> - Images: All you need for a running system (bootloader/kernel/rootfs..) >>> is build by images. Prepared are found at <oe_base>/recipes/images. >>> - Single packages: If there is no preferred version set by the >>> distribution (for us <oe_base>/conf/distro/angstrom-2008.1.conf and the >>> files included by 'require') or the machine (for us >>> <oe_base>/conf/overo.conf and the files included by 'require') the file >>> name with the maximum version is build. >>> >>> see: >>> >>> http://docs.openembedded.org/usermanual/usermanual.html#recipes_versioning >>> >>> http://docs.openembedded.org/usermanual/usermanual.html#recipes_package_relationships >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by Sprint >>> What will you do first with EVO, the first 4G phone? >>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >> >> > |
From: Andreas M. <sch...@gm...> - 2010-07-14 08:59:40
|
On Wednesday 14 July 2010 05:28:44 am Vidya Menon wrote: > Update: > I think I got a probable answer. > If I run python-gst*.bb directly then it will build all the packages (using > the corresponding .bb) recursively specified in the DEPENDS field. Back-ward > dependency (ie building python-gst when we call for python) would just be an > overhead. Correct me if I am wrong. Sorry but I can't really follow fully but why should OE follow backward-dependency? > > Sorry, I am using the recipes that you had posted as my entry point. If you > > don't mind that. > > So the overo specific packages (.ipk) are installed into > > /overo-oe/tmp/deploy/glibc/ipk/overo/ > > and the packages are split into : > > libclutter-glx-1.0-0_1.2.10-r2.0.5_overo.ipk, > > libclutter-glx-1.0-dbg_1.2.10-r2.0.5_overo.ipk, > > libclutter-glx-1.0-dev_1.2.10-r2.0.5_overo.ipk, > > libclutter-glx-1.0-doc_1.2.10-r2.0.5_overo.ipk right? I didn't notice them > > before as I was looking for packages starting with clutter* . So just wanted > > to confirm that these are the packages in question. conformed. BTW: To get an idea what's inside check tmp/work/overo-angstrom-linux-gnueabi/overo-angstrom-linux-gnueabi/<package_name&version>/package-split for machine dependent packages (clutter is machine dependent due to gles) tmp/work/overo-angstrom-linux-gnueabiarmv7a-angstrom-linux-gnueabi/<package_name&version>/package-split for architecture dependent packages Andreas |
From: Andreas M. <sch...@gm...> - 2010-07-14 09:36:56
|
On Wednesday 14 July 2010 10:43:08 am Vidya Menon wrote: > Hi, > > I wrote a new recipe for clutter-gst to use the latest version. As you said, > it builds fine on forcing gl. > But I am facing some issues with the clutter-gst-video-sink.c for gles2. > > ./clutter-gst-video-sink.c: At top level: > | ./clutter-gst-video-sink.c:138: error: expected ')' before > 'GLUNIFORM1IPROC' > | ./clutter-gst-video-sink.c:140: error: expected ')' before > 'GLGENPROGRAMSPROC' > | ./clutter-gst-video-sink.c:141: error: expected ')' before > 'GLBINDPROGRAMPROC' > | ./clutter-gst-video-sink.c:142: error: expected ')' before > 'GLPROGRAMSTRINGPROC' > | ./clutter-gst-video-sink.c:147: error: expected specifier-qualifier-list > before 'GLGENPROGRAMSPROC' > > 'APIENTRYP' itself is not defined anywhere. Could that be the problem? Yes it is (one of) the problem(s). It is defined in tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/GL/gl.h (you need to bitbake mesa - but by forcing gl you should already have). I think our problem is that the GLES(2) support is still under development. As far as I know clutter is a project mainly supported by Intel: Their processors do support full gl. A hint on this are the latest commits in http://git.clutter-project.org/clutter/. I tried to build the latest cutter but it fails with 'GLES2/gl2ext.h: present but cannot be compiled' This file is coming from libgles-omap3. Right now I am checking why this does not compile with the latest version og TI driver stuff to save from effords in old packages. Sometimes I got the feeling if you open one door you will enter a room with ten doors closed... Andreas |
From: Vidya M. <vid...@gm...> - 2010-07-14 10:13:33
|
Looks a lot more complicated than I thought it would be. Thanks for the help! Vidya On Wed, Jul 14, 2010 at 2:29 AM, Andreas Mueller <sch...@gm...>wrote: > > > 'APIENTRYP' itself is not defined anywhere. Could that be the problem? > Yes it is (one of) the problem(s). It is defined in > tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/GL/gl.h (you need to > bitbake mesa - but by forcing gl you should already have). I think > our problem is that the GLES(2) support is still under development. As far > as I know clutter is a project mainly supported by Intel: Their processors > do support full gl. A hint on this are the latest > commits in http://git.clutter-project.org/clutter/. > > I tried to build the latest cutter but it fails with > > 'GLES2/gl2ext.h: present but cannot be compiled' > > This file is coming from libgles-omap3. Right now I am checking why this > does not compile with the latest version og TI driver stuff to save from > effords in old packages. > > Sometimes I got the feeling if you open one door you will enter a room with > ten doors closed... > > Andreas > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Vidya M. <vid...@gm...> - 2010-07-14 09:45:55
|
It was just a thought. For eg: after building clutter, clutter-gtk etc I realised that clutter-gst requires gst-plugins-base, which I hadn't installed. So I was wondering if I could specify which all .bb recipes to build when building gstreamer.Again, I wouldn't have know all what I needed anyway. And if the default option is to build all the recipes in the folder, it would have been a big overload. Thanks. I did check that out. Regards, Vidya. On Wed, Jul 14, 2010 at 1:52 AM, Andreas Mueller <sch...@gm...>wrote: > On Wednesday 14 July 2010 05:28:44 am Vidya Menon wrote: > > Update: > > I think I got a probable answer. > > If I run python-gst*.bb directly then it will build all the packages > (using > > the corresponding .bb) recursively specified in the DEPENDS field. > Back-ward > > dependency (ie building python-gst when we call for python) would just be > an > > overhead. Correct me if I am wrong. > > Sorry but I can't really follow fully but why should OE follow > backward-dependency? > > > > Sorry, I am using the recipes that you had posted as my entry point. If > you > > > don't mind that. > > > So the overo specific packages (.ipk) are installed into > > > /overo-oe/tmp/deploy/glibc/ipk/overo/ > > > and the packages are split into : > > > libclutter-glx-1.0-0_1.2.10-r2.0.5_overo.ipk, > > > libclutter-glx-1.0-dbg_1.2.10-r2.0.5_overo.ipk, > > > libclutter-glx-1.0-dev_1.2.10-r2.0.5_overo.ipk, > > > libclutter-glx-1.0-doc_1.2.10-r2.0.5_overo.ipk right? I didn't notice > them > > > before as I was looking for packages starting with clutter* . So just > wanted > > > to confirm that these are the packages in question. > conformed. > > BTW: To get an idea what's inside check > tmp/work/overo-angstrom-linux-gnueabi/overo-angstrom-linux-gnueabi/<package_name&version>/package-split > for machine dependent packages (clutter is machine dependent due to gles) > tmp/work/overo-angstrom-linux-gnueabiarmv7a-angstrom-linux-gnueabi/<package_name&version>/package-split > for architecture dependent packages > > Andreas > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Andreas M. <sch...@gm...> - 2010-07-14 09:59:32
|
On Wednesday 14 July 2010 11:45:46 am Vidya Menon wrote: > It was just a thought. > For eg: after building clutter, clutter-gtk etc I realised that clutter-gst > requires gst-plugins-base, which I hadn't installed. So I was wondering if I > could specify which all .bb recipes to build when building gstreamer.Again, > I wouldn't have know all what I needed anyway. And if the default option is > to build all the recipes in the folder, it would have been a big overload. How about creating an image, based on (=require) omap3-console-image, build that and let OE decide what you need? Andreas |