On Wed, Dec 4, 2013 at 3:29 PM, Brian Hutchinson <[email protected]>wrote:
> On Wed, Dec 4, 2013 at 5:10 PM, Chris Larson <[email protected]> wrote: > >> >> do_install is the task that installs. If your makefile has an install >> target, you’d define a do_install that runs it. But not all makefiles >> provide an equivalent to automake’s DESTDIR, which is why we don’t provide >> a do_install for non-autotools make-based buildsystems. Either manually >> install the library where it belongs in your do_install, e.g. with the >> ‘install’ or ‘cp’ commands, or define one which runs the appropriate make >> command to install the files into ${D}. >> -- >> >> Thanks Chris. > > I do have a do_install that is copying stuff to ${D}/usr/lib which puts > things in my sysroot ... but what target do I use to get stuff into the > package which is used by my IMAGE_INSTALL line? When I tar tvf my > core-image.tar and grep for my .so it currently isn't there ... but it and > the headers are in the sysroot. > do_install. The contents of ${D} are where the FILES globs are matched. We don’t include the raw libfoo.so, since that’s supposed to be a symlink. If your lib is missing an SONAME, it’d be named incorrectly and be missing a symlink, and the lib would end up in the -dev package instead of the main package. -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics
_______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
