Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <006101c0a328$e2a11240$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "David A. Cobb" <superbiskit AT home DOT com>,
        "Cygwin General MailList" <cygwin AT cygwin DOT com>
References: <3A9FB1E6 DOT FDE781B5 AT home DOT com>
Subject: Re: What's such a big deal about MSVC
Date: Sat, 3 Mar 2001 01:55:49 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime: 02 Mar 2001 14:47:12.0799 (UTC) FILETIME=[AA9F42F0:01C0A327]

AFAIK CRT routines mainly.

IIRC The gtk+ stuff is ported _deliberately_ to the win32 Graphics
interface. (No X calls). GTK+ compiles very cleanly with -mno-win32 :]

Remember that cygwin has come a very long way in the last 12 months (not
that it was bad before), with better i/o support, many more packages,
the setup.exe and so on. I suspect that porters are more likely to
choose cygwin now than they were...

Now back to the topic :]

Chris - you've created another catch phrase...

David, have you tried compiled ctk+/win32 with cygwin (with -mwin32 to
get the right graphics routines) ? Have you got a list of what cygwin is
missing and what it does?

Autoconf won't work (IIRC the porter hasn't set it up as he builds on
MSVC). but there is are MSVC makefiles and the like which can be used to
create standard Makefiles.

BTW: I have tried, but some time ago, and with the goal of X graphics
calls not win32 graphics calls, so I can't offer all that much advice
(except to say that it worked :])

Rob


----- Original Message -----
From: "David A. Cobb" <superbiskit AT home DOT com>
To: "Cygwin General MailList" <cygwin AT cygwin DOT com>
Sent: Saturday, March 03, 2001 1:44 AM
Subject: What's such a big deal about MSVC


> I see several packages, GTK+/Win32 being on my mind at the moment, for
> which the author advises they _must_ be compiled with MSVC.  Part of
the
> reason, evidently is some MSVC????.DLL that gets included.
>
> So, what's the trick?  What funny backdoor is M$ exploiting with this?
> In other words, what would it take to allow Cygwin to provide whatever
> functionality this beast is giving?
>
> --
> David A. Cobb, The Superbiskit !
> Software Engineer, Public Access Advocate, All around nice guy.
> Get my PGP key at
> :<http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=superbiskit>
> Fingerprint=0x{6E3E DB8C 2E8C 4248 62B2  FE29 08EE CF0A 3629 E954}
> "By God's Grace I am a Christian man, by my actions a great sinner."
> --The Way of a Pilgrim, R. M. French [tr.]
> <---.----!----.----!----.----!----.----!----.----!----.----!----.---->
>
>
>
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
>
>


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple