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: <0b0301c14422$b3621150$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Michael D. Crawford" <crawford AT goingware DOT com>, <cygwin AT cygwin DOT com>
References: <3BA5E64B DOT 5030602 AT goingware DOT com>
Subject: Re: debugging threads in CygWin?
Date: Sun, 23 Sep 2001 21:27:16 +1000
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: 23 Sep 2001 11:35:15.0729 (UTC) FILETIME=[D0989810:01C14423]

----- Original Message -----
From: "Michael D. Crawford" <crawford AT goingware DOT com>
To: <cygwin AT cygwin DOT com>
Sent: Monday, September 17, 2001 10:02 PM
Subject: RE: debugging threads in CygWin?


> Thanks for responding.

No probs, sorry for the delay this time around.


> I'm trying to build it under CygWin, but without using the cygwin.dll.
>  I want to be
> able to run native Win32 applications built this way.

You need to pass -mno-cygwin to gcc and g++. You also need to make a
couple of changes to correctly support -mno-cygwin with g++. See this
lists archives (search for g++ should find the reference fairly
recently).

> I'm putting these options on the g++ command line:
>
> -D_REENTRANT -Wl,--subsystem,windows -mwindows

See above.

> It should be possible to build ZooLib applications as X applications
> under CygWin as you suggest, but then this would require an X server
and
> would involve a great deal
> of extra labor on the part of the machine.

Not that much actually :]. The rendering only gets done once after all.

> I wasn't trying to use mingw.  I plan to install mingw as a separate
> build system and
> get that to work after I get the cygwin builds working.

cygwin without linking to cygwin1.dll == mingw. (approximately). The
mingw compiler uses win32 paths, not unix style paths, but thats about
the only difference if the appropriate libraries are present. (I may get
corrected on this point :]).

> Also you said that the zoolib web site doesn't mention Cygwin support.

If you build without linking to cygwin1.dll, you are not creating cygwin
support. You can use Win32 calls from cygwin linked programs (as XFree86
does), but some of the cygwin support is unable to work correctly when
you do so - depending on the calls made. (i.e. if you use ReadFile
instead of read(), cygwin cannot deliver signals to your thread).

Cygwin has support for pthreads, and I recommend you use that rather
than win32 threads.

>  It doesn't yet because I'm doing it.  I wrote the zoolib web site, as
part
> of my effort  to help ZooLib author Andy Green to get ZooLib released
as open source.

Cool. Well we'll help you help Andy :].

Rob



--
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/