From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: RFC: usage of cygwin32-/cygwin64- cross-toolchains
Date: Fri, 10 Jan 2014 16:55:00 -0000 [thread overview]
Message-ID: <20140110165502.GA5381@ednor.casa.cgf.cx> (raw)
In-Reply-To: <52CF9AD0.7000603@users.sourceforge.net>
On Fri, Jan 10, 2014 at 01:01:36AM -0600, Yaakov (Cygwin/X) wrote:
>On 2014-01-10 00:06, Christopher Faylor wrote:
>> On Thu, Jan 09, 2014 at 11:32:44PM -0600, Yaakov (Cygwin/X) wrote:
>>> Now that we're long finished bootstrapping cygwin64, I was wondering to
>>> what degree (if any) are the cygwin32-* and cygwin64-* packages in
>>> either the Cygwin distro or the Fedora Cygwin repository are of actual
>>> use. If you are using any of these, please specify on which platform
>>> you are using them (i686/x86_64, Cygwin, F19, or if you want to move to
>>> F20) and to what extent (IOW "to build Cygwin package A/B/C which
>>> require libraries X/Y/Z"). This will help me best manage my time wrt
>>> keeping these updated.
>>
>> I use them in (essentially) Fedora 18 but I have vague plans to update
>> to the latest Fedora sometime soon.
>
>And which libraries are you using?
Sorry. I think the answer is pretty much "all of them" but the list is
below. Since I do all of my builds on linux, I end up using most of
your packages. However, I have methods for pulling in what I need from
the release if there is a gap.
So, I guess, the only things I really *need* are the compiler and
binutils packages. Everything else is just "nice to have" for me.
cgf
cygwin32-freetype cygwin64-freetype
cygwin32-gcc cygwin64-gcc
cygwin32-gcc-c++ cygwin64-gcc-c++
cygwin32-gcc-gfortran cygwin64-gcc-gfortran
cygwin32-gcc-gnat cygwin64-gcc-objc
cygwin32-gcc-java cygwin64-gcc-objc++
cygwin32-gcc-objc cygwin64-gettext
cygwin32-gcc-objc++ cygwin64-gettext-static
cygwin32-gettext cygwin64-glib2
cygwin32-gettext-static cygwin64-gmp
cygwin32-glib2 cygwin64-isl
cygwin32-gmp cygwin64-libbfd
cygwin32-isl cygwin64-libedit
cygwin32-libbfd cygwin64-libffi
cygwin32-libedit cygwin64-libiconv
cygwin32-libffi cygwin64-libiconv-static
cygwin32-libiconv cygwin64-libltdl
cygwin32-libiconv-static cygwin64-libmpc
cygwin32-libltdl cygwin64-libpng
cygwin32-libmpc cygwin64-libtool
cygwin32-libpng cygwin64-libxml2
cygwin32-libtool cygwin64-minizip
cygwin32-libxml2 cygwin64-mpfr
cygwin32-minizip cygwin64-ncurses
cygwin32-mpfr cygwin64-nettle
cygwin32-ncurses cygwin64-openssl
cygwin32-nettle cygwin64-orc
cygwin32-openssl cygwin64-pcre
cygwin32-orc cygwin64-pixman
cygwin32-pcre cygwin64-pkg-config
cygwin32-pixman cygwin64-ppl
cygwin32-pkg-config cygwin64-readline
cygwin32-ppl cygwin64-w32api-headers
cygwin32-readline cygwin64-w32api-runtime
cygwin32-w32api-headers cygwin64-zlib
cygwin32-w32api-runtime cygwin64-zlib-static
next prev parent reply other threads:[~2014-01-10 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 5:32 Yaakov (Cygwin/X)
2014-01-10 6:06 ` Christopher Faylor
2014-01-10 7:01 ` Yaakov (Cygwin/X)
2014-01-10 16:55 ` Christopher Faylor [this message]
2014-01-10 9:47 ` Corinna Vinschen
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=20140110165502.GA5381@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin-apps@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).