public inbox for
 help / color / mirror / Atom feed
From: Ross Johnson <>
To: pthreads-win32 <>
Subject: Re: BCB support (lib+dll)
Date: Thu, 18 Nov 2004 01:21:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Robert Kindred wrote:

>I am not sure if pthreads-win32 is officially supported under Builder.  I
>have a project which builds it under BCB5.  However, CodeGuard tells me that
>there are some leaks.  I don't know if pthreads-win32 actually has leaks, or
>this is a Builder problem.
Not 'officially' supported, but Will Bryant contributed patches and a 
makefile for BCB (see 'Bmakefile' in the source and tests folders - also 
README.Borland). I'm about to run them again to see where they get to 
(I'm in Linux right now on a dual-boot machine). I'm pretty sure the dll 
builds ok, but I don't recall if it passed all the tests.

Assuming that leaks have not recently been added, the library has been 
screened several times in the past by others, and their patches, if any, 
have been applied. So the library should be clean, but if you can track 
those leaks down it would be appreciated. If it helps, the very first 
test in the 'tests' folder prints a list of all the pthreads-win32 
structs and their sizes. This test was added a while back for this purpose.


>Finally, I am a C++ programmer, and my wrappers on top of pthreads-win32 may
>not be anything that you want.
>Robert Kindred
>>-----Original Message-----
>>[]On Behalf Of Gianluca
>>Sent: Wednesday, November 17, 2004 5:51 AM
>>Subject: BCB support (lib+dll)
>>Please is it possible to put in
>>latest the builds for BCB too?
>>Thanks in advance,

  reply	other threads:[~2004-11-18  1:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-17 11:51 Gianluca
2004-11-17 15:02 ` Robert Kindred
2004-11-18  1:21   ` Ross Johnson [this message]
2004-11-18  3:44     ` Will Bryant

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).