Re: [OE-core] [PATCH 2/3] boost: Fix link problems with caffe and Movidius SDK

I can't seem to find where cmake's python checker magically decides the name of the shared object, but I did find an override, so you can drop the patch.   I had even gone so far as to simply make a zero length file instead of the symlink, and everything still built and run.  It is just some

Re: [OE-core] [PATCH 2/3] boost: Fix link problems with caffe and Movidius SDK

Perhaps a bug in the cmake detect which is part of boost, because I am not using python2 for caffe. I used the path of least resistance because as far as I could tell boost only let you build one or the other and in my case it was the python3 boost api. In the end caffe was working and all

Re: [OE-core] [PATCH 2/3] boost: Fix link problems with caffe and Movidius SDK

I thought that boost_python was the py2 binary, and boost_python3 was the py3 one? Is this not a bug in caffe? On 13 March 2018 at 03:08, Jason Wessel wrote: > When using an image built with the Yocto Project which has a compiler > and all the required libraries,

[OE-core] [PATCH 2/3] boost: Fix link problems with caffe and Movidius SDK

When using an image built with the Yocto Project which has a compiler and all the required libraries, projects such as caffe for the Movidius SDK which use python3 and boost fail to build because they look for libboost_python.so. The error that cmake returns doesn't even point to the fact that