From: Andy Tai <atai@atai.org>
To: guile-user@gnu.org
Subject: Re: OpenCV binding
Date: Wed, 7 Dec 2022 11:36:11 -0800 [thread overview]
Message-ID: <CAJsg1E_TtJU9MOUg_K-yDuNt2UaHAaeSuDE2RNbNtAM3YfOBoQ@mail.gmail.com> (raw)
In-Reply-To: <54E43A98-5666-45C0-9A42-F6CEAE85A4C7@telia.com>
As a follow-up to this, some recent bindings for OpenCV to other
languages use "unofficial" (not OpenCV supported) C bindings generated
by the binding authors themselves to bind... for example Go's gocv
contains C APIs generated from using libclang to parse OpenCV C++
headers and these C APIs are then used for bindings to Go, and D.
I read that Java and Python OpenCV bindings were also made this way
but I did not confirm them.
Wonder if this is the way to go for accessing modern OpenCV from guile?
On Thu, Sep 8, 2022 at 11:59 AM Hans Åberg <haberg-1@telia.com> wrote:
>
>
> > On 8 Sep 2022, at 19:54, David Pirotte <david@altosw.be> wrote:
> >
> >> curious if there is OpenCV binding for guile? and anything like NumPy
> >> for guile?
> >
> > No, and currently that would not be possible, as Open-CV is written in
> > C++ and there no ffi for C++ code ...
>
> I wrote a C++ wrap for Guile, and the opposite is also possible with GCC, only that C++ exceptions do not work properly:
> https://lists.gnu.org/archive/html/guile-user/2010-05/msg00035.html
>
>
prev parent reply other threads:[~2022-12-07 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 16:24 OpenCV binding Andy Tai
2022-09-08 17:54 ` David Pirotte
2022-09-08 18:59 ` Hans Åberg
2022-12-07 19:36 ` Andy Tai [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJsg1E_TtJU9MOUg_K-yDuNt2UaHAaeSuDE2RNbNtAM3YfOBoQ@mail.gmail.com \
--to=atai@atai.org \
--cc=guile-user@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).