From: Martin Jansa <martin.jansa@gmail.com>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH] opencv: Add missing dependencies
Date: Wed, 23 Mar 2016 15:34:22 +0100 [thread overview]
Message-ID: <20160323143422.GC2565@jama> (raw)
In-Reply-To: <CAPybu_1-CCqMjSRC5it6nLL+SWzP7WfJEL6S5dY=Wjn4unon3g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
On Wed, Mar 23, 2016 at 02:05:41PM +0100, Ricardo Ribalda Delgado wrote:
> Hi Martin
>
> On Wed, Mar 23, 2016 at 11:12 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
>
>
> > Still shows:
> > WARN: opencv: libopencv-dnn rdepends on protobuf, but it isn't a build
> > dependency?
> >
> > protobuf support in dnn probably depends on something else which is also autodetected.
>
> if I just clone a clean version of meta-oe and meta-core and do a
> bitbake opencv i cannot replicate the error.
>
> Any idea of how to replicate it without having to do a bitbake world
> before bitbake opencv?
Check temp/log.do_package if you see protobuf dependency being added for
libopencv-dnn package.
If not then read configure script or sources to see what in
libopencv-dnn is being autodetected -> then build these autodetected
dependencies before rebuilding opencv and re-check the log.do_package
file.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-03-23 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 10:31 [PATCH] opencv: Add missing dependencies Ricardo Ribalda Delgado
2016-03-23 10:12 ` Martin Jansa
2016-03-23 13:05 ` Ricardo Ribalda Delgado
2016-03-23 14:34 ` Martin Jansa [this message]
2016-03-23 20:53 ` Martin Jansa
2016-03-24 12:21 ` Ricardo Ribalda Delgado
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=20160323143422.GC2565@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=ricardo.ribalda@gmail.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.