unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: Andy Tai <atai@atai.org>
Cc: guile-user@gnu.org
Subject: Re: OpenCV binding
Date: Thu, 8 Sep 2022 14:54:39 -0300	[thread overview]
Message-ID: <20220908145439.728d4fab@aicha> (raw)
In-Reply-To: <CAJsg1E8_GGeg+UW8NuUQDDnUC05+pg+LVyookRnNau3NZwQMXw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]

Hello Andy,

> 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 ... They used to have and maintain a
C api, up to 2.xx (not sure up to what exact version), then dropped
support for the C api.

This is why - not the only reason, but a major factor in my decision -
I choose to bind and extend Guile-CV [1] using Vigra [2], but now Vigra
seems unmaintained :(

You also might look at aiscm [3], and other projects that might interest
you, to my knowledge, the most up-to-date guile projects list is here
[4].

David

[1]	https://www.gnu.org/software/guile-cv/
[2]	http://ukoethe.github.io/vigra/

	it actually is because someone was maintaining a Vigra C lib
	that I could use Vigra in Guile-CV, as Vigra is also written in
	C++

	https://github.com/BSeppke/vigra_c

[3]	https://github.com/wedesoft/aiscm
[4]	http://sph.mn/foreign/guile-software.html

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-09-08 17:54 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 [this message]
2022-09-08 18:59   ` Hans Åberg
2022-12-07 19:36     ` Andy Tai

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=20220908145439.728d4fab@aicha \
    --to=david@altosw.be \
    --cc=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).