From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] cygport 0.33.0-1
Date: Mon, 25 Mar 2019 20:13:00 -0000 [thread overview]
Message-ID: <announce.20190325154720.25999-1-yselkowitz@cygwin.com> (raw)
The following packages have been uploaded to the Cygwin distribution:
* cygport-0.33.0-1
cygport is the standard method for building and maintaining packages for
the Cygwin distribution.
This release adds Python 3.7 to PYTHON_WHEEL_VERSIONS="default" and the
3.8 prerelease version to "all". Maintainers of Python module packages
can and should begin rebuilding their packages with this version so that
we can move entirely to 3.7 in the near future.
The other notable change is that autotools-based MinGW packages will no
longer build static libraries by default. Many packages require special
preprocessor macros to handle dllimport/dllexport when building them, or
when building with them, on native Windows. This precludes building
them, or their reverse dependencies, with both shared and static
libraries simultaneously. If you need really static libraries (e.g.
setup prerequisites), AND the library builds properly both shared and
static, AND its library dependencies do not require different macros for
building with them in each mode, then you can override this by passing
--enable-static to configure. If you still need static libraries but the
other conditions are not met, you can compile the package twice in separate
directories, once with the default and the second with --disable-shared
--enable-static, but be careful of any differences between generated files
(e.g. installed config headers or pkg-config metadata etc.) between the two
(shared should generally be the default).
The other changes in this release are internal in preparation for future
features.
--
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:[~2019-03-25 20:13 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.20190325154720.25999-1-yselkowitz@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).