wine-devel

wine-devel@winehq.org

11 participants
84461 discussions

iTunes, 1608: Unable to create InstallDriver instance
by Olivier Kaloudoff 07 Oct '04

07 Oct '04

Hi, with a fresh clean install of wine, trying to run iTunesSetup.exe gives the error given in the subject. It's related to DCOM, so Microsoft recommands to download DCOM95 or DCOM98 ... crawling again and again ... It turns out that some DCOM patches have been written, and TransGaming is ready to give them away as LGPL, asking for some Wine people to change their license to LGPL, too, instead of pure GPL. http://www.kernel-traffic.org/wine/wn20020522_123_print.html ok .. so I don't understand the whole implications of this, but, probably, switching these famous patches to LGPL would help much people to have their applications run under Wine. Did this point evolve since 2002 ? Did someone try to start a rewrite of the relevant patches (I don't think this is the good way to proceed, I would propose some compensation for their work to the GPL code writers) ? Is there any light for the small users we are ? ;-) Regards, Olivier Kaloudoff LUG Linux Azur http://www.linux-azur.org FRANCE

1 0

MASK_FLAG_DDEWAIT in ShellExecuteExW32 ()
by Olivier Kaloudoff 07 Oct '04

07 Oct '04

Hi, Trying to run an unsupported application, I get the following error: fixme:exec:ShellExecuteExW32 flags ignored: 0x00000140 and the application gives me C:\windows\temp\MMIsnst, access denied... so two bits are set by the application, requesting MASK_FLAG_DDEWAIT and MASK_NOCLOSEPROCESS ... as far as I understand DDEWAIT, it should be trivial to implement, as it is just some kind of sleep() ... even with no C experience, I should be able to do this.. what about NOCLOSEPROCESS ? .... hmmm, crawling the web, it turns out that the writer of this application (MobileMaster.exe) probably made a call to a RunWait function ... in a language called LibertyBasic ... am I right ? http://libertybasic.conforums.com/index.cgi?board=tips&num=1079874405&actio… sub RunWait file$, para$, dir$ ' sub to open an application or file ' ' Usage: ' call RunWait {filename}, {parameters}, {startfolder} ' ' filename ...... full path to file or executable ' parameters .... if file is a document this should be empty ' if file is an executable any parameters ' that should be passed to it ' startfolder ... initial folder, can be empty SEE.MASK.NOCLOSEPROCESS = hexdec("40") SEE.MASK.FLAG.DDEWAIT = hexdec("100") struct ExecInfo, _ Size as long, _ fMask as long, _ hwnd as long, _ Verb$ as ptr, _ File$ as ptr, _ Parameters$ as ptr, _ Directory$ as ptr, _ Show as long, _ InstApp as long, _ IDList as long, _ Class$ as ptr, _ keyClass as long, _ HotKey as long, _ Icon as long, _ Process as long ExecInfo.fMask.struct = SEE.MASK.NOCLOSEPROCESS or SEE.MASK.FLAG.DDEWAIT ExecInfo.File$.struct = file$ + chr$(0) ExecInfo.Parameters$.struct = para$ + chr$(0) ExecInfo.Directory$.struct = dir$ + chr$(0) ExecInfo.Show.struct = _SW_SHOWNORMAL ExecInfo.Size.struct = len(ExecInfo.struct) calldll #shell32, "ShellExecuteExA", _ ExecInfo as struct, _ result as long if result <> 0 then Handle = ExecInfo.Process.struct Milliseconds = _INFINITE calldll #kernel32, "WaitForSingleObject", _ Handle as long, _ Milliseconds as long, _ result as long end if end sub

1 0

Re: Handle the case when an active MDI child is being hidden
by Alexandre Julliard 07 Oct '04

07 Oct '04

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > Hello, > > with my last patch I introduced a regression with frame menu handling > when last maximized MDI child gets destroyed. Here is a better fix for > that problem. > > Changelog: > Dmitry Timoshkov <dmitry(a)codeweavers.com> > Handle the case when an active MDI child is being hidden. This is causing test failures here: msg.c:1591: Test failed: wrong focus window 0x90028 msg.c:1616: Test failed: wrong focus window 0x90028 msg.c:1622: Test failed: wrong active MDI child (nil) msg.c:1672: Test failed: wrong focus window 0x60026 msg.c:1678: Test failed: wrong focus window 0x60026 msg.c:1684: Test failed: wrong focus window 0x60026 msg.c:1746: Test failed: wrong focus window 0x90028 msg.c:1799: Test failed: wrong focus window 0x90028 -- Alexandre Julliard julliard(a)winehq.org

1 0

make depend on CVS fails due some widl error
by Saulius Krasuckas 06 Oct '04

06 Oct '04

It may be redundant info, but whatever. An excerpt from the output: | Configure finished. Do 'make depend && make' to compile Wine. | | cd include && make all | make[1]: Entering directory `/mnt/antras/usr/src/wine-cvs/wine/include' | ../tools/widl/widl -I. -I. -I../include -I../include -h -H exdisp.h | exdisp.idl | exdisp.idl:103: Error: parse error | make[1]: *** [exdisp.h] Error 1 :-/

3 3

I'm getting two of every email post
by Kevin R. Casper 06 Oct '04

06 Oct '04

I must have done something wrong when I signed up for this list as an email list. I'm getting two of every message. Any idea what's wrong? Kevin Casper

3 2

Martin Rasp/PTB ist außer Haus.
by Martin.Rasp＠ptb.de 06 Oct '04

06 Oct '04

Ich werde ab 06.10.2004 nicht im Büro sein. Ich kehre zurück am 22.10.2004. Vertreter: Herr Scheffler, Telefon 8419

1 0

Re: Small API documentation fix
by Francois Gouget 06 Oct '04

06 Oct '04

On Wed, 6 Oct 2004, Francois Gouget wrote: > > I found this one when examining the output of ./tools/winapi/winapi_check. > It turned out to be just a stroke of luck as winapi_check seems to complain > about the documentation of each and every function though I don't understand > what's wrong: > > $ ./tools/winapi/winapi_check > dlls/advapi32/advapi.c:53: advapi32: BOOL WINAPI GetUserNameA(LPSTR,LPDWORD): > documentation: GetUserNameA (ADVAPI32.@) wrong [...] > $ ./tools/winapi/winapi_check | grep documentation: | wc -l > 9489 You can ignore this. It turns out I had a bad patch in my tree. Now everything is back to normal (only 485 documentation-related issues). -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ 1 + e ^ ( i * pi ) = 0

1 0

Re: some console fixes (for ctrl-c handling)
by Ferenc Wagner 06 Oct '04

06 Oct '04

Eric Pouech <pouech-eric(a)wanadoo.fr> writes: > ChangeLog: > - ctrl-c enabling flag is now inherited > - fixed console-related fields in RTL_USER_PROCESS_PARAMETERS > - various clean-up in kernel32.SetConsoleCtrlHandler > - only send a console event once to a process and not to all the process' threads > [...] > + ok(GenerateConsoleCtrlEvent(CTRL_C_EVENT, 0), "Couldn't send ctrl-c event\n"); > + todo_wine ok(mch_count == 1, "Event isn't synchronous\n"); > + ok(WaitForSingleObject(mch_event, 3000) == WAIT_OBJECT_0, "event sending didn't work\n"); > + CloseHandle(mch_event); > + ok(SetConsoleCtrlHandler(NULL, TRUE), "Couldn't turn off ctrl-c handling\n"); > + mch_event = CreateEventA(NULL, TRUE, FALSE, NULL); > + mch_count = 0; > + ok(GenerateConsoleCtrlEvent(CTRL_C_EVENT, 0), "Couldn't send ctrl-c event\n"); Hi Eric, these Ctrl-C events kill off winetest under XP. You probably did your tests and found this OK, so I'm not sure what to do. Can you offer a solution? I commented those two lines out, which made it go through... -- Thanks, Feri.

2 1

winedbg - No debug info showing
by Ann and Jason Edmeades 06 Oct '04

06 Oct '04

Hiya, I just hit a trap in a d3d8 test I was running, and winedbg isnt showing the module information (I've put a manual DebugBreak in, and stepped through the call to a fixme, and I see no info!). This was on my temporary wine machine, so I dont know if its ever worked before, but I have a basic (cvs) install, no special info. I am sure winedbg used to show the d3d8 functions in the past. Note that because they are in COM routines, they dont have to be exports, but I dont know if they are or not. nm d3d8.dll.so does seem to show the entrypoints, so is there anything I am missing - configuration wise, setup wise etc? Jason

2 1

audio driver autodetection
by James Hawkins 06 Oct '04

06 Oct '04

>From Mike Hearn's winecfg post: > > - Obviously, once audio autodetection has been moved into the drivers we > > need to kill the audio tab. > > Still needs to be done. Not all that hard. I remember working on this a couple months ago. I put the driver detection in winmm.c, but that was wrong. I can't remember exactly what I was supposed to do to fix it...something like put the driver detection in each driver. I'm not really sure what that means or how it would work if it does what I think it does. Does it mean that we load one driver, and if it doesn't detect its *nix counterpart then it loads the next driver? I would like to get to work on this task, so if anyone has any pointers or ideas on this one, please let me know. -- James Hawkins

6 15

DllCanUnloadNow janitorial
by James Hawkins 06 Oct '04

06 Oct '04

Hi, I would like to work on the DllCanUnloadNow janitorial task, but I was wondering if there are any patches or examples of dll's that correctly implement this so that I can do it right. Is LockServer(TRUE/FALSE) the same as this example? static HRESULT WINAPI SFCF_LockServer(LPCLASSFACTORY iface,BOOL dolock) { IClassFactoryImpl *This = (IClassFactoryImpl *)iface; FIXME("(%p)->(%d),stub!\n",This,dolock); return S_OK; } If they are the same, what is needed to complete this stub? I would think that there would be a refCount variable that is incremented if dolock is true and decremented if dolock is false. Also, should the LockServer functions be listed in the spec files of the dlls? After implementing LockServer, it should be an easy matter to do a check for refCount == 0 to see if the dll can be unloaded or not. Am I heading in the right direction? -- James Hawkins

1 0

kind of newbie question :)
by Carlo Bono 06 Oct '04

06 Oct '04

i report this post from comp.emulators.ms-windows.wine... hope i will not be boring, stupid or what. even if that's difficult :D first of all, excuse me for my bad english. but i hope it will be the worst thing that all of you will read here :)) i'm trying to port an industrial application on linux, some people suggested me to try to compile it using wine/winelib. i documented myself a bit on it, and i tried to build a sample application (as the user guide tells, winemine :D) but winemaker DOES NOT genreate any configure script! wine version is 14/9/2004 and was compiled from source on slackware 10.0 running on a via C3 (intel x86 100% compatibile). is there any suggestion or workaround, or maybe this is normal, or maybe then i'm forgetti something really stupid? (maybe not so stupid, don't think it makes a difference :D) i also tried to generate by myself a configure script, using tools as autoscan, autoheader and autoconf, and trying to "fine tune" the output script by hand, but i could not manage to get the application compile. something tells me i'm not on the right way to compile a greater, more complex program like i have to do :))) thanks anyway just for reading this post! have a nice day carlo

2 1

kind of newbie question :)
by Carlo Bono 06 Oct '04

06 Oct '04

first of all, excuse me for my bad english. but i hope it will be the worst thing that all of you will read here :)) i'm trying to port an industrial application on linux, some people suggested me to try to compile it using wine/winelib. i documented myself a bit on it, and i tried to build a sample application (as the user guide tells, winemine :D) but winemaker DOES NOT genreate any configure script! wine version is 14/9/2004 and was compiled from source on slackware 10.0 running on a via C3 (intel x86 100% compatibile). is there any suggestion or workaround, or maybe this is normal, or maybe then i'm forgetti something really stupid? (maybe not so stupid, don't think it makes a difference :D) i also tried to generate by myself a configure script, using tools as autoscan, autoheader and autoconf, and trying to "fine tune" the output script by hand, but i could not manage to get the application compile. something tells me i'm not on the right way to compile a greater, more complex program like i have to do :))) thanks anyway just for reading this post! have a nice day carlo

2 1

Re: How to deal with C++ APIs in wine spec file
by Jon Griffiths 06 Oct '04

06 Oct '04

Hi, > how can I call a class constructor (which is built form > another class) in spec file? Can anyone provide me an example? This is possible, although it is not immediately obvious. Here is the solution I use (I will document this one day but I'm very busy ATM): Scenario 1: App uses C++ dll, dll does not use win32 calls Solution: Compile as non wine dll (unix .so) and link. Scenario 2: App uses C++ dll, dll uses win32 calls Solution 1: Static link with the object files of the dll. Winebuild will resolve references to win32 calls. Solution 2: Use native .exe and dlls Solution 3: Compile as wine dll with one extern "C" dummy function that does nothing. Do _not_ attempt to export any C++ symbols. install the resulting .dll.so as: /usr/local/lib/wine/NAME.dll.so and place a soft link to it as /usr/local/lib/libNAME.dll.so Don't forget to install the .def file as: /usr/local/lib/wine/libNAME.def Link as a wine dll _and_ a unix .so. e.g: wineg++ -mwindows -o app.exe.so <opts> -lNAME -lNAME.dll In any dll or program that calls functions from the dll, place a call to your dummy function immediately after WinMain(). This will force winebuild to link to the dll and the loader to set up the Win32 function pointers in the dll. Due to dlopen magic the ctors/dtors for statics will only be called once. Be carefull with the order of static object initialisation, you may need to use gcc's attribute init_priority to ensure correct ordering, or defer static initialisation until after loading Hope this helps, Jon ===== "Don't wait for the seas to part, or messiahs to come; Don't you sit around and waste this chance..." - Live jon_p_griffiths(a)yahoo.com __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail

3 3

Re: Add a test case for accelerators, make the test pass on Wine. Take 3.
by Alexandre Julliard 05 Oct '04

05 Oct '04

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > I don't see why it's needed because there is no a visual hang, system > menu gets displayed. This is exactly the same behaviour as pressing > Left arrow on the most left item of a window menu, so I vote to remove > this code from the patch: But this is not how it's supposed to behave, on Windows the system menu doesn't get displayed in that case. And if we are going to be incompatible anyway, then not tracking the system menu at all is much better IMO. -- Alexandre Julliard julliard(a)winehq.org

1 0

Wine user guid (pdf)
by Daniel Richards Jr. 05 Oct '04

05 Oct '04

I am new to Linux (gettn tired of M$ so called operating systems) and just got a hold of your wine user guide. Thanks for putting the time in to put this together. Greatly detailed and just what I need to try and get some of my win based programs to run in Linux. As I get a the opportunity to setup wine while following the guide, I will let you know if I come across anything confusing etc. Thanks again for putting this together. Dan

2 1

audio.c - problems
by Dietrich Teickner 05 Oct '04

05 Oct '04

Knows anyone this problem ? I can not compile wine since some days.I have checked out all new and also start make clen after connfigure and some more. Any Ideas ? Dietrich make[2]: Wechsel in das Verzeichnis ?/home/sao2l02/Wine/wine/dlls/winmm/winealsa½ gcc -c -I. -I. -I../../../include -I../../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o audio.o audio.c audio.c: In function `ALSA_TraceParameters': audio.c:514: too many arguments to function `snd_pcm_hw_params_get_access' audio.c:515: too many arguments to function `snd_pcm_hw_params_get_format' audio.c:564: too many arguments to function `snd_pcm_hw_params_get_channels' audio.c:568: too many arguments to function `snd_pcm_hw_params_get_channels_min' audio.c:569: too many arguments to function `snd_pcm_hw_params_get_channels_max' audio.c:578: too many arguments to function `snd_pcm_hw_params_get_buffer_size' audio.c:582: too many arguments to function `snd_pcm_hw_params_get_buffer_size_min' audio.c:583: too many arguments to function `snd_pcm_hw_params_get_buffer_size_max' audio.c:605: too many arguments to function `snd_pcm_hw_params_get_rate' audio.c:605: too many arguments to function `snd_pcm_hw_params_get_rate_min' audio.c:605: too many arguments to function `snd_pcm_hw_params_get_rate_max' audio.c:606: too many arguments to function `snd_pcm_hw_params_get_buffer_time' audio.c:606: too many arguments to function `snd_pcm_hw_params_get_buffer_time_min' audio.c:606: too many arguments to function `snd_pcm_hw_params_get_buffer_time_max' audio.c:607: too many arguments to function `snd_pcm_hw_params_get_periods' audio.c:607: too many arguments to function `snd_pcm_hw_params_get_periods_min' audio.c:607: too many arguments to function `snd_pcm_hw_params_get_periods_max' audio.c:612: warning: passing arg 2 of `snd_pcm_hw_params_get_period_size' from incompatible pointer type audio.c:612: too many arguments to function `snd_pcm_hw_params_get_period_size' audio.c:616: warning: passing arg 2 of `snd_pcm_hw_params_get_period_size_min' from incompatible pointer type audio.c:616: too many arguments to function `snd_pcm_hw_params_get_period_size_min' audio.c:617: warning: passing arg 2 of `snd_pcm_hw_params_get_period_size_max' from incompatible pointer type audio.c:617: too many arguments to function `snd_pcm_hw_params_get_period_size_max' audio.c:624: too many arguments to function `snd_pcm_hw_params_get_period_time' audio.c:624: too many arguments to function `snd_pcm_hw_params_get_period_time_min' audio.c:624: too many arguments to function `snd_pcm_hw_params_get_period_time_max' audio.c:625: too many arguments to function `snd_pcm_hw_params_get_tick_time' audio.c:625: too many arguments to function `snd_pcm_hw_params_get_tick_time_min' audio.c:625: too many arguments to function `snd_pcm_hw_params_get_tick_time_max' audio.c: In function `ALSA_WaveInit': audio.c:744: too many arguments to function `snd_pcm_hw_params_get_rate_min' audio.c:745: too many arguments to function `snd_pcm_hw_params_get_rate_max' audio.c:746: too many arguments to function `snd_pcm_hw_params_get_channels_min' audio.c:747: too many arguments to function `snd_pcm_hw_params_get_channels_max' audio.c:851: too many arguments to function `snd_pcm_hw_params_get_rate_min' audio.c:852: too many arguments to function `snd_pcm_hw_params_get_rate_max' audio.c:853: too many arguments to function `snd_pcm_hw_params_get_channels_min' audio.c:854: too many arguments to function `snd_pcm_hw_params_get_channels_max' audio.c: In function `wodPlayer_DSPWait': audio.c:1200: too many arguments to function `snd_pcm_hw_params_get_period_time' audio.c: In function `wodOpen': audio.c:1721: warning: passing arg 3 of `snd_pcm_hw_params_set_rate_near' makes integer from pointer without a cast audio.c:1733: warning: passing arg 3 of `snd_pcm_hw_params_set_buffer_time_near' makes integer from pointer without a cast audio.c:1735: warning: passing arg 3 of `snd_pcm_hw_params_set_period_time_near' makes integer from pointer without a cast audio.c:1739: warning: passing arg 2 of `snd_pcm_hw_params_get_period_size' from incompatible pointer type audio.c:1739: too many arguments to function `snd_pcm_hw_params_get_period_size' audio.c:1740: too many arguments to function `snd_pcm_hw_params_get_buffer_size' audio.c: In function `DSDB_MMAPCopy': audio.c:2252: too many arguments to function `snd_pcm_hw_params_get_channels' audio.c:2253: too many arguments to function `snd_pcm_hw_params_get_format' audio.c:2255: warning: passing arg 2 of `snd_pcm_hw_params_get_period_size' from incompatible pointer type audio.c:2255: too many arguments to function `snd_pcm_hw_params_get_period_size' audio.c: In function `DSDB_CreateMMAP': audio.c:2306: too many arguments to function `snd_pcm_hw_params_get_format' audio.c:2307: too many arguments to function `snd_pcm_hw_params_get_buffer_size' audio.c:2308: too many arguments to function `snd_pcm_hw_params_get_channels' audio.c: In function `IDsDriverBufferImpl_GetPosition': audio.c:2463: warning: passing arg 2 of `snd_pcm_hw_params_get_period_size' from incompatible pointer type audio.c:2463: too many arguments to function `snd_pcm_hw_params_get_period_size' audio.c: In function `widOpen': audio.c:3211: warning: passing arg 3 of `snd_pcm_hw_params_set_rate_near' makes integer from pointer without a cast audio.c:3224: warning: passing arg 3 of `snd_pcm_hw_params_set_buffer_time_near' makes integer from pointer without a cast audio.c:3226: warning: passing arg 3 of `snd_pcm_hw_params_set_period_time_near' makes integer from pointer without a cast audio.c:3231: warning: passing arg 2 of `snd_pcm_hw_params_get_period_size' from incompatible pointer type audio.c:3231: too many arguments to function `snd_pcm_hw_params_get_period_size' audio.c:3232: too many arguments to function `snd_pcm_hw_params_get_buffer_size' make[2]: *** [audio.o] Fehler 1 make[2]: Verlassen des Verzeichnisses ?/home/sao2l02/Wine/wine/dlls/winmm/winealsa½ make[1]: *** [winmm/winealsa] Fehler 2 make[1]: Verlassen des Verzeichnisses ?/home/sao2l02/Wine/wine/dlls½ make: *** [dlls] Fehler 2 sao2l02@x2l:~/Wine/wine>

3 2

Re: Audit the buttons code
by Dmitry Timoshkov 05 Oct '04

05 Oct '04

"Dimitrie O. Paun" <dpaun(a)rogers.com> wrote: > + * This code was audited for completeness against the documented features > + * of Comctl32.dll version 6.0 on Oct. 3, 2004, by Dimitrie O. Paun. "Button" is a built-in user32 control and has nothing to do with comctl32 at all. Same for all other controls in the dlls/user/ subdirectory. -- Dmitry.

5 20

building on P3 for a P2
by Carl Karsten (435025) 05 Oct '04

05 Oct '04

I want to run wine on a P2 laptop that doesn't have compiler and such installed. I have a P3 box that does. I looked over the results of ./configure and didn't see anything that looked like it had turned on any P3 specific options. The plan is to compile on the p3 then on the P2 nfs mount the wine source dir and run make install. Is this a good plan? Carl Karsten -- http://www.personnelware.com/carl/resume.html

2 1

Re: Compiling Wine with MSVC
by Brian Vincent 05 Oct '04

05 Oct '04

On Tue, 05 Oct 2004 11:10:45 +0100, Martin Fuchs <martin-fuchs(a)gmx.net> wrote: > OK, here is the next problem. > The tool msvcmaker prints the following error messages: > > $ tools/winapi/msvcmaker > Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmaker line 52. I took a stab at this a few months ago, then Steven Edwards posted a patch that supposedly fixes it: http://www.winehq.com/hypermail/wine-devel/2004/05/0476.html I never got a chance to try it out, but if it works it's probably worth forwarding to wine-patches. -Brian

1 0

Compiling Wine with MSVC
by Martin Fuchs 05 Oct '04

05 Oct '04

OK, here is the next problem. The tool msvcmaker prints the following error messages: $ tools/winapi/msvcmaker Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmaker line 52. Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmaker line 116. Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmaker line 441. Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmaker line 1031. Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmaker line 1091. Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmaker line 1141. Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmaker line 1183. Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmaker line 1220. Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmaker line 1237. Execution of tools/winapi/msvcmaker aborted due to compilation errors. My perl version used is the current one of Cygwin: v5.8.5

2 2

Compiling Wine on Cygwin/with MSVC
by Martin Fuchs 05 Oct '04

05 Oct '04

Hello, when trying to compile WINE using Cygwin I am getting errors such as: (this example for wine/programs/notepad) gcc -c -I. -I. -I../../include -I../../include -I../../include/msvcrt -DNO_LIBWINE_PORT -D_REENTRANT -Wall -pipe -mprefe rred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o License_En.o License_En.c In file included from /usr/include/w32api/objfwd.h:7, from /usr/include/w32api/objidl.h:7, from ../../include/objbase.h:270, from ../../include/ole2.h:25, from ../../include/windows.h:77, from License_En.c:1: /usr/include/w32api/basetyps.h:124: error: Syntaxfehler before '*' token /usr/include/w32api/basetyps.h:125: error: Syntaxfehler before '*' token /usr/include/w32api/basetyps.h:127: error: Syntaxfehler before '*' token In file included from ../../include/objbase.h:270, from ../../include/ole2.h:25, from ../../include/windows.h:77, from License_En.c:1: /usr/include/w32api/objidl.h:10: error: Syntaxfehler before "LPOLESTR" I configured with "configure --disable-win16". When trying to compile parts of WINE using MSVC, I'm getting: Compiling... comctl32undoc.c d:\wine-msvc\include\windows.h(23) : fatal error C1189: #error : Wine should not include windows.h internally This all worked some months ago. Can someone explain, what's wrong here? Thanks, Martin

4 6

RE: fixed bug in shell32
by Rolf Kalbermatter 05 Oct '04

05 Oct '04

>@@ -163,10 +163,10 @@ > else > ret = (SHNotifyDeleteFileA(szTemp) == ERROR_SUCCESS); > } while (ret && FindNextFileA(hFind, &wfd)); >+ FindClose(hFind); >+ if (ret) >+ ret = (SHNotifyRemoveDirectoryA(pszDir) == ERROR_SUCCESS); > } >- FindClose(hFind); >- if (ret) >- ret = (SHNotifyRemoveDirectoryA(pszDir) == ERROR_SUCCESS); > return ret; > } This create a FindFile handle leak if the user chooses to abort the delete operation. Rolf Kalbermatter

1 0

Re: Contributing to WINE
by Shachar Shemesh 05 Oct '04

05 Oct '04

Hi Ronald, I cannot stress this point enough. Wine is a community project. Everyone involved in the Wine project would appreciate a chance to answer your questions, as well as hear what you have to say. Sometimes there is a need to establish private communication with certain people. As a rule, however, all technical guidance and discussions should be done on the mailing list. This way, everyone gets a chance to respond to your inquiries. Also, it appears that many participants of this list, as well as the web mail archive, are having problems with the format in which you send your emails. Please try to send mail to this list in plain text format. The format in which you sent me seems to be ok, but I cannot say for sure. Ronald Robin wrote: >Hi Shachar, thank you for your response to my post. I am sorry for several >things: First, that we have not tried posting to this mailing list before. >We thought before that it would be better to establish communications first >with the person who leads the project (i.e. Mr. Julliard). I guess that was >my mistake. Second, that it took me a long time to respond back to you. >You've been a great help. Thank you for the suggestions that you gave. I'm >sure it would be most helpful in case we would need to hire some more help >in the future. > >Anyway, I'd like to introduce myself again. I'm Ronald Robin of SpecOpS >Labs. I am the Project Manager for the David Project. I'm in charge of >managing the research and development efforts within our lab as well as >those done by our partner universities an institutions including the the >National Computer Center, De Lasalle University, and Ateneo de Manila >Univesity here in the Philippines. > >As mandated by our President & CEO, Frederick Lewis and our CTO, Peter >Valdez, we are glad to announce to you that one of my team's newer >objectives is to regularly contribute to the WINE Community. To get things >started with, I can assign some of our developers to focus working on >something we can proudly contribute to the WINE community. We may not be >able to dedicate a significant number of them, but it’s a start. > > Any development you can put towards the wine project would be appreciated and welcomed. >I was wondering, is it ok for me to ask you some more questions? > > Better yet, ask everyone the questions. This way, you will get answers even if I happen to be busy, or not know the answer. >I believe you're one of the best persons right now to help us get some ideas >as to what particular problem areas we can focus our contribution efforts >on. It would be really nice if my team can contribute something significant >to the community. > > While I thank you for the complement, this is not how things usually work in a free software project. As you may know, Wine has several areas that could use a developer's attention. We don't know much about your company, so it would be hard to know what areas would be best for you to contribute in. First off, we would all appreciate if you sent any code you happen to change in Wine while working on David anyways. This basic form of contribution is usually the easiest for you to do. As for general areas of improvements in Wine, there are a few. Development there had better be coordinated with the people already working on these things. Probably the area most needing tender love and care is DCOM. While people are currently working on it, we still depend on Microsoft's DLLs in that area, which is not a good thing. Another place that could use enhancement is MSI. Personally, I also want to see better BiDi support, but that's something not many of the list's members care about as much as I. I'm sure other list members will be happy to fill in other areas where your help would be most appreciated. >Thanks again. > > Any time. >Cheers! > >Ronald Robin > > Shachar -- Shachar Shemesh Lingnu Open Source Consulting ltd. http://www.lingnu.com/

1 0

wctype
by Ge van Geldorp 05 Oct '04

05 Oct '04

I compared the results of CT_CTYPE1 GetStringTypeW() between Windows 2000 and Wine and found a lot of differences (about 12000 of them). Nothing really spectacular, e.g. codepoint 0x00b5 (MICRO SIGN) is classified C1_PUNCT in Win2k and (C1_ALPHA | C1_LOWER) in Wine. I noticed that the Wine table is generated from information on ftp.unicode.org, so I'm wondering if the table generation is correct or if Microsoft made some strange choices? Gé van Geldorp.

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel