Those are 2 different paths to the same goal.
Just to clarify my "goal"
Painless development and deployment of
software across Linux and Windows.
Both open-source and commercial.
Which, for me is already 95% there
with Cygwin, and possibly even
98% there with Cygwin+Mingw
Che
Nigel Stewart & Fiona Smith wrote:
> 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 heav
> > The source tarball for cygwin is 4.6M. I don't understand why this
> > is a huge hardship but, frankly, I don't really care.
> 4.6 MB times how many versions will I need to keep around? Before I removed
> them from the Hercules site, I had four sets of the Cygwin DLLs,
> corresponding to four
On Thu, Feb 06, 2003 at 10:34:36AM +0100, Ronald Landheer-Cieslak wrote:
> The way I read GPL (but please correct me if I'm wrong) you should be able
> to write a fork off the current Setup that installs the Hercules and gets
> the Cygwin from one of the mirrors (of which you can download the lis
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 inten
The way I read GPL (but please correct me if I'm wrong) you should be able
to write a fork off the current Setup that installs the Hercules and gets
the Cygwin from one of the mirrors (of which you can download the list at
the time of installing from cygwin.com). Technically, you would not be
d
On Thu, 2003-02-06 at 05:55, Jay Maynard wrote:
> > A setup.ini with just the cygwin DLL in it seems pretty simple.
>
> True. OTOH, when setup.exe changes, the format of that file is subject to
> change (see Igor's warning in the message where he first suggested that). I
> can insulate myself fr
One of the things that your users have been bitten of with the newer
cygwin1.dll is that they impose a stronger authentication mechanism (ntsec
is on per default). This is often brought up here by users that are have
upgraded their version.
Please (re)consider supporting a cygwin package via the
Cutting through the noise:
1) In an open source, volunteer project there are no guarantees that
anything will be fixed. We do the best we can given our interests
and time. However, you should be reporting cygwin bugs to the cygwin
mailing list if you want the possibility of getting them
On Wed, Feb 05, 2003 at 12:55:43PM -0500, Christopher Faylor wrote:
> On Wed, Feb 05, 2003 at 11:18:22AM -0600, Jay Maynard wrote:
> >It may be intended to be upward compatible, but that's not our experience.
> Ok. I'm not going to start scouring random other mailing lists for
> cygwin bug reports
On Thu, Feb 06, 2003 at 04:31:15AM +1100, Nigel Stewart & Fiona Smith wrote:
>>I would suggest that, if it is desired to promote the development of
>>applications on the Cygwin platform, serious consideration be made to
>>making it as simple as possible to install only those portions of
>>Cygwin th
On Wed, Feb 05, 2003 at 11:18:22AM -0600, Jay Maynard wrote:
>On Tue, Feb 04, 2003 at 10:32:46PM -0500, Christopher Faylor wrote:
>> On Tue, Feb 04, 2003 at 08:48:03PM -0600, Jay Maynard wrote:
>> >On Tue, Feb 04, 2003 at 09:31:43PM -0500, Igor Pechtchanski wrote:
>> >>Remember that linking against
Nigel Stewart & Fiona Smith wrote:
>> I would suggest that, if it is desired to promote the development of
>> applications on the Cygwin platform, serious consideration be made
>> to making it as simple as possible to install only those portions of
>> Cygwin that the application requires. This mean
I would suggest that, if it is desired to promote the development of
applications on the Cygwin platform, serious consideration be made to making
it as simple as possible to install only those portions of Cygwin that the
application requires. This means just the necessary DLLs, without all of the
On Tue, Feb 04, 2003 at 10:32:46PM -0500, Christopher Faylor wrote:
> On Tue, Feb 04, 2003 at 08:48:03PM -0600, Jay Maynard wrote:
> >On Tue, Feb 04, 2003 at 09:31:43PM -0500, Igor Pechtchanski wrote:
> >>Remember that linking against some version of libcygwin.a doesn't mean
> >>you have to keep to
On Wed, Feb 05, 2003 at 09:12:02AM -0500, Christopher Faylor wrote:
> On Thu, Feb 06, 2003 at 12:39:45AM +1100, Nigel Stewart & Fiona Smith wrote:
> >>However, just in case you need to hear it, it is true that you have to
> >>provide the sources for the cygwin DLL if you want to distribute it.
> >T
On Thu, Feb 06, 2003 at 12:39:45AM +1100, Nigel Stewart & Fiona Smith wrote:
>>However, just in case you need to hear it, it is true that you have to
>>provide the sources for the cygwin DLL if you want to distribute it.
>
>There is always the MingW option via -mno-cygwin. (Perhaps stating the
>ob
However, just in case you need to hear it, it is true that you have to
provide the sources for the cygwin DLL if you want to distribute it.
There is always the MingW option via -mno-cygwin.
(Perhaps stating the obvious, but just in case...)
http://www.mingw.org/
Regards,
Nigel Stewart
-
On Tue, Feb 04, 2003 at 08:48:03PM -0600, Jay Maynard wrote:
>On Tue, Feb 04, 2003 at 09:31:43PM -0500, Igor Pechtchanski wrote:
>>Now, hold on there, no need to jump the gun. I'm not what you may call
>>"a definitive expert on Cygwin licensing". In fact, whatever that page
>>says surely override
On Tue, Feb 04, 2003 at 09:31:43PM -0500, Igor Pechtchanski wrote:
> Now, hold on there, no need to jump the gun. I'm not what you may call "a
> definitive expert on Cygwin licensing". In fact, whatever that page says
> surely overrides what I said earlier.
Okkay...that's what I'd been relying o
On Tue, 4 Feb 2003, Jay Maynard wrote:
> On Tue, Feb 04, 2003 at 06:27:39PM -0500, Igor Pechtchanski wrote:
> > You are aware that linking against the Cygwin DLL automatically makes your
> > software GPL'ed, right?
>
> Not according to http://cygwin.com/licensing.html:
>
> "In accordance with sect
On Tue, Feb 04, 2003 at 06:27:39PM -0500, Igor Pechtchanski wrote:
> You are aware that linking against the Cygwin DLL automatically makes your
> software GPL'ed, right?
Not according to http://cygwin.com/licensing.html:
"In accordance with section 10 of the GPL, Red Hat permits programs whose
so
On Tue, 4 Feb 2003, Jay Maynard wrote:
> This is probably an FAQ, but I haven't been able to find any answers on the
> FAQ page at cygwin.com.
>
> I'm the maintainer of Hercules, an emulator for IBM mainframe systems that
> runs on Linux, Mac OS X, and other Unix-style OSes, and Windows via Cygwin
This is probably an FAQ, but I haven't been able to find any answers on the
FAQ page at cygwin.com.
I'm the maintainer of Hercules, an emulator for IBM mainframe systems that
runs on Linux, Mac OS X, and other Unix-style OSes, and Windows via Cygwin.
It's distributed under an OSD-compliant license
24 matches
Mail list logo
