Re: symbol hiding

2004-05-13 Thread Dmitry Timoshkov
"Paul Davis" <[EMAIL PROTECTED]> wrote: > >> for this reason, i personally wouldn't feel comfortable asking in a > >> public forum how to go about doing this. your mileage may and probably > >> does vary, of course. > > > >Well, if I could clearly predict ELF linker behaviour with several > >diffe

Re: [DMUSIC] cleanups, fixes and IDirectMusicStyle loading

2004-05-13 Thread Alexandre Julliard
Raphael <[EMAIL PROTECTED]> writes: > Alexandre, instead using copy of the sames files can we use a static library > for sharing this code ? I'm afraid not, we can't create a separate static library every time we need to share some code between dlls, it doesn't scale. -- Alexandre Julliard [EM

Re: symbol hiding

2004-05-13 Thread Paul Davis
>> for this reason, i personally wouldn't feel comfortable asking in a >> public forum how to go about doing this. your mileage may and probably >> does vary, of course. > >Well, if I could clearly predict ELF linker behaviour with several >different modules each having global variables/functions w

Re: Running "United Devices Agent" (was Unhandled API Call to Kernel32 Question)

2004-05-13 Thread Roger Olson
Tue, 11 May 2004 23:22:27 +0100 Mike Hearn Wrote: > Sure. Be warned : this would be a major project for you. There is a > huge world of difference between writing VB apps and writing a > Windows emulator. > > First thing you need to do is learn C. Unfortunately VB > doesn't cut it at this sort of l

Re: symbol hiding

2004-05-13 Thread Dmitry Timoshkov
"Paul Davis" <[EMAIL PROTECTED]> wrote: > i'd just like to mention a small concern i have. > > hiding symbols might well be a perfectly honest thing to want to do. i > personally can't see why, since a list of symbol names doesn't provide > much extra help to somebody who wants to disassemble and

symbol hiding

2004-05-13 Thread Paul Davis
i'd just like to mention a small concern i have. hiding symbols might well be a perfectly honest thing to want to do. i personally can't see why, since a list of symbol names doesn't provide much extra help to somebody who wants to disassemble and reverse engineer your code. but i can understand t

Re: wininet: prevent memory leak and superfluous status notifications

2004-05-13 Thread Kevin Koltzau
On Thursday 13 May 2004 01:04 pm, Steven Edwards wrote: > While you are working on the wininet stuff... If you have time could > you look at a way to be able to make use of Winsock on the mingw port? > We wanted to convert wininet to winsock but Alexandre says this will > be to slow on Unix so we

Re: Exporting symbols

2004-05-13 Thread Dan Timis
From: Mike Hearn <[EMAIL PROTECTED]> Subject: Re: Exporting symbols Date: Thu, 13 May 2004 10:39:42 +0100 Organization: CodeWeavers, Inc On Wed, 12 May 2004 19:45:42 -0700, Dan Timis wrote: After running strip on the .exe.so if we do nm -D all the symbols are still there. Is there any way to get r

Re: Alsa compilation error

2004-05-13 Thread Ferenc Wagner
Francois Gouget <[EMAIL PROTECTED]> writes: > On Thu, 13 May 2004, James Courtier-Dutton wrote: > >> You have to use a version of alsa that came out after >> 19th June 2002 I.E. 0.9.0rc2 or above. The version of >> alsa you are using came out in 26th Feb 2002 >> >> Just upgrade your alsa version

Re: Alsa compilation error

2004-05-13 Thread James Courtier-Dutton
Francois Gouget wrote: On Thu, 13 May 2004, James Courtier-Dutton wrote: [...] You have to use a version of alsa that came out after 19th June 2002 I.E. 0.9.0rc2 or above. The version of alsa you are using came out in 26th Feb 2002 Just upgrade your alsa version to a NON-BETA version. Debian stab

Re: Alsa compilation error

2004-05-13 Thread Francois Gouget
On Thu, 13 May 2004, James Courtier-Dutton wrote: [...] > You have to use a version of alsa that came out after 19th June 2002 > I.E. 0.9.0rc2 or above. > The version of alsa you are using came out in 26th Feb 2002 > > Just upgrade your alsa version to a NON-BETA version. Debian stable does not ha

Re: Building WINE with Intel ICC for Linux

2004-05-13 Thread Eric Pouech
Steven Edwards a écrit : --- Mike Hearn <[EMAIL PROTECTED]> wrote: No surprise it crashes, this code is setting something in the TEB which you commented out. Wine won't get anywhere when missing such critical functions: being able to set and access the TEB is vital for nearly all Wine functions. F

Re: Winelib and MFC and mixing native Windows DLLs

2004-05-13 Thread Shachar Shemesh
Raghavan Gurumurthy wrote: Second question - If my Windows application uses 10 DLLs, do I have to build all these 10 DLLs in addition to the executable on Winelib? Or can I leave the 10 DLLs run in 'native' mode and only convert the executable to be built with Winelib? I think that depends on

Re: Winelib and MFC and mixing native Windows DLLs

2004-05-13 Thread Tim Hentenaar
On Thu, 13 May 2004 09:37:04 -0700 Raghavan Gurumurthy <[EMAIL PROTECTED]> wrote: > I am trying to build my MFC-based Windows application on Linux. > > First question - I read in the Winelib user guide that I have to build MFC > completely on Winelib as well. Is this really a must? Is there no

Re: wininet: prevent memory leak and superfluous status notifications

2004-05-13 Thread Steven Edwards
Hello Kevin, --- Kevin Koltzau <[EMAIL PROTECTED]> wrote: > Under Windows, InternetOpenUrl only sends one > INTERNET_STATUS_HANDLE_CREATED and the > handle created by this function only creates one > INTERNET_STATUS_HANDLE_CREATED when closed While you are working on the wininet stuff... If you h

Winelib and MFC and mixing native Windows DLLs

2004-05-13 Thread Raghavan Gurumurthy
Title: Winelib and MFC and mixing native Windows DLLs I am trying to build my MFC-based Windows application on Linux. First question - I read in the Winelib user guide that I have to build MFC completely on Winelib as well. Is this really a must? Is there no other alternative? Second quest

Re: Alsa compilation error

2004-05-13 Thread James Courtier-Dutton
Francois Gouget wrote: revision 1.42 date: 2004/05/05 22:03:48; author: julliard; state: Exp; lines: +143 -67 James Courtier-Dutton <[EMAIL PROTECTED]> Updated to the new alsa api. This patch causes a compilation error on my build machine: alsa-headers 0.9+0beta12-3 gcc -c -I. -I. -I../../../inc

Winelib Native Linux App

2004-05-13 Thread Simon Craythorn
I'm a little confused on two points. I wrote a simple windows application just to open a window. It has a file menu with exit on it, and that's about it. All the documentation I read for Winelib suggests that re-compiling the application is the best option as this will give a native linux app th

Alsa compilation error

2004-05-13 Thread Francois Gouget
revision 1.42 date: 2004/05/05 22:03:48; author: julliard; state: Exp; lines: +143 -67 James Courtier-Dutton <[EMAIL PROTECTED]> Updated to the new alsa api. This patch causes a compilation error on my build machine: alsa-headers 0.9+0beta12-3 gcc -c -I. -I. -I../../../include -I../../../in

Re: [patch] Listview drag-and-drop fix

2004-05-13 Thread Rein Klazes
On Wed, 12 May 2004 09:07:25 -0400, you wrote: > On Monday May 10 2004 07:31 am, Rein Klazes wrote: > > > The problem here is that on Windows the WM_LBUTTONUP message *is* > > swallowed when it terminates a drag and drop operation. The real problem > > is probably not to get in this LISTVIEW_Trac

Re: winmm test patch

2004-05-13 Thread Andreas Mohr
Hi, On Thu, May 13, 2004 at 07:30:27AM -0400, Robert Reif wrote: > Adds better error messages. Would probably be more useful to use an often-used construct like: #define DEVTYPE_TO_STR(dev) case dev: return #dev Andreas Mohr

Re: Load a .so from a Windows binary using Wine

2004-05-13 Thread Mike Hearn
On Thu, 13 May 2004 09:05:34 +0300, Shachar Shemesh wrote: > Only winelib apps can technically call a native so, so calling your > library directly from the PE is impossible without either employing a > proxy, or implementing the linux loader yourself. You could add a new Wine DLL which simply e

Re: Exporting symbols

2004-05-13 Thread Mike Hearn
On Wed, 12 May 2004 19:45:42 -0700, Dan Timis wrote: > After running strip on the .exe.so if we do nm -D all the symbols are > still there. Is there any way to get rid of the ones that are not > needed for dynamic linking? Dmitry is right, ask on the binutils list. However if you hide symbols u