Phil wrote:
>The Wine socket implementation has problems when it comes to select.
>A fix for this problem is not currently on anybody's radar.
> http://www.winehq.org/pipermail/wine-devel/2006-February/044588.html
Hmm. You never filed a bug at http://bugs.winehq.org
for this, it seems. Could you
"Phil Lodwick" <[EMAIL PROTECTED]> writes:
> My initial test of creating two threads, one that is Win32-aware and then
> synchronizing between the two of them appears to work. Does anybody know why
> this might be a bad idea?
It's not a bad idea, except maybe for performance reasons. As long as
> Could you please elaborate on what kind of problems you have when trying
> to use the Windows version of your library under Wine?
The Wine socket implementation has problems when it comes to select. A fix
for this problem is not currently on anybody's radar.
http://www.winehq.org/pipermail/wi
Phil Lodwick escribió:
Greetings,
I have a proprietary library that has both Windows and Linux ports. The
Windows DLL has problems running on Wine, so I have created a builtin version
of this DLL in Wine. This has worked fine, except for one function that
basically creates a new thread and
> There was a problem like this with the CoreAudio library on macos, but I am
> not sure about the details.
> Is there any reason why you cannot use CreateThread?
I can't use CreateThread because the pthread_create is in a Linux library I
am calling.
My initial test of creating two threads, one
Hi,
> If instead of using pthread_create I use CreateThread, I never have a
> problem. I notice no other wine DLLs are using pthread_create and I have
> seen hints that this might not work. If so, how do I use the Linux
> library. (Call_dll_to_spawn_thread_and_register_callback is just simulatin
