Creating library

Creating library

[Keskinarkaus, Teemu]

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

Hi,

Hopefully this is the correct mailing list.

I'm using Yocto/Poky to create Linux distribution and so far everything has gone rather smoothly, but now I have come up to a problem that I cannot seem to be able to fix.

I'm adding existing old software to Yocto/Poky and they don't use autotools so there is ready made Makefile that does everything.

Problem comes with the library that is compiled that way too. Makefile has targets 'all' and 'install' that does the compilation and installation. Library compiles ok and installs ok too under -build directory, but when bitbake creates the deb-packages it creates only library-dev.deb, library-dbg.deb and library-staticdev.deb. The package library.deb does not get created and that causes build to fail. I looked the logs and bitbake says that NOTE: not creating empty library.deb - package. or something like that.

I've tried anything that comes to my mind and also searched documentation and google and looked other libraries that are in yocto/poky, but just cannot get that work. I've also tried add FILES_${PN} to the recipe to force the files in the library.deb package, but that didn't help.  Makefile installs the files to DESTDIR and files are installed just fine in the temporary image that is created under build-directory.

For some reason, maybe because lack of autotools, I had to set S and B dir to point to the dir where library sources are. Would that be causing the problems even though the library gets installed to image in build-directory?

Library.deb isn't the actual name, but just an example.

I wouldn't want to convert all the software to use autotools since there are quite many of them and they are used in other projects as well so it would be rather big task. Any idea how to get that library thing to work?

I have few kernel modules where I also had to set S and B to point the dir where the kernel module sources are, but in those cases there were no problems. Only the library gives me hard time.

-Teemu Keskinarkaus

________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

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

Re: Creating library

[Gary Thomas]

On 2013-06-19 04:45, Keskinarkaus, Teemu wrote:
> Hi,
>
> Hopefully this is the correct mailing list.
>
> I’m using Yocto/Poky to create Linux distribution and so far everything has gone rather smoothly, but now I have come up to a problem that I cannot seem to be able to fix.
>
> I’m adding existing old software to Yocto/Poky and they don’t use autotools so there is ready made Makefile that does everything.
>
> Problem comes with the library that is compiled that way too. Makefile has targets ‘all’ and ‘install’ that does the compilation and installation. Library compiles ok and installs
> ok too under –build directory, but when bitbake creates the deb-packages it creates only library-dev.deb, library-dbg.deb and library-staticdev.deb. The package library.deb does
> not get created and that causes build to fail. I looked the logs and bitbake says that NOTE: not creating empty library.deb – package. or something like that.
>
> I’ve tried anything that comes to my mind and also searched documentation and google and looked other libraries that are in yocto/poky, but just cannot get that work. I’ve also
> tried add FILES_${PN} to the recipe to force the files in the library.deb package, but that didn’t help.  Makefile installs the files to DESTDIR and files are installed just fine
> in the temporary image that is created under build-directory.
>
> For some reason, maybe because lack of autotools, I had to set S and B dir to point to the dir where library sources are. Would that be causing the problems even though the library
> gets installed to image in build-directory?
>
> Library.deb isn’t the actual name, but just an example.
>
> I wouldn’t want to convert all the software to use autotools since there are quite many of them and they are used in other projects as well so it would be rather big task. Any idea
> how to get that library thing to work?

See if this helps; tell bitbake to allow empty packages like this:
   ALLOW_EMPTY_${PN} = "1"
Put this line in your recipe and you should be able to move forward.

>
> I have few kernel modules where I also had to set S and B to point the dir where the kernel module sources are, but in those cases there were no problems. Only the library gives me
> hard time.
>
> -Teemu Keskinarkaus

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

Re: Creating library

[Keskinarkaus, Teemu]

Hi,

That helped a little. Now the build process didn't end with an error, but the image itself doesn't have the library. I think the deb-package is used to install stuff to the actual image that is being generated and not the directory that is under build-directory.

So, real fix would be figure out somehow how to get the library.deb to be generated properly instead just those those dev/dbg-packages.

I tried looking for example under poky, but majority, if not all, of them use autotools so they are not that much help.

-Teemu Keskinarkaus

-----Original Message-----
From: poky-bounces@yoctoproject.org [mailto:poky-bounces@yoctoproject.org] On Behalf Of Gary Thomas
Sent: 19. kesäkuuta 2013 7:34
To: poky@yoctoproject.org
Subject: Re: [poky] Creating library

On 2013-06-19 04:45, Keskinarkaus, Teemu wrote:
> Hi,
>
> Hopefully this is the correct mailing list.
>
> I'm using Yocto/Poky to create Linux distribution and so far everything has gone rather smoothly, but now I have come up to a problem that I cannot seem to be able to fix.
>
> I'm adding existing old software to Yocto/Poky and they don't use autotools so there is ready made Makefile that does everything.
>
> Problem comes with the library that is compiled that way too. Makefile
> has targets 'all' and 'install' that does the compilation and
> installation. Library compiles ok and installs ok too under -build directory, but when bitbake creates the deb-packages it creates only library-dev.deb, library-dbg.deb and library-staticdev.deb. The package library.deb does not get created and that causes build to fail. I looked the logs and bitbake says that NOTE: not creating empty library.deb - package. or something like that.
>
> I've tried anything that comes to my mind and also searched
> documentation and google and looked other libraries that are in
> yocto/poky, but just cannot get that work. I've also tried add FILES_${PN} to the recipe to force the files in the library.deb package, but that didn't help.  Makefile installs the files to DESTDIR and files are installed just fine in the temporary image that is created under build-directory.
>
> For some reason, maybe because lack of autotools, I had to set S and B
> dir to point to the dir where library sources are. Would that be causing the problems even though the library gets installed to image in build-directory?
>
> Library.deb isn't the actual name, but just an example.
>
> I wouldn't want to convert all the software to use autotools since
> there are quite many of them and they are used in other projects as well so it would be rather big task. Any idea how to get that library thing to work?

See if this helps; tell bitbake to allow empty packages like this:
   ALLOW_EMPTY_${PN} = "1"
Put this line in your recipe and you should be able to move forward.

>
> I have few kernel modules where I also had to set S and B to point the
> dir where the kernel module sources are, but in those cases there were no problems. Only the library gives me hard time.
>
> -Teemu Keskinarkaus

--
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
_______________________________________________
poky mailing list
poky@yoctoproject.org
https://lists.yoctoproject.org/listinfo/poky

________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

Re: Creating library

[Richard Purdie]

On Wed, 2013-06-19 at 05:56 +0000, Keskinarkaus, Teemu wrote:
> That helped a little. Now the build process didn't end with an error,
> but the image itself doesn't have the library. I think the deb-package
> is used to install stuff to the actual image that is being generated
> and not the directory that is under build-directory.
> 
> So, real fix would be figure out somehow how to get the library.deb to
> be generated properly instead just those those dev/dbg-packages.
> 
> I tried looking for example under poky, but majority, if not all, of
> them use autotools so they are not that much help.

It sounds like you need a FILES_${PN} += "/place/of/lib/files" type of
expression to show the system which files to install into the main
package.

I'm guessing but perhaps the libs you generate are xxxx.so files and
this is confusing the system? Usually libs are versioned and the x.so is
placed into the -dev package so you'll have to change the default FILES
variables if you do have something which is unversioned.

More information about the names of the files that aren't getting
matched would make it easier to help you. Did they get installed into
the -dev package?

Cheers,

Richard

Re: Creating library

[Keskinarkaus, Teemu]

Sorry for top post, but this outlook is horrible.

It seemed that those missing library.1.0.so, library.1.so etc.. links were the key. By adding them the library.deb - package got made correctly and library installed to image just fine.

Thanks!

-Teemu

-----Original Message-----
From: Richard Purdie [mailto:richard.purdie@linuxfoundation.org]
Sent: 19. kesäkuuta 2013 11:08
To: Keskinarkaus, Teemu
Cc: poky@yoctoproject.org
Subject: Re: [poky] Creating library

On Wed, 2013-06-19 at 05:56 +0000, Keskinarkaus, Teemu wrote:
> That helped a little. Now the build process didn't end with an error,
> but the image itself doesn't have the library. I think the deb-package
> is used to install stuff to the actual image that is being generated
> and not the directory that is under build-directory.
>
> So, real fix would be figure out somehow how to get the library.deb to
> be generated properly instead just those those dev/dbg-packages.
>
> I tried looking for example under poky, but majority, if not all, of
> them use autotools so they are not that much help.

It sounds like you need a FILES_${PN} += "/place/of/lib/files" type of expression to show the system which files to install into the main package.

I'm guessing but perhaps the libs you generate are xxxx.so files and this is confusing the system? Usually libs are versioned and the x.so is placed into the -dev package so you'll have to change the default FILES variables if you do have something which is unversioned.

More information about the names of the files that aren't getting matched would make it easier to help you. Did they get installed into the -dev package?

Cheers,

Richard


________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

Creating library

[Keskinarkaus, Teemu]

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

Hi,

Hopefully this is the correct mailing list.

I'm using Yocto/Poky to create Linux distribution and so far everything has gone rather smoothly, but now I have come up to a problem that I cannot seem to be able to fix.

I'm adding existing old software to Yocto/Poky and they don't use autotools so there is ready made Makefile that does everything.

Problem comes with the library that is compiled that way too. Makefile has targets all and install that does the compilation and installation. Library compiles ok and installs ok too under -build directory, but when bitbake creates the deb-packages it creates only library-dev.deb, library-dbg.deb and library-staticdev.deb. The package library.deb does not get created and that causes build to fail. I looked the logs and bitbake says that NOTE: not creating empty library.deb - package. or something like that.

I've tried anything that comes to my mind and also searched documentation and google and looked other libraries that are in yocto/poky, but just cannot get that work. I've also tried add FILES_${PN} to the recipe to force the files in the library.deb package, but that didn't help.  Makefile installs the files to DESTDIR.

For some reason, maybe because lack of autotools, I had to set S and B dir to point to the dir where library sources are. Would that be causing the problems even though the library gets installed to image in build-directory?

Library.deb isn't the actual name, but just an example.

I wouldn't want to convert all the software to use autotools since there are quite many of them and they are used in other projects as well so it would be rather big task. Any idea how to get that library thing to work?

I have few kernel modules where I also had to set S and B to point the dir where the kernel module sources are, but in those cases there were no problems. Only the library gives me hard time.

-Teemu Keskinarkaus


________________________________

Actuant Corporation Email Notice

This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and/or CONFIDENTIAL.
This email is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this email is not an intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited.
If you have received this email in error, please notify the sender immediately by return mail and permanently delete the copy you received.

Thank you.

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