No, libdir is /usr/lib on the target. We never write to the host system
outside the build directory. do_install installs a lib into ${D}${libdir},
and then the contents of ${D} get split up into individual binary packages,
and those packages are then installed in a root filesystem and archived
into a rootfs image.
On Thu, Apr 21, 2016 at 8:53 AM 杜 昊 <stephanie2...@hotmail.com> wrote:
> Hello there!
>
> I have a question about the absolute path of ${libdir}.
>
> for example in poco recipe:
>
>
> here is:
>
> PACKAGES += "${PN}-dev ${PN}-staticdev"
> FILES_${PN}-dev = "${includedir} ${libdir}/libPoco*.so ${libdir}/cmake"
> FILES_${PN}-staticdev = "${libdir}/libPoco*.a"
>
>
> i have searched for the yocto reference. In meta/conf/bitbake.conf we can
> see
>
>
> baselib = "${BASELIB}"
> BASELIB = "lib"
>
> # Path prefixes
> export exec_prefix = "/usr"
>
> # Architecture dependent paths
> export bindir = "${exec_prefix}/bin"
> export libdir = "${exec_prefix}/${baselib}"
>
> Does this mean that ${libdir} =/usr/lib in my host machine. But i
> can't find such libraries(libPoco*.so) in my host(ubuntu 14.04) under
> /usr/lib
> I think i misunderstand the absolute path of ${libdir}. Who can tell me
> the right meaning of this. Thanks for helping.
>
> regards
> hao du
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
