unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
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.3.1 release
Date: Tue, 16 Nov 2021 00:45:56 -0300	[thread overview]
Message-ID: <20211116004556.6dce600f@aicha> (raw)

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

Hello,

GNU Guile-CV 0.3.1 is released.

This is a maintenance release, which fixes a bug in the =pre-inst-env=
script, which is used by Guile-CV at build time and may also be used to
test and run an uninstalled Guile-CV instance.

  [ 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/
  [ or
  [	https://savannah.gnu.org/projects/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.3.1.tar.gz
	http://ftp.gnu.org/gnu/guile-cv/guile-cv-0.3.1.tar.gz.sig

This released was bootstrapped with the following tools:

	-] gcc              (Debian 11.2.0-10) 11.2.0 
	-] autoconf         (GNU Autoconf) 2.71 
	-] automake         (GNU automake) 1.16.5 
	-] libtool          (GNU libtool) 2.4.6 
	-] 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 e81e12a [Sep 2019]
	-] guile-3.0        3.0.7.51-b1bba
	-] guile-lib-1.0    0.2.7

* Changes since 0.3.0

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.

** Bug fixing

The =pre-inst-env.in= script has been fixed and now adds a specific
build time library location, so Guile 3.0 (>= 3.0.6) finds libguile-cv
at build time.

Guile 3.0 (>= 3.0.6) does not use libltdl anymore, and although in guile
(system foreign-library) module, both the comment and the definition of
augment-ltdl-library-path seems to take care of finding .so files either
aside .la or in a .libs/ subdir, it does not work.

* 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.3.1.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:[~2021-11-16  3:45 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=20211116004556.6dce600f@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).