This is the mail archive of the
pthreads-win32@sourceware.org
mailing list for the pthreas-win32 project.
RE: pthread_exit and STL problems
The reason the executable couldn't locate msvcrt80.dll is because you
will have to install the Visual Studio 8 redistributable which can be
found in " C:\Program Files (x86)\Microsoft Visual Studio
8\SDK\v2.0\BootStrapper\Packages\vcredist_x86" of a Visual Studio
install. Or you can read more at Microsoft's website. The other thing
you have to do is embed the manifest into the pthreadVC2.dll after is
generated. This is a new requirement Microsoft added for Visual Studio
8.
Ross,
The embedding of the manifest in the dll is another thing besides the
warnings that has to be dealt with.
Thanks,
Kip
-----Original Message-----
From: pthreads-win32-owner@sourceware.org
[mailto:pthreads-win32-owner@sourceware.org] On Behalf Of Stefan
Eilemann
Sent: Wednesday, January 31, 2007 4:00 AM
To: Ross Johnson
Cc: Pthreads-Win32 list
Subject: Re: pthread_exit and STL problems
On 31. Jan, 2007, at 0:13 , Ross Johnson wrote:
Hello Ross,
> My C++ is very limited but I have a couple of general questions and
> possibly redundant general comments.
>
> You're using pthreads-win32 2.8.0 but which version of the DLL are
> you using, VC or VCE?
I am using pthreadVC2.
> Are you building the pthreads library from source? The packaged
> dlls are built using VC6 and the BUGS file in the pthreads
> distribution refers to problems relating to the VCE dll which may
> or may not be VC version specific.
I am using the packaged DLL. Since I am using the VC version, it is my
understanding that this doesn't matter.
>
> Does trying any of the above alternatives avoid the problem?
I've just tried to build the library myself using VC8.0.
Using 'nmake clean VC' path failed, since the resulting library
was referencing msvcrt80.dll, which the executable couldn't find.
Converting the .dsw file in VS2005 and using it resulted in a
usable library - though I am not sure which 'version' I have.
__CLEANUP_C and PTW32_BUILD are defined. Can you enlighten me?
Do I need to define __CLEANUP_C during my build as well? I am
just a bit nervous using a library where I haven't fully grokked
the side effects.
Cheers,
Stefan.
--
http://www.equalizergraphics.com
http://www.linkedin.com/in/eilemann