Hi Andre,

I tried without

FILES_${PN}_append = "${includedir}/open62541.h"

and got a QA error about a file installed that was not added to a
package.... I don't understand the ${PN}-dev here, and I'm not sure how
packaging works in this context - since it's not clear to me which files
get installed and which don't... except for when a recipe that depends on
this breaks because it can't find the header file.


On Tue, Mar 6, 2018 at 4:06 PM Andre McCurdy <armccu...@gmail.com> wrote:

> On Tue, Mar 6, 2018 at 1:03 PM, Giordon Stark <kra...@gmail.com> wrote:
> > Yes. The CMakeLists file definitely doesn't install that (annoyingly).
> > Playing around a bit, I created a test recipe, added these lines in my
> > open62541.inc file (original recipe here)
> >
> > do_install_append() {
> >   install -d ${D}${includedir}
> >   install -m 644 ${B}/open62541.h ${D}${includedir}
> > }
> >
> > FILES_${PN}_append = "${includedir}/open62541.h"
> This is trying to put the header in the runtime package (ie the
> package containing files which typically end up in the target rootfs).
> Header files should be in the ${PN}-dev package instead.
> Since the default packaging rules already cover header files, you
> don't actually need to add anything here in order to have the header
> packaged correctly - just remove that line.
> Note that you also tried to use _append without a leading space -
> which is wrong in this context (it's wrong in almost every context).
> > and it looks like the test recipe can pick up that header file
> correctly. So
> > I think this is correct-er (at least for code that uses #include
> > <open62541.h>).
> >
Giordon Stark
yocto mailing list

Reply via email to