From: Alejandro del Castillo <alejandro.delcastillo@ni.com>
To: <yocto@yoctoproject.org>
Subject: Re: yocto package naming
Date: Wed, 6 Jan 2016 15:21:12 -0600 [thread overview]
Message-ID: <568D8548.9010006@ni.com> (raw)
In-Reply-To: <56791A82.7050809@arigo-software.de>
On 12/22/2015 03:40 AM, Simon Ruetzler wrote:
> Hello,
> I want to create different packages from one recipe.
>
> This is working except for one package.
> I addes this package with
> PACKAGES += " ${PN}-demo"
> and I expected that it is named with the recipe name and demo. In this case
> rumo-cpp-demo-1.0-rc...
> But the name is libscom1-1.0-rc..
>
> The demo package contains the files for a dynamic library: libscom.so,
> libscom.so.1 and libscom.so.1.5.0
> and this library name is automatically used for the package name.
>
> For the other packages the name are as expected. All package are defined in the
> same way except that FILES_.. definition is different.
> This packages also have dynamic libs but only the libname.so.1 files and the
> libname.so as a link.
>
> Why is the demo package created with the libscom name? How can I disable this?
>
> Regards Simon
I believe setting DEBIAN_NOAUTONAME_${PN}-demo = "1" should do it.
--
Cheers,
Alejandro
prev parent reply other threads:[~2016-01-06 21:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 9:40 yocto package naming Simon Ruetzler
2015-12-22 10:38 ` Ioan-Adrian Ratiu
2015-12-22 10:45 ` Simon Ruetzler
2015-12-22 11:03 ` Ioan-Adrian Ratiu
2015-12-22 12:50 ` Simon Ruetzler
2015-12-22 11:12 ` Burton, Ross
2015-12-22 12:03 ` Simon Ruetzler
2015-12-22 12:18 ` Burton, Ross
2016-01-06 21:21 ` Alejandro del Castillo [this message]
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=568D8548.9010006@ni.com \
--to=alejandro.delcastillo@ni.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.