What is the best practice for customizing libraries included in yocto distribution?

What is the best practice for customizing libraries included in yocto distribution?

[Federico Vitali]

[-- Attachment #1: Type: text/plain, Size: 514 bytes --]

Hi everyone,

what should I do to customize and crosscompile a library already
distributed with yocto?


I see 2 possibilities:

1. Build and install a toolchain and sysrootfs on local host and untar the
original library,
   apply yocto distributed patches and then cross compile ==> I'm having
trouble here

2. Use the yocto build environment itself, but I don't like this option.

Does anyone have already customized a library?

Any help will be appreciated

Thank you in advance

Federico

[-- Attachment #2: Type: text/html, Size: 763 bytes --]

Re: What is the best practice for customizing libraries included in yocto distribution?

[Nicolas Dechesne]

Hi,

On Thu, Mar 13, 2014 at 4:52 PM, Federico Vitali <fede.vitali@gmail.com> wrote:
> Hi everyone,
>
> what should I do to customize and crosscompile a library already distributed
> with yocto?
>

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 see 2 possibilities:
>
> 1. Build and install a toolchain and sysrootfs on local host and untar the
> original library,
>    apply yocto distributed patches and then cross compile ==> I'm having
> trouble here

telling us more about the trouble might be useful. also telling how
you build the toolchain and sysrootfs.

>
> 2. Use the yocto build environment itself, but I don't like this option.

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?

>
> Does anyone have already customized a library?

Re: What is the best practice for customizing libraries included in yocto distribution?

[Federico Vitali]

[-- Attachment #1: Type: text/plain, Size: 3824 bytes --]

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
libtool: link: warning: library
`/opt/poky/1.5.1/sysroots/armv6-vfp-poky-linux-gnueabi/usr/lib/
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' was moved.
libtool: link: warning: library
`/opt/poky/1.5.1/sysroots/armv6-vfp-poky-linux-gnueabi/usr/lib/
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' was moved.
libtool: link: warning: library
`/opt/poky/1.5.1/sysroots/armv6-vfp-poky-linux-gnueabi/usr/lib/
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' was moved.
libtool: link: warning: library
`/opt/poky/1.5.1/sysroots/armv6-vfp-poky-linux-gnueabi/usr/lib/libxml2.la'
was moved.
sed: can't read /usr/lib/libgstreamer-0.10.la: No such file or directory
libtool: link: `=/usr/lib/libgstreamer-0.10.la' is not a valid libtool
archive
make[4]: *** [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!

[-- Attachment #2: Type: text/html, Size: 5723 bytes --]

Re: What is the best practice for customizing libraries included in yocto distribution?

[Gary Thomas]

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
------------------------------------------------------------

Re: What is the best practice for customizing libraries included in yocto distribution?

[Nicolas Dechesne]

On Fri, Mar 14, 2014 at 10:10 AM, Gary Thomas <gary@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

Re: What is the best practice for customizing libraries included in yocto distribution?

[Federico Vitali]

[-- Attachment #1: Type: text/plain, Size: 2987 bytes --]

Thank you Nicholas and Gary! I'm quite experienced in linux embedded
developement, but I'm new to yocto / openembedded.
Nicolas, can you please explain me how to use my sources separate from OE
build dir tree and still using oe built system?
Do I have to edit the sources directly in builddir/tmp/work/etcetera or can
I keep it separate?




2014-03-14 10:24 GMT+01:00 Nicolas Dechesne <nicolas.dechesne@linaro.org>:

> On Fri, Mar 14, 2014 at 10:10 AM, Gary Thomas <gary@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
>

[-- Attachment #2: Type: text/html, Size: 5102 bytes --]

Re: What is the best practice for customizing libraries included in yocto distribution?

[Nicolas Dechesne]

Frederico,

On Fri, Mar 14, 2014 at 11:09 AM, Federico Vitali <fede.vitali@gmail.com> wrote:
> Thank you Nicholas and Gary! I'm quite experienced in linux embedded
> developement, but I'm new to yocto / openembedded.
> Nicolas, can you please explain me how to use my sources separate from OE
> build dir tree and still using oe built system?
> Do I have to edit the sources directly in builddir/tmp/work/etcetera or can
> I keep it separate?

Please have a look at

http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-classes-externalsrc
http://www.yoctoproject.org/docs/1.5.1/dev-manual/dev-manual.html#building-software-from-an-external-source

let us know if you have additional questions

Re: What is the best practice for customizing libraries included in yocto distribution?

[Federico Vitali]

[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]

Thank you Nicolas. Sorry, but I'm new to this extremely powerful building
system, I'm a little confused. Now I'll read the sections you suggest!
Thank you again!

Federico
Il giorno 14/mar/2014 11:18, "Nicolas Dechesne" <nicolas.dechesne@linaro.org>
ha scritto:

> Frederico,
>
> On Fri, Mar 14, 2014 at 11:09 AM, Federico Vitali <fede.vitali@gmail.com>
> wrote:
> > Thank you Nicholas and Gary! I'm quite experienced in linux embedded
> > developement, but I'm new to yocto / openembedded.
> > Nicolas, can you please explain me how to use my sources separate from OE
> > build dir tree and still using oe built system?
> > Do I have to edit the sources directly in builddir/tmp/work/etcetera or
> can
> > I keep it separate?
>
> Please have a look at
>
>
> http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-classes-externalsrc
>
> http://www.yoctoproject.org/docs/1.5.1/dev-manual/dev-manual.html#building-software-from-an-external-source
>
> let us know if you have additional questions
>

[-- Attachment #2: Type: text/html, Size: 1664 bytes --]

Re: What is the best practice for customizing libraries included in yocto distribution?

[Federico Vitali]

[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]

It worked! Thank you so much! Now I have to go out, I have only to
understand
a couple of things...

1. how to make bitbake understand that I've only changed one or more file,
now I have
to do bitbake -c clean gst-plugins-base && bitbake gst-plugins-base

2. how to debug via Eclipse.

Thank you again!


Federico



2014-03-14 11:18 GMT+01:00 Nicolas Dechesne <nicolas.dechesne@linaro.org>:

> Frederico,
>
> On Fri, Mar 14, 2014 at 11:09 AM, Federico Vitali <fede.vitali@gmail.com>
> wrote:
> > Thank you Nicholas and Gary! I'm quite experienced in linux embedded
> > developement, but I'm new to yocto / openembedded.
> > Nicolas, can you please explain me how to use my sources separate from OE
> > build dir tree and still using oe built system?
> > Do I have to edit the sources directly in builddir/tmp/work/etcetera or
> can
> > I keep it separate?
>
> Please have a look at
>
>
> http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-classes-externalsrc
>
> http://www.yoctoproject.org/docs/1.5.1/dev-manual/dev-manual.html#building-software-from-an-external-source
>
> let us know if you have additional questions
>

[-- Attachment #2: Type: text/html, Size: 2010 bytes --]

Re: What is the best practice for customizing libraries included in yocto distribution?

[Gary Thomas]

On 2014-03-14 09:45, Federico Vitali wrote:
> It worked! Thank you so much! Now I have to go out, I have only to understand
> a couple of things...
> 
> 1. how to make bitbake understand that I've only changed one or more file, now I have
> to do bitbake -c clean gst-plugins-base && bitbake gst-plugins-base

If you've only changed a file or two, try this instead:
  $ bitbake gst-plugins-base -C compile

If you made a change that requires rerunning the 'configure' step,
just use that instead of 'compile'.

> 2. how to debug via Eclipse.
> 
> Thank you again!
> 
> 
> Federico
> 
> 
> 
> 2014-03-14 11:18 GMT+01:00 Nicolas Dechesne <nicolas.dechesne@linaro.org <mailto:nicolas.dechesne@linaro.org>>:
> 
>     Frederico,
> 
>     On Fri, Mar 14, 2014 at 11:09 AM, Federico Vitali <fede.vitali@gmail.com <mailto:fede.vitali@gmail.com>> wrote:
>     > Thank you Nicholas and Gary! I'm quite experienced in linux embedded
>     > developement, but I'm new to yocto / openembedded.
>     > Nicolas, can you please explain me how to use my sources separate from OE
>     > build dir tree and still using oe built system?
>     > Do I have to edit the sources directly in builddir/tmp/work/etcetera or can
>     > I keep it separate?
> 
>     Please have a look at
> 
>     http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-classes-externalsrc
>     http://www.yoctoproject.org/docs/1.5.1/dev-manual/dev-manual.html#building-software-from-an-external-source
> 
>     let us know if you have additional questions
> 
> 

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------