From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: What is the best practice for customizing libraries included in yocto distribution?
Date: Fri, 14 Mar 2014 03:10:09 -0600 [thread overview]
Message-ID: <5322C771.8070601@mlbassoc.com> (raw)
In-Reply-To: <CAD78y+4tJLHEGAd6NZ-S=XU7j_J9=-pFb5vYRxF7gZb52Qkq-Q@mail.gmail.com>
On 2014-03-14 03:04, Federico Vitali wrote:
> Thank you Nicolas.
> I try to explain better, sorry, yesterday I wrote the email in a hurry.
>
> I'm working to build an OS based on sato, but I have to modify the code
> of some libraries included in the distribution. When I wrote "customize"
> I meant modify source code.
>
> I answer to your questions:
>
>
> can you be a bit more specific? not sure i understand completely what
> you want to do. also how are you getting your distribution?
> it's
> prebuilt and you only have the image or you build it yourself from
> recipes?
>
>
> I'm basing my distribution on sato-sdk. I've built it from source. I've built and
> installed a cross toolchain and root filesystem to use for building. I'm developing applications
> using the cross toolchain, adt tools and Eclipse. It is all set up properly.
>
>
>
> telling us more about the trouble might be useful. also telling how
> you build the toolchain and sysrootfs.
>
>
> I have to modify some source code of some gstreamer plugins to support
> some custom functionalities. During the developement I would like to
> work outside bitbake to develop / compile / debug on the target. I know
> that when I've finished I can simply add my patch to a bb append file of
> my own, and when the developement will be finished I will certainly do.
>
>
>
>
> well, that would definitely be the more natural way of customizing
> existing recipes. that's what most people would do in their own
> layers, generally with .bbappend recipes. it's probably even easier to
> do that building your own toolchain/SDK to some extends.. why don't
> you like this option?
>
>
>
> I certainly use this option when I customize existing recipes! My problem
> is in developement phase.
>
>
> This is the specific problem I get when I try to build gst-plugins-base:
>
> ake[4]: ingresso nella directory "/home/vitalife/sources/gst-plugins-base-0.10.36/gst-libs/gst/tag"
> CC libgsttag_0.10_la-gstvorbistag.lo
> CC libgsttag_0.10_la-gstid3tag.lo
> CC libgsttag_0.10_la-gstxmptag.lo
> gstxmptag.c: In function 'xmp_tag_type_get_name':
> gstxmptag.c:178:1: warning: control reaches end of non-void function [-Wreturn-type]
> }
> ^
> CC libgsttag_0.10_la-gstexiftag.lo
> CC libgsttag_0.10_la-lang.lo
> CC libgsttag_0.10_la-licenses.lo
> CC libgsttag_0.10_la-tags.lo
> CC libgsttag_0.10_la-gsttagdemux.lo
> CC libgsttag_0.10_la-gsttagmux.lo
> CC libgsttag_0.10_la-gsttageditingprivate.lo
> CC libgsttag_0.10_la-id3v2.lo
> CC libgsttag_0.10_la-id3v2frames.lo
> CC libgsttag_0.10_la-xmpwriter.lo
> 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.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-03-14 9:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 15:52 What is the best practice for customizing libraries included in yocto distribution? Federico Vitali
2014-03-14 8:35 ` Nicolas Dechesne
2014-03-14 9:04 ` Federico Vitali
2014-03-14 9:10 ` Gary Thomas [this message]
2014-03-14 9:24 ` Nicolas Dechesne
2014-03-14 10:09 ` Federico Vitali
2014-03-14 10:18 ` Nicolas Dechesne
2014-03-14 10:50 ` Federico Vitali
2014-03-14 15:45 ` Federico Vitali
2014-03-14 15:52 ` Gary Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5322C771.8070601@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.