wine-devel December 2004

wine-devel@winehq.org

127 participants
276 discussions

Wine CVS still broken
by Florian Goth 08 Dec '04

08 Dec '04

I deleted my wine - folder and did a full cvs checkout today(23:00 CET ) But there's still a problem in winejack: The previously reported errors seem to be away 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 -O2 -march=athlon-xp -m32 -mmmx -m3dnow -msse -ftracer -funroll-loops -fpeel-loops -funswitch-loops -fweb -funit-at-a-time -o winejack.drv.dbg.o winejack.drv.dbg.c ../../../tools/winegcc/winegcc -B../../../tools/winebuild -shared ./winejack.drv.spec audio.o jack.o winejack.drv.dbg.o -o winejack.drv.so -L../../../dlls -lwinmm -luser32 -lkernel32 -L../../../libs/wine -lwine -ldxguid -luuid -L../../../libs/port -lwine_port audio.o(.text+0x22fe): In function `JACK_WaveInit': /home/sifff/wine/dlls/winmm/winejack/audio.c:935: undefined reference to `strcpyW' audio.o(.text+0x23de):/home/sifff/wine/dlls/winmm/winejack/audio.c:969: undefined reference to `strcpyW' collect2: ld gab 1 als Ende-Status zurück winegcc: gcc failed. make[2]: *** [winejack.drv.so] Fehler 2 make[2]: Leaving directory `/home/sifff/wine/dlls/winmm/winejack' make[1]: *** [winmm/winejack] Fehler 2 make[1]: Leaving directory `/home/sifff/wine/dlls' make: *** [dlls] Fehler 2

2 1

Re: windows/win.c : add missing styles
by Dmitry Timoshkov 08 Dec '04

08 Dec '04

"Rémi Assailly" <remi.assailly(a)free.fr> wrote: > --- windows/win.c~ 2004-11-29 18:35:46.000000000 +0100 > +++ windows/win.c 2004-12-07 18:04:02.135332008 +0100 > @@ -872,7 +872,6 @@ > if(style & WS_MINIMIZEBOX) TRACE(" WS_MINIMIZEBOX"); > if(style & WS_MAXIMIZEBOX) TRACE(" WS_MAXIMIZEBOX"); > > - /* FIXME: Add dumping of BS_/ES_/SBS_/LBS_/CBS_/DS_/etc. styles */ Don't remove this line, your patch doesn't add dumping of those styles. > #define DUMPED_STYLES \ > (WS_POPUP | \ > WS_CHILD | \ > @@ -882,6 +881,7 @@ > WS_CLIPSIBLINGS | \ > WS_CLIPCHILDREN | \ > WS_MAXIMIZE | \ > + WS_CAPTION | \ This isn't a style you want to add here. > WS_BORDER | \ > WS_DLGFRAME | \ > WS_VSCROLL | \ > @@ -891,7 +891,94 @@ > WS_GROUP | \ > WS_TABSTOP | \ > WS_MINIMIZEBOX | \ > - WS_MAXIMIZEBOX) > + WS_MAXIMIZEBOX | \ > + BS_DEFPUSHBUTTON | \ > + BS_CHECKBOX | \ > + BS_AUTOCHECKBOX | \ > + BS_AUTOCHECKBOX | \ > + BS_3STATE | \ > + BS_AUTO3STATE | \ > + BS_GROUPBOX | \ > + BS_USERBUTTON | \ > + BS_AUTORADIOBUTTON | \ > + BS_OWNERDRAW | \ > + BS_LEFTTEXT | \ > + BS_ICON | \ > + BS_BITMAP | \ > + BS_LEFT | \ > + BS_RIGHT | \ > + BS_CENTER | \ > + BS_TOP | \ > + BS_BOTTOM | \ > + BS_VCENTER | \ > + BS_PUSHLIKE | \ > + BS_MULTILINE | \ > + BS_NOTIFY | \ > + BS_FLAT | \ > + ES_CENTER | \ > + ES_RIGHT | \ > + ES_MULTILINE | \ > + ES_UPPERCASE | \ > + ES_LOWERCASE | \ > + ES_PASSWORD | \ > + ES_AUTOVSCROLL | \ > + ES_AUTOHSCROLL | \ > + ES_NOHIDESEL | \ > + ES_COMBO | \ > + ES_OEMCONVERT | \ > + ES_READONLY | \ > + ES_WANTRETURN | \ > + ES_NUMBER | \ > + SBS_VERT | \ > + SBS_TOPALIGN | \ > + SBS_LEFTALIGN | \ > + SBS_BOTTOMALIGN | \ > + SBS_RIGHTALIGN | \ > + SBS_SIZEBOXTOPLEFTALIGN | \ > + SBS_SIZEBOXBOTTOMRIGHTALIGN | \ > + SBS_SIZEBOX | \ > + SBS_SIZEGRIP | \ > + LBS_NOSEL | \ > + LBS_COMBOBOX | \ > + LBS_STANDARD | \ > + CBS_SIMPLE | \ > + CBS_DROPDOWN | \ > + CBS_DROPDOWNLIST | \ > + CBS_OWNERDRAWFIXED | \ > + CBS_OWNERDRAWVARIABLE | \ > + CBS_AUTOHSCROLL | \ > + CBS_OEMCONVERT | \ > + CBS_SORT | \ > + CBS_HASSTRINGS | \ > + CBS_NOINTEGRALHEIGHT | \ > + CBS_DISABLENOSCROLL | \ > + CBS_UPPERCASE | \ > + CBS_LOWERCASE | \ > + DS_ABSALIGN | \ > + DS_SYSMODAL | \ > + DS_3DLOOK | \ > + DS_FIXEDSYS | \ > + DS_NOFAILCREATE | \ > + DS_LOCALEDIT | \ > + DS_SETFONT | \ > + DS_MODALFRAME | \ > + DS_NOIDLEMSG | \ > + DS_SETFOREGROUND | \ > + DS_CONTROL | \ > + DS_CENTER | \ > + DS_CENTERMOUSE | \ > + DS_CONTEXTHELP | \ > + SS_USERITEM | \ > + SS_LEFTNOWORDWRAP | \ > + SS_OWNERDRAW | \ > + SS_BITMAP | \ > + SS_ENHMETAFILE | \ > + SS_ETCHEDHORZ | \ > + SS_ETCHEDVERT | \ > + SS_ETCHEDFRAME | \ > + SS_TYPEMASK | \ > + SS_WORDELLIPSIS | \ > + SS_ELLIPSISMASK) And where do you dump all the above listed styles? (Just a hint: you can't dump them without looking at the class name, and it won't work for superclassed windows). -- Dmitry.

1 0

Feedback on user manual
by Ross Boylan 08 Dec '04

08 Dec '04

The manual lamented the lack of feedback, so I thought I'd give you some. 1.1.1 says "It tries to target both the new Wine user, by offering a step by step approach, and the experienced Wine user, by offering the reference material mentioned above." Ordinarily, I would expect the novice stuff, followed by reference material. But, judging from the table of contents, this isn't what you've done. It would be good to say how the stuff is arranged. Assuming the novice and expert stuff is interspersed, it might be better to separate them. Yes, I realize that's probably a lot of work. That's why this is only a though :) You might also want to put a date and version number on the documentation; at least on Debian, looking at the html, I don't see it. I'm using wine-doc 0.0.20040716-1.3. Thanks for your work on wine. -- Ross Boylan wk: (415) 502-4031 530 Parnassus Avenue (Library) rm 115-4 ross(a)biostat.ucsf.edu Dept of Epidemiology and Biostatistics fax: (415) 476-9856 University of California, San Francisco San Francisco, CA 94143-0840 hm: (415) 550-1062

3 3

Compiling wine fails
by Florian Goth 07 Dec '04

07 Dec '04

Patch: http://cvs.winehq.org/patch.py?id=14706 breaks compiling on my system(kernel-2.6.9; gcc 3.4.2 ) Reverting the patch fixes compiling. The patch produces the following Errors: make[2]: Entering directory `/home/sifff/wine/dlls/winmm/winejack' 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 -O2 -march=athlon-xp -m32 -mmmx -m3dnow -msse -ftracer -funroll-loops -fpeel-loops -funswitch-loops -fweb -funit-at-a-time -o audio.o audio.c audio.c: In function `JACK_WaveInit': audio.c:902: Warnung: implizite Deklaration der Funktion »wine_dlsym« audio.c:902: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung audio.c:903: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung audio.c:904: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung audio.c:905: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung audio.c:906: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung audio.c:907: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung audio.c:908: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung audio.c:909: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung audio.c:910: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung audio.c:911: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung audio.c:912: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung audio.c:913: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung audio.c:914: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung audio.c:915: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung audio.c:916: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung audio.c:934: Warnung: implizite Deklaration der Funktion »strcpyW« audio.c:998: Warnung: implizite Deklaration der Funktion »wine_dlclose« audio.c: In function `wodDevInterfaceSize': audio.c:1682: Warnung: implizite Deklaration der Funktion »MultiByteToWideChar« audio.c:1682: Fehler: »CP_ACP« nicht deklariert (erste Benutzung in dieser Funktion) audio.c:1682: Fehler: (Jeder nicht deklarierte Bezeichner wird nur einmal aufgeführt audio.c:1682: Fehler: für jede Funktion in der er auftritt.) audio.c: In function `wodDevInterface': audio.c:1692: Fehler: »CP_ACP« nicht deklariert (erste Benutzung in dieser Funktion) audio.c: In function `widDevInterfaceSize': audio.c:2428: Fehler: »CP_ACP« nicht deklariert (erste Benutzung in dieser Funktion) audio.c: In function `widDevInterface': audio.c:2438: Fehler: »CP_ACP« nicht deklariert (erste Benutzung in dieser Funktion) make[2]: *** [audio.o] Fehler 1 make[2]: Leaving directory `/home/sifff/wine/dlls/winmm/winejack' make[1]: *** [winmm/winejack] Fehler 2 make[1]: Leaving directory `/home/sifff/wine/dlls' make: *** [dlls] Fehler 2

3 2

Fwd:[Fwd: [AppDB] Status Report]
by Ivan Leo Puoti 07 Dec '04

07 Dec '04

Can someone working on appdb fix this? Ivan. ____________________________________________________________ Libero ADSL: 3 mesi gratis e navighi a 1.2 Mega, senza costi di attivazione. Abbonati subito su http://www.libero.it

1 0

Re: No more winrash?
by Ferenc Wagner 07 Dec '04

07 Dec '04

Jakob Eriksson <jakov(a)vmlinux.org> writes: > Do you agree, should we stop using winrash? > > "Dmitry Timoshkov" <dmitry(a)baikal.ru> wrote: > >> "Jakob Eriksson" <jakov(a)vmlinux.org> wrote: >> >>> Well, I tried now marking the service as interactive, >>> but that didn't make any difference. >>> >>> So, what follows, deprecate Winrash? >> >> If it really breaks the tests then definitely yes. I think it does provide much useful information which would be largely lost if we resorted to manual testing. What's more, winetest is not really up to that, as it doesn't ask for a tag but relies on a command line option which people would tend to forget. What I propose: make winetest detect whether it's running on an interactive desktop or not, and include this info in the header just like bRunningUnderWine. Meanwhile add the tag dialog to winetest and separate or mark the different reports on the webpage for easier reference. That would bring us the best of both worlds. Or possibly tweak the sensitive tests (how many are there?) to make clear in the output that they were not run for this reason... That would probably require a new field in the final report (ie. success-failure-todo-skipped or similar). This could also signal WINETEST_INTERACTIVE tests so that they aren't forgotten about... That said, I don't know much of this desktop business, so I'm not sure how to put the detection logic in. The rest should not be hard, I hope I'll find the time for them if we decide to go this way. -- Feri.

4 3

Re: Shell about box
by Dmitry Timoshkov 07 Dec '04

07 Dec '04

"Ge van Geldorp" <gvg(a)reactos.com> wrote: > Changelog: > Klemens Friedl <frik85(a)hotmail.com> > - Design Shell About dialog more Windows-like The patch will not apply since it's utf-8 encoded. -- Dmitry.

1 0

Re: Implemented CreateAsyncBindCtx
by Alexandre Julliard 07 Dec '04

07 Dec '04

Jacek Caban <jack(a)itma.pwr.wroc.pl> writes: > It's my tiny bug. RegsterObjectParam can fail only with E_OUTOFMEMORY > here, so checking it's return is > really not important, but to be correct at all, hres should be just > returned. No, that's worse than before, now you return an error while still allocating the object. You need to cleanup the allocated context when returning a failure. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: Help with some strange debugging.
by Jon Griffiths 07 Dec '04

07 Dec '04

Hi Oliver, >I've also got a little patch for oleaut/varient.c to >allow number-string comparisons. There are a couple of >undocumented assumptions I've made,like what to return >for an empty of if the string isn't a number, and the >only thing I've been able to test with is 1 vb >application as I don't have windows, should I post it >to this list or to patch? If you need to test how the native dll works, please write a unit test case for the comparasons you are interested in (there are a _huge_ number of variant tests already defined in the dlls/oleaut32/tests directory). Run the tests manually from the tests directory as: WINEDLLOVERRIDES="oleaut32=n" wine ./oleaut32test.exe.so <testname> To check out the native versions behaviour (of course you will need a native oleaut32.dll in your fake c:\windows\system dir). for the builtin version run: WINETEST_PLATFORM="wine" WINEDLLOVERRIDES="oleaut32=b" wine ./oleaut32test.exe.so <testname> This will catch any regressions from your patch and ensure that future changes don't break your changes in any way. Cheers, 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!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com

1 0

Re: Providing success stories
by Dan Kegel 07 Dec '04

07 Dec '04

Stefan Munz wrote: > In order to push the use of Open Source Software we plan a project with the > "Wirtschaftsförderung Region Stuttgart GmbH" ... to > find software producers who pay us for a wine compatibility test of their > software. ... What's the URL, by the way? Is it http://opensource.region-stuttgart.de/ ? > This project is starting at the moment. I thought a good idea to give > something back to the community is to provide some success stories i.e. for > use on winehq.com. Is this interesting? Yes. I don't see anything on winehq.com like that, but http://www.codeweavers.com/site/products/case_studies seems to be along the lines you're thinking of, maybe? Try just writing up a first draft of a success story on a web page somewhere, and post a link to wine-devel so we can see what you're thinking of. Then I'm sure getting it onto winehq.org will be easy. - Dan -- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html

3 3

← Newer
1
...
18
19
20
21
22
23
24
...
28
Older →

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 December 2004