August 2007 - Wine-Devel - list.winehq.org

Re: [oleaut32/tests] Error when running tests on Wine, anyone?

by Paul Vriens

Alexandre Julliard wrote: > Paul Vriens <paul.vriens.wine(a)gmail.com> writes: > >> Hi, >> >> Can somebody confirm if all oleaut32 tests run correctly on Wine. > > All the tests that are in the tree run correctly, at least on my > box. Tests that fail for me don't get committed. > I know that. I just hoped somebody had a failure as well. That way it's easier to look for the issue/fix. Anything that could influence that test? Cheers, Paul.

Aug. 10, 2007

Re: [oleaut32/tests] Error when running tests on Wine, anyone?

by Alexandre Julliard

Paul Vriens <paul.vriens.wine(a)gmail.com> writes: > Hi, > > Can somebody confirm if all oleaut32 tests run correctly on Wine. All the tests that are in the tree run correctly, at least on my box. Tests that fail for me don't get committed. -- Alexandre Julliard julliard(a)winehq.org

Aug. 10, 2007

Re: [Winetest RFI] What do you want out of the test suite?

by Juan Lang

> I just want to get people's opinion(s) about the needs/requirements/whishes for > both the conformance tests themselves (including winetest) as well as the webpages. That's too broad a question, I think. "No answer" could mean, "don't use it," or it could mean, "it already does what I want." --Juan

Aug. 10, 2007

Re: [MSI/tests] ConvertSidToStringSid not available on win98/NT4

by Juan Lang

> Thats not exactly what I meant, I think. This Kerberos support comes > from extra functions > in secur32.dll right? The tests then will notice that there is no > Kerberos support and not > run Kerberos tests. Am I mistaken? You are mistaken. The same functions exist in Windows NT4 (they're in security.dll rather than secur32.dll, but the exports are the same.) You ask for a provider by name, and the Kerberos provider exists in Windows 2000 and up, but not in NT4. That doesn't mean that the tests couldn't use skip if Kerberos isn't available. --Juan

Aug. 10, 2007

[oleaut32/tests] Error when running tests on Wine, anyone?

by Paul Vriens

Hi, Can somebody confirm if all oleaut32 tests run correctly on Wine. I'm trying to change LoadLibrary to GetModuleHandle and though it was my failure, but current GIT fails for me: ../../../tools/runtest -v -P wine -M oleaut32.dll -T ../../.. -p oleaut32_test.exe.so vartest.c && touch vartest.ok fixme:variant:VarMod Could not convert left type 4096 to 20? rc == 0x80020008 fixme:variant:VarMod Could not convert left type 8192 to 20? rc == 0x80020008 fixme:variant:VarMod Could not convert left type 16384 to 20? rc == 0x80020008 vartest.c:3128: Test failed: got VT_DATE(-1.5) expected VT_DATE(-1.4) vartest.c:3129: Test failed: got VT_R8(-1.5) expected VT_R8(-1.4) vartest: 1031879 tests executed (0 marked as todo, 2 failures), 0 skipped. make: *** [vartest.ok] Error 2 Cheers, Paul.

Aug. 10, 2007

Re: [2/2] winex11: Don't use context-specific info when initializing

by Roderick Colenbrander

I would like to keep this GL_RENDERER/GL_VENDOR stuff around although it might not be 100% correct in all cases (on some cards there's indeed a difference between direct and indirect rendering). To be correct also add similar code to the glx context creation code. Roderick On Friday 10 August 2007 11:29, Chris Robinson wrote: > Doesn't make much sense to use info from a temporary context when the > context the app eventually sets may be different (such is the case for > direct vs. indirect rendering on certain drivers, or multiple > screens/output devices).

Aug. 10, 2007

[Winetest RFI] What do you want out of the test suite?

by Paul Vriens

Hi, I just want to get people's opinion(s) about the needs/requirements/whishes for both the conformance tests themselves (including winetest) as well as the webpages. I'll collect the information and will put it on the wiki. Cheers, Paul.

Aug. 10, 2007

[programs] add winerun for starting programs from wine.desktop

by Kirill K. Smirnov

>+/* >+ * Wordpad implementation >+ * >+ * Copyright 2007 by Damjan Jovanovic >+ * It is not wordpad, is it? >+ ok = CreateProcessW(exePath, NULL, NULL, NULL, FALSE, 0, NULL, currentDirectory, >+ &startupInfo, &processInfo); This code does not run console apps correctly (use CREATE_NEW_CONSOLE flag). -- Kirill

Aug. 10, 2007

Re: [2/2] winex11: Don't use context-specific info when initializing

by Chris Robinson

On Friday 10 August 2007 02:35:59 am Christoph Frick wrote: > On Fri, Aug 10, 2007 at 02:29:49AM -0700, Chris Robinson wrote: > > @@ -137,7 +132,7 @@ typedef struct wine_glpbuffer { > } Wine_GLPBuffer; > > static Wine_GLContext *context_list; > -static struct WineGLInfo WineGLInfo = { 0 }; > +static struct WineGLInfo WineGLInfo; > static int use_render_texture_emulation = 1; > static int use_render_texture_ati = 0; > static int swap_interval = 1; > > why is this changed? its a Good Thing to have global structs initialized so > they fail earlier under abuse. The first field was changed from a const char* to an int[2], so it'd at least need to be changed to { { 0 } } to avoid compiler warnings. But considering it's global, and global variables are automatically cleared to 0, there's no need to be explicit about setting it to 0.

Aug. 10, 2007

Re: [1/2] winex11: NV_texture_rectangle and NV_vertex_array_range do not have WGL extension names

by Roderick Colenbrander

Both are 'fake' WGL extensions. I agree that no string should be displayed in either case and that we don't need a check for NV_texture_rectangle. The loading of the NV vertex array range stuff depending on the presence of the GL extension of which it is part is fine. Yes, GL extensions are context dependend but relying on glXGetProcAddress is even more evil (as it doesn't have to return NULL). Upto now I haven't seen problems with this. On Friday 10 August 2007 11:15, Chris Robinson wrote: > This patch and the next are designed to remove the need for > context-specific information taken from a temporary context. For this one, > the aforementioned extensions don't have WGL extension names. Their > respective specs and a recent nvidia card/driver's WGL extension output > confirms this.

Aug. 10, 2007