From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] MinGW GNOME 3.26 libraries
Date: Tue, 20 Feb 2018 20:50:00 -0000 [thread overview]
Message-ID: <announce.6140f179-10b1-0b12-799f-57a077eb80bd@cygwin.com> (raw)
The following packages has been uploaded to the Cygwin distribution:
* mingw64-i686-adwaita-icon-theme-3.26.1-1
* mingw64-i686-atk1.0-2.26.1-1
* mingw64-i686-gdk-pixbuf2.0-2.36.11-1
* mingw64-i686-gdl3-3.26.0-1
* mingw64-i686-glib2.0-2.54.3-1
* mingw64-i686-glib2.0-networking-2.54.1-1
* mingw64-i686-glibmm2.4-2.54.1-1
* mingw64-i686-goffice0.10-0.10.38-1
* mingw64-i686-gtk3-3.22.28-1
* mingw64-i686-gtkmm3.0-3.22.2-1
* mingw64-i686-gtksourceview3.0-3.24.6-1
* mingw64-i686-json-glib1.0-1.4.2-1
* mingw64-i686-libgee0.8-0.20.1-1
* mingw64-i686-libgsf1-1.14.42-1
* mingw64-i686-librest0.7-0.8.1-1
* mingw64-i686-librsvg2-2.40.20-1
* mingw64-i686-libsoup2.4-2.60.3-1
* mingw64-i686-pango1.0-1.40.14-1
* mingw64-x86_64-adwaita-icon-theme-3.26.1-1
* mingw64-x86_64-atk1.0-2.26.1-1
* mingw64-x86_64-gdk-pixbuf2.0-2.36.11-1
* mingw64-x86_64-gdl3-3.26.0-1
* mingw64-x86_64-glib2.0-2.54.3-1
* mingw64-x86_64-glib2.0-networking-2.54.1-1
* mingw64-x86_64-glibmm2.4-2.54.1-1
* mingw64-x86_64-goffice0.10-0.10.38-1
* mingw64-x86_64-gtk3-3.22.28-1
* mingw64-x86_64-gtkmm3.0-3.22.2-1
* mingw64-x86_64-gtksourceview3.0-3.24.6-1
* mingw64-x86_64-json-glib1.0-1.4.2-1
* mingw64-x86_64-libgee0.8-0.20.1-1
* mingw64-x86_64-libgsf1-1.14.42-1
* mingw64-x86_64-librest0.7-0.8.1-1
* mingw64-x86_64-librsvg2-2.40.20-1
* mingw64-x86_64-libsoup2.4-2.60.3-1
* mingw64-x86_64-pango1.0-1.40.14-1
This updates the GTK+/GNOME libraries for the MinGW-w64 cross-compiler
toolchains to the 3.26 stable release.
--
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
reply other threads:[~2018-02-20 20:50 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=announce.6140f179-10b1-0b12-799f-57a077eb80bd@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin@cygwin.com \
/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).