- Wine-Devel - list.winehq.org

Re: [PATCH] setkey breaks FreeBSD
by Mike Hearn Oct. 18, 2004

Oct. 18, 2004

Anish Mistry wrote: > The attached patch fixes a CVS build problem with confilicting setkey in the > stdlib.h header. It's changed to WINE_setkey. I've gone ahead and changed > getkey to match. Aesthetics wise, I'd rather it was renamed to eg setcfgkey or something - there are no WINE_ prefixes in winecfg and none are needed, I'd rather keep it that way. thanks -mike

3 3

Re: ez-cdda sleep
by Mike Hearn Oct. 18, 2004

Oct. 18, 2004

>> - storing context in server while entering USR1 signal handler (to be >> done without races, which will require some more work, as the server >> doesn't synchronize with the USR1 handler) I've implemented this in my local tree, and it works fine: Easy CD-DA gets further now. It is still being nailed by the copy protection system (called "Armadillo" apparently) but the splash screen appears now :) Today the BT engineer reconnected our line. So, now I just have to wait for ADSL to be activated, then I can flush my patch queue and get back to some real work. To eliminate the race at the top of SIGUSR1 handler I made server get_thread_context/set_thread_context RPCs fail with STATUS_RETRY if the context has not yet been uploaded, and adjusted the ntdll code to spin in a loop yielding the timeslice whenever it receives STATUS_RETRY. It's not fancy but it works, and on average only 1 yield is needed (obvious in hindsight I guess). The SIGCONTEXT is reloaded when the context override is cancelled, so set_thread_context on a suspended thread works as expected. thanks -mike

1 0

Problem using winelib
by Ross Quinlan Oct. 18, 2004

Oct. 18, 2004

Hello, This is my first try with winelib ... I'm running RedHat 7.3. I've downloaded the wine source (wine-20040914) and built everything using ./tools/wineinstall. I'm trying the winemine example in the winelib doc. I've copied the .c, .h, and .rc files to a new directory winemine2 and in that directory I've run winemaker as follows: E> winemaker --lower-uppercase . Winemaker 0.6.0 Copyright 2000 Francois Gouget <fgouget(a)codeweavers.com> for CodeWeavers Scanning the source directories... Fixing the source files... dialog.c main.c De.rc En.rc Es.rc Fr.rc It.rc Nl.rc Pl.rc Pt.rc Ru.rc Si.rc rsrc.rc dialog.h main.h resource.h Generating project files... . This generates one new file, "Makefile" (no Makefile.in, configure) so I can't run ./configure --with-wine etc. If I try a simple make, here's the result: E> make all winebuild -o winemine2.exe.dbg.c --debug -C. dialog.c main.c winegcc -c -mno-cygwin -I. -o winemine2.exe.dbg.o winemine2.exe.dbg.c winegcc -c -mno-cygwin -I. -o dialog.o dialog.c winegcc -c -mno-cygwin -I. -o main.o main.c wrc -I. -foDe.res De.rc De.rc:22:21: Error: parse error make: *** [De.res] Error 1 I'm therefore contacting this address as suggested in the winemaker documentation. Any help for a complete novice would be appreciated! Regards, Ross

3 2

Fwd: Re: Fwd: Re: about a book I'm thinking of writing
by Wesley Parish Oct. 18, 2004

Oct. 18, 2004

This is in relation to an idea I had a few months ago. Bruce Perens stated that he didn't see any future at present for a book on ReactOS, but he would definitely be interested in a book on Win internals, from one of the Wine developers. Is there anyone on this list who'd be interested? FWIW, I'd be willing to edit, if necessary. (That's something I'm not unfamiliar with.) Wesley Parish ---------- Forwarded Message ---------- Subject: Re: Fwd: Re: about a book I'm thinking of writing Date: Mon, 18 Oct 2004 13:53 From: Alexandre Julliard <julliard(a)winehq.org> To: Wesley Parish <wes.parish(a)paradise.net.nz> Wesley Parish <wes.parish(a)paradise.net.nz> writes: > I wrote an email to Bruce Perens on doing something for the ReactOS > project, and he sent me this reply. Do you think there'd be anyone in the > Wine HQ who'd be interested and capable of writing a book on the Wine > internals a la "Inside Windows NT" or "VAX/VMS Internals and Data > Structures", or suchlike? I don't know of anyone, but you may want to ask this on the wine-devel list. -- Alexandre Julliard julliard(a)winehq.org ------------------------------------------------------- -- Wesley Parish * * * Clinersterton beademung - in all of love. RIP James Blish * * * Mau e ki, "He aha te mea nui?" You ask, "What is the most important thing?" Maku e ki, "He tangata, he tangata, he tangata." I reply, "It is people, it is people, it is people."

1 0

Appdb - Add 'Delete' button to comments when the user is an admin
by Chris Morgan Oct. 18, 2004

Oct. 18, 2004

This patch adds a delete button to comments when the user is an admin. It will need to be modified slightly when application maintainers are added to appdb. The hope is that we can start to clear the stale comments out of the database to increase the signal-to-noise. After deleting the comment the parentId of the child comments are adjusted to be the parentId of the deleted comment. I'm still a php rookie, comments, questions are welcome ;-) Chris

1 0

Re: Temporary fix to trying to put a pointer in a DWORD
by Dmitry Timoshkov Oct. 17, 2004

Oct. 17, 2004

"Vincent Béron" <vberon(a)mecano.gme.usherb.ca> wrote: > We try to put a pointer in a DWORD in a static initialization of > CRITICAL_SECTION_DEBUGs. Of course it doesn't work on Win64. We'll have > to find a better solution though. Another way to fix it is to use full 'DWORD Spare[2]' to store a pointer on Win64 and leave it as it is now for Win32. -- Dmitry.

3 4

Re: Fix various function prototypes
by Rolf Kalbermatter Oct. 17, 2004

Oct. 17, 2004

Vincent Béron wrote: >MSDN says it's void >http://msdn.microsoft.com/library/default.asp?url=/library/en- >us/shellcc/platform/shell/reference/functions/shcocreateinstance.asp > >I don't have latest PSDK. > >This will need to be investigated some more (although I'm leaning >towards HRESULT). My own tests seem to indicate that the function really returns some codes which are consistent with HRESULTs. Also my SDK (from February 2003) declares the functions as SHSTDAPI which is an abbreviation for "extern HRESULT __stdcall". So MSDN seems to be wrong here and besides returning them anyhow in the implementation eventhough some clients may ignore them based on MSDN documentation seems the correct way to me! Rolf Kalbermatter

1 0

Re: Enable _WIN64
by Robert Shearman Oct. 17, 2004

Oct. 17, 2004

Vincent Béron wrote: >Index: wine/dlls/oleaut32/oaidl_p.c >=================================================================== >RCS file: /home/wine/wine/dlls/oleaut32/oaidl_p.c,v >retrieving revision 1.4 >diff -u -r1.4 oaidl_p.c >--- wine/dlls/oleaut32/oaidl_p.c 7 Oct 2004 03:06:49 -0000 1.4 >+++ wine/dlls/oleaut32/oaidl_p.c 16 Oct 2004 04:50:00 -0000 >@@ -11119,7 +11119,7 @@ > }; > > >-#if !defined(__RPC_WIN32__) >+#if !defined(__RPC_WIN32__) && !defined(__RPC_WIN64__) > #error Invalid build platform for this stub. > #endif > > > oaidl.idl needs to be regenerated from a newer MIDL that knows about Win64 instead of this hack. Rob

1 0

Re: Fix various function prototypes
by Robert Shearman Oct. 17, 2004

Oct. 17, 2004

Vincent Béron wrote: >SHCoCreateInstance returns void, not HRESULT. >Some functions had a different prototype than their declaration. > >Changelog: >Fix various function prototypes. > > Some of these are wrong if we want binary compatibility with Windows 64-bit because e.g.: sizeof(unsigned long) on linux != sizeof(unsigned long) on Windows If a parameter to a function is "unsigned long" then we will have to change it to "ULONG" instead. Rob

1 0

Re: Freetype portability fix for older versions - improved
by Rein Klazes Oct. 17, 2004

Oct. 17, 2004

On 15 Sep 2004 11:17:10 -0400, you wrote: > Tested on both freetype 2.1.2 and freetype 2.1.4. > > Changelog: > Use the preferred FT_ENCODING values rather than ft_encoding. > > +#ifndef FT_ENCODING_NONE > +#define FT_ENCODING_NONE ft_encoding_none > +#endif > +#ifndef FT_ENCODING_MS_SYMBOL > +#define FT_ENCODING_MS_SYMBOL ft_encoding_symbol > +#endif > +#ifndef FT_ENCODING_UNICODE > +#define FT_ENCODING_UNICODE ft_encoding_unicode > +#endif > +#ifndef FT_ENCODING_APPLE_ROMAN > +#define FT_ENCODING_APPLE_ROMAN ft_encoding_apple_roman > +#endif The patch works, but is not quite correct and doing the opposite of what you claim: the FT_ENCODING's are never defined but are enums. Therefore "ifndef FT_ENCODING_XYZ" is always true and you always use the depreciated ft_encodings. On old freetype2: enum FT_Encoding { ft_encoding_xyz, ... On Newer freetype2: enum FT_Encoding { FT_ENCODING_XYZ, ... #define ft_encoding_xyz FT_ENCODING_XYZ So to use FT_ENCODING_XYZ in the code and still compile with older freetype2's, we need to test: #ifndef ft_encoding_xyz Patch attached, tested to compile with freetype 2.0.9 and 2.1.7. Changelog: dlls/gdi : freetype.c Test whether the ft_encoding's are defined, not the FT_ENCODING's. Rein. -- Rein Klazes rklazes(a)xs4all.nl

1 0