From: David Pirotte <david@altosw.be>
To: guile-user <guile-user@gnu.org>,
guile-devel <guile-devel@gnu.org>, info-gnu <info-gnu@gnu.org>
Subject: GNU Guile-CV 0.4.0 release
Date: Wed, 1 Mar 2023 02:02:09 -0300 [thread overview]
Message-ID: <20230301020209.6d9b8ebc@aicha> (raw)
[-- Attachment #1: Type: text/plain, Size: 3026 bytes --]
Hello,
GNU Guile-CV 0.4.0 is released.
This is a maintenance release, which introduces new interfaces.
[ for those who wouldn't know, the message is marked-up using
[ org-mode - https://orgmode.org/ - and best viewed in emacs, or any
[ org-mode aware editor, or (skip reading here and) visit
[ https://www.gnu.org/software/guile-cv/
* About
[[http://www.gnu.org/software/guile-cv/][GNU Guile-CV]]
Image Processing and Analysis in [[http://www.gnu.org/software/guile/][Guile]]
a Computer Vision functional programming library
Guile-CV is based on [[http://ukoethe.github.io/vigra/][Vigra]] (Vision with Generic Algorithms), enhanced
with additional algorithms (Image Textures, Delineate, Reconstruction
and many more), all accessible through a nice, clean and easy to use
high level API.
Guile-CV is natively multi-threaded, and takes advantage of multiple
cores, using high-level and fine grained application-level parallelism
constructs available in Guile, based on its support to POSIX threads.
* Download
Here are the compressed sources and a GPG detached signature [fn:1]:
http://ftp.gnu.org/gnu/guile-cv/guile-cv-0.4.0.tar.gz
http://ftp.gnu.org/gnu/guile-cv/guile-cv-0.4.0.tar.gz.sig
This released was bootstrapped with the following tools:
-] gcc Debian 12.2.0-14) 12.2.0
-] autoconf (GNU Autoconf) 2.71
-] automake (GNU automake) 1.16.5
-] libtool (GNU libtool) 2.4.7
-] makeinfo (GNU texinfo) 6.8
-] pdflatex 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian)
-] vigra 1.11.1
-] vigra_c commit 49f5319 [Jan 2023]
-] guile-3.0 3.0.9.4-d8c34-dirty
-] guile-lib-1.0 0.2.7
* Changes since 0.3.1
Here is a summary of visible changes since version 0.2.1. See GNU
Guile-CV's [[http://git.savannah.gnu.org/cgit/guile-cv.git][git summary]] and [[http://git.savannah.gnu.org/cgit/guile-cv.git/log/][git log]] for a complete description.
** Dependencies
Vigra >= 1.11.1
Vigra C >= commit 3351722 - Jan 18, 2022
** New interfaces
im-fft
im-fft-channel
im-fft-inverse
im-fft-inverse-channel
im-fcc
im-fcc-channel
im-fncc
im-fncc-channel
* Bug reports
Please report bugs to bug-guile-cv@gnu.org
* Mailing lists
For the time being, Guile-CV uses Guile's mailing list:
guile-user@gnu.org is for general user help and discussion;
guile-devel@gnu.org is used to discuss most aspects of Guile-CV,
including development and enhancement requests.
David
[fn:1]
Use a .sig file to verify that the corresponding file (without the
.sig suffix) is intact. First, be sure to download both the .sig file
and the corresponding tarball. Then, run a command like this:
gpg --verify guile-cv-0.4.0.tar.gz.sig
If that command fails because you don't have the required public key,
then run this command to import it:
gpg --keyserver keys.gnupg.net --recv-keys A3057AD7
and rerun the 'gpg --verify' command
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2023-03-01 5:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230301020209.6d9b8ebc@aicha \
--to=david@altosw.be \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=info-gnu@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).