From: Jimmy at 86Pixels <hello@86pixels.com>
To: buildroot@busybox.net
Subject: [Buildroot] OpenCV-Python Support
Date: Thu, 08 Jun 2017 06:41:04 -0700 [thread overview]
Message-ID: <1496929264.1141448.1002947512.5E415DB6@webmail.messagingengine.com> (raw)
In-Reply-To: <1496323183.528769.995383584.4FE97B8B@webmail.messagingengine.com>
Has nobody ever run into this?
On Thu, Jun 1, 2017, at 06:19 AM, Jimmy at 86Pixels wrote:
> Good day all,
>
> I noticed that back in 2015 there was a patch submitted and signed off
> that added opencv_python as a build option for OpenCV 2.
>
> I noticed that it was then reverted in this commit when OpenCV 2.4 was
> targeted.
>
> https://github.com/buildroot/buildroot/commit/ac57d05076d7554d5bf43375cc7269fc0e658acc#diff-44c9b82a4a4d16aae921f9f88a95634b
>
> To my knowledge, this should still work, was this simply a mistake, or
> am I missing something? I'd love to add it back in as its a dependency
> of mine.
>
> Thanks!
> Jimmy
next prev parent reply other threads:[~2017-06-08 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 13:19 [Buildroot] OpenCV-Python Support Jimmy at 86Pixels
2017-06-08 13:41 ` Jimmy at 86Pixels [this message]
2017-06-08 15:30 ` Thomas Petazzoni
2017-06-08 15:39 ` Jimmy at 86Pixels
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=1496929264.1141448.1002947512.5E415DB6@webmail.messagingengine.com \
--to=hello@86pixels.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox