> On Aug 7, 2015, at 2:25 AM, yocto yocto <yoctomailingl...@gmail.com> wrote: > > I added the meta-openembedded layer to my configuration. I want to have > libmcrypt (in meta-openembedded/meta-oe/recipes-support) on my system: > > IMAGE_INSTALL += "libmcrypt" > > The library (libmcrypt.so) is actually being built. Everything is located in > "libmcrypt/2.5.8-r0/package/usr", however after flashing the image libmcrypt > is not part of the filesystem. >
build system has preset rules for shared libraries that follow the versioning
scheme, in that scheme foo.so is a symlink to real shared object which is
something like foo.x.y.z or something like that. then packager goes in and
bundles the .so into -dev ipk and real shared object into proper ipk and all
works. So is this library using versioning ? if not you have to jump through
some hoops to let system know about that so it stats treating .so as final
shared object and not as symlink.
> I tried writing some kind of "libmcrypt_%.bbappend" with
>
> do_install() {
> install -m 0755 ${WORKDIR}/package/usr ${D}/
> }
you need to specify filenames or wildchars something like
${WORKDIR}/package/usr/bin/mybinary or something like that look at manpage of
install utility for more insights
>
> However, I get a bitbake error that do_install failed but there is exact
> message. Any ideas how to solve this properly?
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
