From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Victor Rodriguez <vm.rod25@gmail.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>,
openembedded-devel@lists.openembedded.org
Subject: Re: Bug in Open CV receipt
Date: Tue, 21 Jul 2015 15:49:45 -0500 [thread overview]
Message-ID: <55AEB069.80005@linux.intel.com> (raw)
In-Reply-To: <CAK5mtexxdYxhwvv-MB27Ur56iwAV8O3Y6ah_BPAo+R58NmNouQ@mail.gmail.com>
On 07/21/2015 09:57 AM, Victor Rodriguez wrote:
> Hi team
>
> Few weeks ago I was having some problems with open CV receipt. In the
> begining I toght I was adding opencv tro my core-image-minimal-xfce
> just with this:
>
> IMAGE_INSTALL_append = " gcc gcc-dev openssh php mariadb opencv"
>
> Now after booting the image I realize that none of the libraries for
> open stack were added to my image
>
> What I had to do was the following:
>
>
> IMAGE_INSTALL_append = " libopencv-core-dev libopencv-highgui-dev
> libopencv-imgproc-dev libopencv-objdetect-dev libopencv-ml-dev
> opencv-staticdev python-opencv"
>
A recipe can produce several packages. As I can see on opencv recipe, it
can produced the following ones:
PACKAGES="opencv-staticdev opencv-dev opencv-dbg opencv-doc opencv
opencv-apps python-opencv"
and dynamic ones (depending on what else you have install)
PACKAGES_DYNAMIC="^opencv-locale-.* ^libopencv-.*"
For the opencv case, it happens that the package opencv is empty, so you
need to append the other sub-packages it produces into your
IMAGE_INSTALL variable.
So, it is not a bug, this is expected.
> Even last night when one of the opencv developers ask me for python
> opencv I had to add the last part python-opencv. That is not cool at
> all . If I add opencv in the beginning I assume we are more than cool
> with that and yocto will add all the packages . Unless I am doing
> something wrong, in taht case I am more than happy to get the
> feedback.
>
> Thanks a lot for all the help . If someone else can reproduce this bug
> I am more than happy to report it in bugzila (not sure the URL)
>
> Hope it helps to cut the time of some others
>
> Best regards
>
> Victor Rodriguez
>
next prev parent reply other threads:[~2015-07-21 20:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 14:57 Bug in Open CV receipt Victor Rodriguez
2015-07-21 20:49 ` Leonardo Sandoval [this message]
2015-07-21 20:50 ` [yocto] " Victor Rodriguez
2015-07-21 20:50 ` Victor Rodriguez
2015-07-21 21:03 ` [yocto] " Gary Thomas
2015-07-21 21:03 ` Gary Thomas
2015-07-22 12:35 ` [oe] " Otavio Salvador
2015-07-23 15:05 ` [yocto] " Victor Rodriguez
2015-07-23 15:05 ` [oe] " Victor Rodriguez
2015-07-23 16:30 ` [yocto] " Otavio Salvador
2015-07-23 16:30 ` [oe] " Otavio Salvador
2015-08-10 15:12 ` [yocto] " Victor Rodriguez
2015-08-10 15:12 ` [oe] " Victor Rodriguez
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=55AEB069.80005@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=vm.rod25@gmail.com \
--cc=yocto@yoctoproject.org \
/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.