All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick <kpa_info@yahoo.fr>
To: poky@yoctoproject.org
Subject: Re: Include already exisiting rpm or .spec
Date: Thu, 24 May 2012 11:22:41 +0200	[thread overview]
Message-ID: <4FBDFDE1.3050505@yahoo.fr> (raw)
In-Reply-To: <4F982FA9.8010909@windriver.com>

Hello all,

We have tried to add one of our package called 
test_libs-v27_v30-1.armv7a.rpm into tmp/deploy/rpm/armv7a directory.

Then in our image receipes we have added test_libs in  IMAGE_INSTALL.

The when we bitbake our image we have the following error message:

Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'test_libs' (but 
/home/yocto/poky-denzil-7.0/meta-test/recipes-extended/images/test-image.bb 
RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'test_libs' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['test_libs']
ERROR: Required build target 'test-image' has no buildable providers.
Missing or unbuildable dependency chain was: ['test-image', 'test_libs']

Thanks for any help !

Patrick


On 04/25/2012 07:08 PM, Mark Hatle wrote:
> On 4/25/12 10:56 AM, Patrick wrote:
>> Dear all,
>>
>> We have some software that we develop from a while that we release as
>> rpm. To build these rpm we have some complexe .spec files.
>>
>> Now we use Yocto/Poky to build many new elements and I would like to
>> include in my rootfs generated with Yocto/Poky some of our "old"
>> software. We don't want to manage the bitbake recipes and the .spec for
>> each of our "old" software.
>>
>> I then would like to know if I could made a simple bitbake recipes that
>> "call/include/use" the .specs files ?
>> Another solution would be to include directly the rpm to the final
>> image. Do you think that it's possible ?
>
> This is something that we have discussed, but nobody has implement it yet.
>
> It is best for long term maintenance to transfer the spec file items
> into recipe format... but if you don't want to do that you can copy your
> built binary RPM packages into the deploy/RPMS/<arch> directory and then
> add the package names to install into IMAGE_INSTALL (from memory).
>
> --Mark
>
>> Thanks in advance for idea or hint
>>
>> Patrick
>> _______________________________________________
>> poky mailing list
>> poky@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky



  reply	other threads:[~2012-05-24  9:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-25 15:56 Include already exisiting rpm or .spec Patrick
2012-04-25 17:08 ` Mark Hatle
2012-05-24  9:22   ` Patrick [this message]
2012-05-25 12:03     ` Patrick
2012-05-25 18:14       ` Robert Abel

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=4FBDFDE1.3050505@yahoo.fr \
    --to=kpa_info@yahoo.fr \
    --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.