wine-devel November 2003

wine-devel@winehq.org

121 participants
276 discussions

Re: Default printer and patch management
by Ivan Leo Murray-Smith 27 Nov '03

27 Nov '03

For all wine files that contain code written by others: >a) Just keep them "secret" until I get paid, at which point I send them >in all together. Pros: Simple, Cons: people might duplicate my work. Good idea >b) Notify the Wine community of what the patches do/are but keep their >contents secret. LGPL violation, if you give your customer a LGPL'ed binary of wine, you must give them (Or at least offer them) access to the source, and you can't legally stop him/them from sending the code to wine-patches (Even if he/they may not have any interest in doing so) >c) Post them all to wine-devel but under a license that prevents them >being merged unless you get a special exception from me. That way people >can see, peer review the patches etc but they don't get committed. Of >course, as this is just supposed to be insurance anyway, that seems a >bit worthless. Obvious and explicit LGPL violation. >d) Say "screw it", submit as usual and just hope I'm dealing with >trustworthy people (unfortunately no contract in this case, the job >isn't really big enough to warrant one). Probably in your interest to opt for A, you can never be sure. Of course, if the code you've written is just say a dll that's linked to/by wine,and you're the only author of that file/dll/whatever, you can even keep if proprietary and choose options b or c or just keep the code totally secret(That's what Transgaming and Codeweavers do). Alternatively, you can ask the copyright holders of the files you've modified for a special license that allows commercial use, in this case you can keep the code closed, and opt for b or d, or keep the code totally secret. Have a good look at http://www.gnu.org/licenses/lgpl.txt

1 0

compiler warnings
by Ivan Leo Murray-Smith 27 Nov '03

27 Nov '03

The current code compiles with a few warnings, in the attachment. BTW you can see how code degenerates rapidly when it's not free software any more, probably 10% of all the output when compiling winex 3.2 is compiler warnings.

1 0

Re: Prevent wildcards from being accepted in filenames (NT mode)
by Dmitry Timoshkov 27 Nov '03

27 Nov '03

"Shachar Shemesh" <wine-patches(a)shemesh.biz> wrote: > + /* If wer'e in NT mode - don't allow wildcards in file name */ > + if( (strchrW(name, '?') || strchrW(name, '*')) && (GetVersion()&0x80000000)==0 ) (GetVersion() & 0x80000000)==0) construct is very inefficient. It forces compiler generate both a bit mask test and a comparison operation. While many modern processors have very effective bit test instructions, and we have to tell to the compiler that we want only a bit test. Simple !(GetVersion() & 0x80000000) is much better IMO. -- Dmitry.

7 8

More spare time = New Winetests build
by Jakob Eriksson 27 Nov '03

27 Nov '03

winetests has still not made it to CVS so one month later I have another build for you: Tests built with MSVC 7 from CVS 20031127. (Testing shell cross built with mingw32.) http://vmlinux.org/jakov/Wine/ And as Brian Vincent put it: "All you have to do is download winetests.exe and just run it. All of the collected results get displayed in a browser window with the option of submitting them to the wine-tests-results mailing list." Don't be afraid it the screen turns blank for a second. It's normal. regards, Jakob .

1 0

winearts & KDE 3.2-beta1
by Kevin Koltzau 27 Nov '03

27 Nov '03

I decided to give KDE 3.2-beta1 a try (just for reference I'm using the Gentoo ebuild), and found a problem with compiling winearts under KDE 3.1 "artsc-config --cflags" gives me -I/usr/kde/3.1/include/artsc but under KDE 3.2-beta1 I get -I/usr/kde/3.2/include/artsc -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include which causes a problem because this value is passed to makedep during compilation, which fails with "Unknown option '-pthread'"

2 1

Debug channel list
by Mike Hearn 27 Nov '03

27 Nov '03

Here's a more readable version of what I just posted to wine-patches. There are quite a few, aren't there? Full marks to anybody who can actually describe what they all monitor :) accel adpcm advapi animate aspi atom avicap avifile bidi bitblt bitmap cabinet capi caret cdrom cfgmgr32 class clipboard clipping combo comboex comm commctrl commdlg computername console crtdll crypt curses cursor d3d d3d_shader d3d_surface datetime dc ddeml ddraw ddraw_fps ddraw_geom ddraw_tex debugstr devenum dialog dinput dll dma dmband dmcompos dmfile dmfiledat dmime dmloader dmscript dmstyle dmsynth dmusic dosfs dosmem dplay dplayx dpnhpast driver dsound dsound3d edit enhmetafile environ event eventlog exec file fixup font fps g711 gdi global glu graphics header heap hook hotkey icmp icon imagehlp imagelist imm int int21 int31 io ipaddress iphlpapi jack joystick key keyboard listbox listview loaddll local mapi mci mcianim mciavi mcicda mcimidi mciwave mdi menu menubuilder message metafile midi mmaux mmio mmsys mmtime module monthcal mpeg3 mpr msacm msdmo msg mshtml msi msimg32 msisys msrle32 msvcrt msvideo mswsock nativefont netapi32 netbios nls nonclient ntdll odbc ole oledlg olerelay opengl pager palette pidl powermgnt print process profile progress propsheet psapi psdrv qcap quartz ras rebar reg region relay resource richedit rundll32 sblaster scroll seh selector server setupapi shdocvw shell shlctrl snmpapi snoop sound static statusbar storage stress string syscolor system tab tape tapi task text thread thunk tid timer toolbar toolhelp tooltips trackbar treeview ttydrv twain typelib uninstaller updown urlmon uxtheme ver virtual vxd wave wc_font win win32 wineboot winecfg wineconsole wine_d3d winevdm wing winhelp wininet winmm winsock winspool wintab wintab32 wnet x11drv x11settings xdnd xrandr xrender xvidmode

1 0

Re: Fun projects?
by Ivan Leo Murray-Smith 27 Nov '03

27 Nov '03

>The easiest way is simply to convert the Gimp into a >Windows program by compiling it with WineLib >That means that in order to use Photoshop >plugins in the Gimp you'd need a special build of the Gimp Special build? Wouldn't it be easier to use the native version of gimp for windows?

2 1

Re: Winealsa : add support for Alsa 1.0
by Dimitrie O. Paun 27 Nov '03

27 Nov '03

On November 27, 2003 06:21 am, Sylvain Petreolle wrote: > Is this second attempt better ? > (not tested with alsa 0.9) Why don't you define the snd_pcm_hw_params_* macros for alsa 0.9. For example, this bit: - snd_pcm_format_t format = snd_pcm_hw_params_get_format(hw_params); - snd_pcm_access_t access = snd_pcm_hw_params_get_access(hw_params); + snd_pcm_format_t format; + snd_pcm_access_t access; + snd_pcm_uframes_t buffer_size, bufsize_min, bufsize_max; + int dir=0, channels, channels_min, channels_max; + long int period_size, periods_min=0, periods_max=0; + +#if (SND_LIB_MAJOR == 0) + format = snd_pcm_hw_params_get_format(hw_params); + access = snd_pcm_hw_params_get_access(hw_params); +#else + snd_pcm_hw_params_get_format(hw_params,&format); + snd_pcm_hw_params_get_access(hw_params,&access); +#endif Could have been coded like so: +#if (SND_LIB_MAJOR == 0) +# define snd_pcm_hw_params_get_format(hw_params,format) do{ *format = snd_pcm_hw_params_get_format(hw_params);} while(0) +# define snd_pcm_hw_params_get_access(hw_params,access) do{ *access = snd_pcm_hw_params_get_access(hw_params);} while(0) ... more snd_pcm_hw_params_* definitions +#endif ... - snd_pcm_format_t format = snd_pcm_hw_params_get_format(hw_params); - snd_pcm_access_t access = snd_pcm_hw_params_get_access(hw_params); + snd_pcm_format_t format; + snd_pcm_access_t access; + snd_pcm_uframes_t buffer_size, bufsize_min, bufsize_max; + int dir=0, channels, channels_min, channels_max; + long int period_size, periods_min=0, periods_max=0; + + snd_pcm_hw_params_get_format(hw_params,&format); + snd_pcm_hw_params_get_access(hw_params,&access); Eliminates a lot of #ifdefs, cleaner code, etc. -- Dimi.

2 1

Wine lecture slides
by Shachar Shemesh 27 Nov '03

27 Nov '03

Hi all, The updated slides for the lecture I'll be giving on Sunday are at http://www.shemesh.biz/wine/slides.pdf. I tried to incorporate all of the feedback from you guys. I would, still, appretiate any further feedback you may wish to give. I also have specific questions, if anyone knows the answers: - What is the current status of "--with-nptl" on RH9? Is it positively necessary to include that when running ./configure? I know it's not necessary when running wineinstall. - Can someone please verify my knowledge of Corel's wine history Hmm, that list turned out shorter Corel-wine: As far as I could discern from the good ol' web, Corel started it's Wine initiative in 1999 as an alternative to actually porting WordPerfect and friends to Linux. They created a branch called "Corel-wine", which was also open source (wine was X11 at the time, so they did have the choice). At some point, corel-wine died. Why did it die? When did that happen? Shachar -- Shachar Shemesh Open Source integration & consulting Home page & resume - http://www.shemesh.biz/

3 2

MSVC build log of wine conformance tests
by Jakob Eriksson 27 Nov '03

27 Nov '03

MSVC build log of wine conformance tests: http://vmlinux.org/jakov/Wine/build_log_MSVC_CVS_2003-11-27.txt All in all, 14 tests compile and 7 do not. AFAIK I use an up to date VC++ 7. (I reinstalled Windows though, so I _might_ have missed something.) regards, Jakob

1 0

← Newer
1
2
3
4
5
6
7
8
9
...
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 November 2003