All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Keskinarkaus, Teemu" <Teemu.Keskinarkaus@Maximatecc.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: Creating library
Date: Wed, 19 Jun 2013 09:07:41 +0100	[thread overview]
Message-ID: <1371629261.20823.158.camel@ted> (raw)
In-Reply-To: <83DB4EC8FADD45428E3CC4E3664761FD015B23F8@AMDTCEX12.actuant.pri>

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



  reply	other threads:[~2013-06-19  8:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19  3:45 Creating library Keskinarkaus, Teemu
2013-06-19  4:33 ` Gary Thomas
2013-06-19  5:56   ` Keskinarkaus, Teemu
2013-06-19  8:07     ` Richard Purdie [this message]
2013-06-20  7:45       ` Keskinarkaus, Teemu
  -- strict thread matches above, loose matches on Subject: below --
2013-06-18 10:30 Keskinarkaus, Teemu

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=1371629261.20823.158.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Teemu.Keskinarkaus@Maximatecc.com \
    --cc=poky@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.