Bug 6511 - [Dev workflow] Document how to copy precompiled binaries to root image
Summary: [Dev workflow] Document how to copy precompiled binaries to root image
Status: RESOLVED FIXED
Alias: None
Product: General Docs
Classification: Documentation
Component: docs-general (show other bugs)
Version: 1.7
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.7 M3
Assignee: Scott Rifenbark
QA Contact:
URL:
Whiteboard: 05 Sept 2014: RESOLVED
Depends on:
Blocks:
 
Reported: 2014-07-08 10:11 UTC by Belen Barros Pena
Modified: 2014-09-05 08:33 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Done (doc changes complete)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Belen Barros Pena 2014-07-08 10:11:53 UTC
As part of development workflow documentation improvements. The source of it all is this thread in the YP mailing list:

https://lists.yoctoproject.org/pipermail/yocto/2014-July/020441.html
Comment 1 Scott Rifenbark 2014-07-10 13:39:41 UTC
So I have done some research on this to try and understand some stuff and have a couple questions:

 1. Aren't pre-compiled libraries (.so files) linked in at runtime? 
    So in describing this situation as "copying pre-compiled binaries to 
    the root image", is that just saying the same thing?  Are we wanting 
    to describe how to link these pre-compiled files to the image at 
    run-time?

 2. From the thread, which was responded to by a couple people, it looks
    like the simplest solution is to simply use 

      FILES_SOLIBSDEV = ""
      FILES_${PN} += "${libdir}/*.so"

    to get the .so files linked to (copied to?) the main package. As noted
    in the mail thread, by default these pre-compiled .so files are by
    default put into ${PN}-dev.  I grepped the following statement out of 
    the bitbake.conf file:

      FILES_${PN}-dev = "${includedir} ${FILES_SOLIBSDEV} ${libdir}/*.la \
                ${libdir}/*.o ${libdir}/pkgconfig ${datadir}/pkgconfig \
                ${datadir}/aclocal ${base_libdir}/*.o \
                ${libdir}/${BPN}/*.la ${base_libdir}/*.la" 

So what I am wondering is this the best solution?  Or is there some 
preferred method we want to encourage?

Scott
Comment 2 Scott Rifenbark 2014-07-22 08:28:03 UTC
Changing the state to NEEDINFO because I need some answers on my last comment.

Scott
Comment 3 Belen Barros Pena 2014-07-25 09:07:43 UTC
A very similar question / answer exchange in this thread 

https://lists.yoctoproject.org/pipermail/yocto/2014-July/020682.html

(just in case it helps somehow).
Comment 4 Scott Rifenbark 2014-07-25 12:54:41 UTC
Hi, 

This does provide more information.  Thanks for the pointer Belen.

Scott
Comment 5 Scott Rifenbark 2014-07-29 06:34:28 UTC
Hi, 

Changing status to IN PROGRESS DESIGN. I have a partial solution in the works and will soon get a review link posted here in the bug.

Scott
Comment 6 Scott Rifenbark 2014-08-04 06:53:45 UTC
Hi, 

I have added a new example to the "Writing a New Recipe" section that describes this issue.  The link is http://www.yoctoproject.org/docs/1.7/dev-manual/dev-manual.html#packaging-externally-produced-binaries.  

Please review the section.  I am changing the status to IN PROGRESS REVIEW.

Scott
Comment 7 Scott Rifenbark 2014-09-05 08:33:09 UTC
No feedback on this in four weeks.  I am marking it RESOLVED and setting the Doc flag to "Done."

Scott