<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>I tried to make a recipe that just installs the file (not sure if this is exactly what you meant) it does generate the ipk with all files at the right place<br><br>the recipe:<br><br>do_install() {<br>install -d ${D}${includedir} ${D}${includedir}/atsc ${D}${includedir}/dvb ${D}${includedir}/dvb/si ${D}${includedir}/mpeg ${D}${includedir}/mpeg/psi ${D}${includedir}/ietf<br>install -m 0755 common.h ${D}${includedir}<br>install -m 0755 atsc/a52.h ${D}${includedir}/atsc<br>install -m 0755 dvb/ci.h dvb/si.h dvb/sim.h dvb/si_print.h dvb/sub.h ${D}${includedir}/dvb<br>install -m 0755 mpeg/aac.h mpeg/h264.h mpeg/mp2v.h mpeg/mpga.h mpeg/pes.h mpeg/psi.h mpeg/psi_print.h mpeg/ts.h ${D}${includedir}/mpeg<br>install -m 0755 ietf/rtp3551.h ietf/rtp.h ${D}${includedir}/ietf<br>cp -r mpeg/psi/ ${D}${includedir}/mpeg/<br>cp -r dvb/si/ ${D}${includedir}/dvb/<br><br>}<br><br>but after launching the compilation for the framework config.log says : configure:17806: checking bitstream/common.h usability<br>configure:17806: arm-angstrom-linux-gnueabi-gcc -mfpu=vfpv3-d16 -march=armv7-a -mthumb-interwork -mfloat-abi=hard --sysroot=/home/rick/oe-core/build/out-eglibc/sysroots/colibri-t20 -std=gnu99 -c -O2 -pipe -g -feliminate-unused-debug-types -D_REENTRANT conftest.c >&5<br>conftest.c:71:30: fatal error: bitstream/common.h: No such file or directory<br>compilation terminated.<br><br><div>> From: nicolas.dechesne@linaro.org<br>> Date: Thu, 17 Jul 2014 11:16:23 +0200<br>> Subject: Re: [yocto] How to include native bitstream dependency in recipe?<br>> To: natural_groove@hotmail.fr; yocto@yoctoproject.org<br>> <br>> cc list. please let's have the discussion on the list<br>> <br>> On Thu, Jul 17, 2014 at 11:10 AM, Natural Groove<br>> <natural_groove@hotmail.fr> wrote:<br>> > "biTStream is a set of C headers allowing a simpler access to binary<br>> > structures such as specified by MPEG, DVB, IETF, etc. "<br>> > (http://www.videolan.org/developers/bitstream.html)<br>> ><br>> > It does not have to be built (just make install)<br>> <br>> ok. you still need a recipe for it, it will be a simple one that only<br>> install the .h files in the '-dev' package. then your other recipe<br>> will just need to DEPENDS on bitstream or bistream-native.<br>> <br>> the .h files will be installed in the sysroot like any other package/recipes.<br><br><br></div> </div></body>
</html>