From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] fdk-aac 0.1.5-2
Date: Thu, 21 Dec 2017 05:53:00 -0000 [thread overview]
Message-ID: <5a3b1753.0543ca0a.bd01a.2c9a@mx.google.com> (raw)
In-Reply-To: <605539f0-4e86-7165-e48a-877477494b00@cygwin.com>
On Wed, 20 Dec 2017 18:56:12, Yaakov Selkowitz wrote:
> What need do you specifically have for static libraries?
its not a need - its a preference - i prefer static builds - the count of
programs i regularly build is small, so the redundancy doesnt hurt my use case.
also if I am to share my builds with others it makes for a smoother process - as
you can end up with a single exe. notice carefully that many projects offer
static and shared builds, here is one example:
http://ffmpeg.zeranoe.com
if you choose to keep doing only shared builds it wont kill me, but it is an
annoyance because its that many more libraries i need to build, when I could
just download and link an already built static library - also notice carefully
that these type packages have some inconsistency - whereas the ones i listed
previously do not have static library - these here do:
1. mingw64-x86_64-curl
- usr/x86_64-w64-mingw32/sys-root/mingw/lib/libcurl.a
2. mingw64-x86_64-libgnurx
- usr/x86_64-w64-mingw32/sys-root/mingw/lib/libgnurx.a
- usr/x86_64-w64-mingw32/sys-root/mingw/lib/libregex.a
3. mingw64-x86_64-openssl
- usr/x86_64-w64-mingw32/sys-root/mingw/lib/libcrypto.a
- usr/x86_64-w64-mingw32/sys-root/mingw/lib/libssl.a
4. mingw64-x86_64-win-iconv
- usr/x86_64-w64-mingw32/sys-root/mingw/lib/libiconv.a
5. mingw64-x86_64-zlib
- usr/x86_64-w64-mingw32/sys-root/mingw/lib/libz.a
--
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
next prev parent reply other threads:[~2017-12-21 2:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f8243f41bb0027583fad54e1e4f817aa@NO-ID-FOUND.mhonarc.org>
2017-12-21 0:56 ` Steven Penny
2017-12-21 3:31 ` Yaakov Selkowitz
2017-12-21 5:53 ` Steven Penny [this message]
2018-03-07 12:08 ` Steven Penny
2017-12-19 18:19 Yaakov Selkowitz
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=5a3b1753.0543ca0a.bd01a.2c9a@mx.google.com \
--to=svnpenn@gmail.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).