> On Aug 10, 2015, at 4:50 AM, yocto yocto <yoctomailingl...@gmail.com> wrote: > > Please see the attachment for a simplified example. A library (consisting of > 1 cpp and 1 header) is being built using soci. Compiling fails since soci.h > is not found. > > 2015-08-10 13:16 GMT+02:00 Burton, Ross <ross.bur...@intel.com > <mailto:ross.bur...@intel.com>>: > > On 10 August 2015 at 12:13, yocto yocto <yoctomailingl...@gmail.com > <mailto:yoctomailingl...@gmail.com>> wrote: > However, when compiling my own recipe I get compiling errors ("soci.h not > found"). I am 100% sure that I specified the correct paths. > > The headers are likely installed in the sysroot, but your script can't find > them. The first step would be to verify that the sysroot does in fact have > the headers installed in, and then you'll have to debug your configure > scripts to find out why they don't find the headers. Sharing your recipe and > sources will help here.
yeah the CMakeLists.txt seems to not include search paths for <sysroot>/usr/include/soci one way you could do it is refer to soci files with namespace when using them in source code like #include <soci/soci.h> then it will automatically apply the default sysroot search paths to includedir and reach it. Alternative is that you can defile a .cmake file for soci and include that in soci recipe and then just find the module in your package’s CMakeLists.txt > > Ross > > <soci-example.tar.bz2>-- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
