From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-announce@cygwin.com
Subject: cygport 0.31.0-1
Date: Tue, 27 Feb 2018 08:55:00 -0000 [thread overview]
Message-ID: <20180227024319.8704-1-yselkowitz@cygwin.com> (raw)
The following packages have been uploaded to the Cygwin distribution:
* cygport-0.31.0-1
cygport is the standard method for building and maintaining packages for
the Cygwin distribution.
This release includes some new features:
* CMake-based builds use Ninja instead of Unix Makefiles to compile if the
default src_compile() functions are used. Otherwise, Unix Makefiles will
still be used to avoid breaking API; however, if you use the default
src_compile() but a custom src_install(), then you will have to change
your .cygport file. The value of CYGCMAKE_GENERATOR overrides the default.
* Cross-compiling with Meson uses the system cross files; this requires
the latest Meson 0.44.1.
* Compiler flags for enabling Stack Smashing Protection and Object Size
Checking guards have been added to the default CFLAGS/etc., except when
cross-compiling to MinGW. This requires Cygwin 2.10.
* The LLVM tools will be used, if present, for stripping binaries and
detecting DLL dependencies, as they tend to be faster than Binutils.
Jon Turney (1):
Produce obsoletes: headers in .hint files
Yaakov Selkowitz (15):
prepstrip: use LLVM toolchain where available
Add Message-Id to announcements
cmake: support and use Ninja generator
kde4: use Ninja cmake generator by default
kf5: use Ninja cmake generator by default
qt4-cmake: use Ninja cmake generator by default
meson: fix installation of i686-w64-mingw32 specs
Add security flags to CFLAGS
cross: remove SSP flags from CFLAGS for MinGW
meson: use system cross files
kf5: separate kf5_cmake command, redefine kf5_compile
kde4: update kde-l10n pruning for Apps 17.12 deprecation
list_deps: use LLVM tools if present
Update gnuconfig
Bump version to 0.31.0
--
Yaakov
reply other threads:[~2018-02-27 8:55 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=20180227024319.8704-1-yselkowitz@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin-announce@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).