From: Nigel Stewart & Fiona Smith <nigels@nigels.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: Packaging software built with cygwin
Date: Thu, 06 Feb 2003 13:17:00 -0000 [thread overview]
Message-ID: <3E42608E.1070507@nigels.com> (raw)
In-Reply-To: <033101c2cd3f$4f2936d0$78d96f83@pomello>
>>Technically, the ideal solution would be to link against a set
>>of static libraries.
>
> I believe this would require some significant work to make it possible.
OK, it feels like we're getting into a circular
argument. I am not insisting that anyone do
any particular thing to Cygwin. My intention
is to raise a perspective on a potential use
of Cygwin which may or may not be desirable,
feasible, popular or supported by the Cygwin
community.
> Also, the most experienced Cygwin coders won't be that interested,
> because they *like* Cygwin-the-enviroment, as opposed to
> Cygwin-for-the-sake-of-one-program.
Fair enough, I like using Cygwin-the-environment, but
feel restricted in terms of deploying binaries into
a non-cygwin environment. Even though the Cygwin
installation procedure has been greatly enhanced and
streamlined, in my opinion Cygwin is too heavy-weight for
an average computer user to install and administer.
So, if this is outside the scope of what Cygwin is
for, then that is a reasonable answer... I'm finding
mingw is working quite well (perhaps, the best of both
worlds) but would prefer to keep my code clean (POSIX)
rather than infected with extraneous win32 calls...
> You can - they just can't use the unix APIs.
> I use Cygwin for all my compilation needs, Cygwin-linked, or native Win32.
So rather than upsetting the Cygwin faithful, would
it be better to expand the support POSIX subset for
mingw, rather than making Cygwin an easily managed
light-weight dependency.
Regards,
Nigel Stewart
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2003-02-06 13:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 22:34 Packaging software built with Cygwin Jay Maynard
2003-02-04 23:27 ` Igor Pechtchanski
2003-02-05 1:46 ` Jay Maynard
2003-02-05 2:31 ` Igor Pechtchanski
2003-02-05 2:48 ` Jay Maynard
2003-02-05 3:32 ` Packaging software built with cygwin Christopher Faylor
2003-02-05 13:38 ` Nigel Stewart & Fiona Smith
2003-02-05 14:11 ` Christopher Faylor
2003-02-05 14:14 ` Jay Maynard
2003-02-05 17:18 ` Jay Maynard
2003-02-05 17:30 ` Nigel Stewart & Fiona Smith
2003-02-05 17:52 ` Max Bowsher
2003-02-06 13:17 ` Nigel Stewart & Fiona Smith [this message]
2003-02-06 13:43 ` Max Bowsher
2003-02-06 14:05 ` Nigel Stewart & Fiona Smith
2003-02-05 18:19 ` Christopher Faylor
2003-02-05 17:54 ` Christopher Faylor
2003-02-05 18:55 ` Jay Maynard
2003-02-05 20:43 ` Christopher Faylor
2003-02-05 21:41 ` Robert Collins
2003-02-06 9:59 ` Ronald Landheer-Cieslak
2003-02-06 13:24 ` Jay Maynard
2003-02-05 20:44 Franz Wolfhagen
2003-02-06 13:24 Joshua Daniel Franklin
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=3E42608E.1070507@nigels.com \
--to=nigels@nigels.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).