Re: [OE-core] [PATCH] boost.inc: make libboost_python3.so available

2018-10-18 Thread Burton, Ross
On Thu, 18 Oct 2018 at 03:29, Yu, Mingli wrote: > Many thanks for Ross's clarification! > If we need to fix the packages one by one, but not add the hack at boost > side, then https://bugzilla.yoctoproject.org/show_bug.cgi?id=12833 > should be invalid. Agreed, done! Ross --

Re: [OE-core] [PATCH] boost.inc: make libboost_python3.so available

2018-10-17 Thread Yu, Mingli
On 2018年10月17日 17:39, Burton, Ross wrote: On Wed, 17 Oct 2018 at 06:48, Yu, Mingli wrote: I'm fine not add the the hack fix from boost side, but as I know there is another package camera-calibration-parsers which has the same problem as below apart from cv-bridge. BTW, there may some other pa

Re: [OE-core] [PATCH] boost.inc: make libboost_python3.so available

2018-10-17 Thread Burton, Ross
On Wed, 17 Oct 2018 at 06:48, Yu, Mingli wrote: > I'm fine not add the the hack fix from boost side, but as I know there > is another package camera-calibration-parsers which has the same problem > as below apart from cv-bridge. BTW, there may some other package also > has this kind of problem. Th

Re: [OE-core] [PATCH] boost.inc: make libboost_python3.so available

2018-10-16 Thread Yu, Mingli
On 2018年10月16日 20:05, Burton, Ross wrote: On Tue, 16 Oct 2018 at 12:18, Burton, Ross wrote: OpenCV has a patch to "fix" (bodge) the Py2 build: https://github.com/ros-perception/vision_opencv/pull/239 But this doesn't work for Py3. This was just pushed: https://github.com/ros-perception/vi

Re: [OE-core] [PATCH] boost.inc: make libboost_python3.so available

2018-10-16 Thread Burton, Ross
On Tue, 16 Oct 2018 at 12:18, Burton, Ross wrote: > OpenCV has a patch to "fix" (bodge) the Py2 build: > > https://github.com/ros-perception/vision_opencv/pull/239 > > But this doesn't work for Py3. This was just pushed: https://github.com/ros-perception/vision_opencv/commit/b57fd5b Ross -- ___

Re: [OE-core] [PATCH] boost.inc: make libboost_python3.so available

2018-10-16 Thread Burton, Ross
Right. This was a change in Boost 1.67 onwards: https://github.com/boostorg/python/commit/d4d41d94aecc9f8098aabd3587fcb95458451f71#diff-42dd6ec1330a7c47aaccf2ab2b8f1e02 OpenCV has a patch to "fix" (bodge) the Py2 build: https://github.com/ros-perception/vision_opencv/pull/239 But this doesn't

Re: [OE-core] [PATCH] boost.inc: make libboost_python3.so available

2018-10-16 Thread Burton, Ross
On Tue, 16 Oct 2018 at 11:01, wrote: > I'm a little worried about why we're having to create these links when > other software seems able to expect these things by default. Is this > some standard packaging most distros do? I'm a little worried we're > creating an ABI here which doesn't exist...

Re: [OE-core] [PATCH] boost.inc: make libboost_python3.so available

2018-10-16 Thread richard . purdie
On Tue, 2018-10-16 at 02:00 -0700, mingli...@windriver.com wrote: > From: Mingli Yu > > Currently boost provides ${libdir}/libboost_python35.so, > but there is some logic as below in CMakeLists.txt > of package cv-bridge under meta-ros layer. > [snip] > if(PYTHONLIBS_VERSION_STRING VERSION_LESS 3

[OE-core] [PATCH] boost.inc: make libboost_python3.so available

2018-10-16 Thread mingli.yu
From: Mingli Yu Currently boost provides ${libdir}/libboost_python35.so, but there is some logic as below in CMakeLists.txt of package cv-bridge under meta-ros layer. [snip] if(PYTHONLIBS_VERSION_STRING VERSION_LESS 3) find_package(Boost REQUIRED python) else() find_package(Boost REQUIRED