All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yu, Mingli" <mingli.yu@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>,
	"Purdie, Richard" <richard.purdie@linuxfoundation.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] boost.inc: make libboost_python3.so available
Date: Wed, 17 Oct 2018 13:46:59 +0800	[thread overview]
Message-ID: <5BC6CCD3.4050003@windriver.com> (raw)
In-Reply-To: <CAJTo0LY79q4La-mTQwG552XAkwJ8UTLp9yztVCd4g7m-pogpKw@mail.gmail.com>



On 2018年10月16日 20:05, Burton, Ross wrote:
> On Tue, 16 Oct 2018 at 12:18, Burton, Ross <ross.burton@intel.com> 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

Thanks Ross!
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. This to say we need to fix the issue for the 
this kind of packages one by one.

meta-ros/recipes-ros/image-common/camera-calibration-parsers_1.11.13.bb:do_configure 
failed
| CMake Error at 
/$Prj/camera-calibration-parsers/1.11.13-r0/recipe-sysroot-native/usr/share/cmake-3.12/Modules/FindBoost.cmake:2048 
(message):
|   Unable to find the requested Boost libraries.
|
|   Boost version: 1.68.0
|
|   Boost include path:
|   /$Prj/camera-calibration-parsers/1.11.13-r0/recipe-sysroot/usr/include
|
|
|   Could not find the following Boost libraries:
|
|           boost_python3
|
|   Some (but not all) of the required Boost libraries were found.  You may
|   need to install these additional Boost libraries.  Alternatively, set
|   BOOST_LIBRARYDIR to the directory containing Boost libraries or 
BOOST_ROOT
|   to the location of Boost.
| Call Stack (most recent call first):
|   CMakeLists.txt:10 (find_package)

Thanks,

>
> Ross
>


  reply	other threads:[~2018-10-17  5:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16  9:00 [PATCH] boost.inc: make libboost_python3.so available mingli.yu
2018-10-16 10:00 ` richard.purdie
2018-10-16 10:38   ` Burton, Ross
2018-10-16 11:18     ` Burton, Ross
2018-10-16 12:05       ` Burton, Ross
2018-10-17  5:46         ` Yu, Mingli [this message]
2018-10-17  9:39           ` Burton, Ross
2018-10-18  2:28             ` Yu, Mingli
2018-10-18  9:22               ` Burton, Ross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5BC6CCD3.4050003@windriver.com \
    --to=mingli.yu@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=ross.burton@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.