delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2002/06/17/01:27:57

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <5D01E8305096D3119D7D00508B5EBBF40A759D6B@ntmsg0133.corpmail.telstra.com.au>
From: "Michnowicz, Simon G" <Simon DOT Michnowicz AT team DOT telstra DOT com>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: Cygwin vs VC++ threading
Date: Mon, 17 Jun 2002 15:25:53 +1000
MIME-Version: 1.0

(Thank you to those who previously helped me link code from VC++ with
Cygwin)

My issue now is if someone has implemented a Windows-compatible
threading library.  The threading in VC++ (e.g. _beginthread) appears in
the VC++ Run-time library, so it can't be linked with cygwin1.dll.
Hence a VC++ that uses multi-threading can't be linked with
cygwin code.  

Is this correct? Or has someone implemented a library to make this possible.

Thanks



Simon Michnowicz
New Wave - Innovation, Chief Technology Unit
Tel:  03 9253 6769
Fax: 03 9253 6352

Partnering to Deliver Telstra's Competitive Edge.


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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019