On Fri, Mar 14, 2014 at 10:10 AM, Gary Thomas <g...@mlbassoc.com> wrote: >> CCLD libgsttag-0.10.la <http://libgsttag-0.10.la> >> libtool: link: warning: library >> `/opt/poky/1.5.1/sysroots/armv6-vfp-poky-linux-gnueabi/usr/lib/libgstbase-0.10.la >> <http://libgstbase-0.10.la>' was moved. >> libtool: link: warning: library >> `/opt/poky/1.5.1/sysroots/armv6-vfp-poky-linux-gnueabi/usr/lib/libgstreamer-0.10.la >> <http://libgstreamer-0.10.la>' was moved. >> libtool: link: warning: library >> `/opt/poky/1.5.1/sysroots/armv6-vfp-poky-linux-gnueabi/usr/lib/libgobject-2.0.la >> <http://libgobject-2.0.la>' was moved. >> libtool: link: warning: library >> `/opt/poky/1.5.1/sysroots/armv6-vfp-poky-linux-gnueabi/usr/lib/libgmodule-2.0.la >> <http://libgmodule-2.0.la>' was moved. >> libtool: link: warning: library >> `/opt/poky/1.5.1/sysroots/armv6-vfp-poky-linux-gnueabi/usr/lib/libgthread-2.0.la >> <http://libgthread-2.0.la>' was moved. >> libtool: link: warning: library >> `/opt/poky/1.5.1/sysroots/armv6-vfp-poky-linux-gnueabi/usr/lib/libglib-2.0.la >> <http://libglib-2.0.la>' was moved. >> libtool: link: warning: library >> `/opt/poky/1.5.1/sysroots/armv6-vfp-poky-linux-gnueabi/usr/lib/libxml2.la >> <http://libxml2.la>' was moved. >> sed: can't read /usr/lib/libgstreamer-0.10.la <http://libgstreamer-0.10.la>: >> No such file or directory >> libtool: link: `=/usr/lib/libgstreamer-0.10.la >> <http://libgstreamer-0.10.la>' is not a valid libtool archive >> make[4]: *** [libgsttag-0.10.la <http://libgsttag-0.10.la>] Errore 1 >> >> The library configured for cross compilation. I'm starting from the sources >> patched as in yocto. >> >> Any help appreciated! > > Why not do these changes/development using your bitbake/Yocto > build environment. I've found that using quilt makes this quite > easy to do and helps manage the changes, patches, etc. It will > also avoid the problem you are having which seems to stem from > trying to build outside the original environment.
yeah. i would recommend that too. I find the externalsrc class quite handy for such things. E.g. you can keep your git tree separate during development, *but* still rely on OE to build, which I think gives you the best of both world... of course for your own applications, using the SDK makes sense. nicolas -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
