On Tue, 22 Dec 2015 11:45:33 +0100 Simon Ruetzler <[email protected]> wrote:
> Hello, > the demo package is the first package. I clear the list with PACKAGES = "" > They package should contain this files, this is not the problem. > The problem is the resulting package name. The name should be > rumo-cpp-demo-1.0rc... and not libscom1-1.0-rc... > Regards Simon How about creating a separate recipe rumo-cpp-demo which depends on libscom? Why exactly prompts you to create rumo-cpp-demo from inside the libscom recipe? Aren't these two different software packages altogether? > > Am 22.12.2015 um 11:38 schrieb Ioan-Adrian Ratiu: > > Hi > > > > On Tue, 22 Dec 2015 10:40:18 +0100 > > Simon Ruetzler <[email protected]> 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? > > Maybe the contents of ${PN}-demo get gobbled up by another package defined > > before it in PACKAGES? The order of the contents of var PACKAGES matters: > > it defines precedence, the first package to match a file includes it. > > > > Try prepending to PACKAGES, something like this: > > PACKAGES =+ "${PN}-demo " > > > >> Regards Simon > > > -- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
