alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: alsa-devel@alsa-project.org
Subject: Announcement for alsa-gobject v0.2.0 release
Date: Sat, 21 Nov 2020 10:29:33 +0900	[thread overview]
Message-ID: <20201121012933.GA62268@workstation> (raw)

Hi,

This is an announcement for the second official release of alsa-gobject
project[1]. The release is available in below URL:

 * https://github.com/alsa-project/alsa-gobject/releases/tag/v0.2.0

It includes some enhancements and bug fixes.

* Some implementations of GLib GQuark is exported as error domain and
  corresponding enumerations are added. This improves error reporting
  in each libraries. It closes issue #47[2].
* Selection of substream in ALSARawmidi.StreamPair.open() now works well.
  This closes issue #53[3].
* Prototypes of some methods in ALSACtl.Card object for data of
  TLV(Type-Length-Value) in ALSA control interface are changed without
  backward compatibility. Corresponding exported symbols are maintained
  by new symbol version. In detail, refer to #55[4].
* Error handling is changed so that function call with invalid argument 
  just returns with warnings instead of generating GError, according to
  convention for GLib application. Memory allocation failure is supposed
  to be unrecoverable error and aborts program, as well.
* It's possible to build for older version Linux kernel, therefore
  build dependency is now Linux kernel v4.5 or later.

For the new release, documentations are also updated. They're
auto-generated by gtk-doc[5] from function annotations:

 * https://alsa-project.github.io/alsa-gobject-docs/

The new release of Rust crates are available as well in repository.
They're auto-generated by gtk-rs/gir[6]:

 * https://github.com/alsa-project/alsa-gobject-rs/releases/tag/v0.2.0

I note that ALSA PCM interface is not supported yet. Please refer to
my announcement for v0.1.0 for the reason[7].

[1] https://github.com/alsa-project/alsa-gobject
[2] https://github.com/alsa-project/alsa-gobject/issues/47
[3] https://github.com/alsa-project/alsa-gobject/issues/53
[4] https://github.com/alsa-project/alsa-gobject/pull/55
[5] https://developer.gnome.org/gtk-doc-manual/
[6] https://github.com/gtk-rs/gir
[7] https://mailman.alsa-project.org/pipermail/alsa-devel/2020-June/169488.html


Regards

Takashi Sakamoto

                 reply	other threads:[~2020-11-21  1:30 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201121012933.GA62268@workstation \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.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 NNTP newsgroup(s).