wine-devel February 2005

wine-devel@winehq.org

157 participants
316 discussions

Winetools Debian Package!
by Scott Ritchie 02 Feb '05

02 Feb '05

Ok, I finished up the winetools Debian packages. It's on the same repository as the Wine packages at winehq, so you should be able to install it easily from there. To run it simply type "winetools" or use the (hopefully created) menu entry. One day I hope to have a man page and such, but for now it seems good. Thanks, Scott Ritchie

1 0

Re: [LOSTWAGES] screenshots
by Tom 02 Feb '05

02 Feb '05

On Tue, 01 Feb 2005 22:13:02 +0100, Jonathan Ernst <Jonathan(a)ErnstFamily.ch> wrote: > Changelog: > - remove non-existant screenshots > - remove link to 404 Not Found page > > Files changed: > - templates/en/screenshots.template > -<tr valign=top align=center> - <td width="33%"> - {$im_6} - {$ds_6} - </td> - <td width="34%"> - {$im_7} - {$ds_7} - </td> - <td width="33%"> - {$im_8} - {$ds_8} - </td> -</tr> :-) Thats not the way it works :) There are 16 screen shots in toatle.. 9 are on the first page correct? now go to more screen shots.... there are 6 on this page humm 15 shots .. shot 10 is missing if you notice. $im_ starts with 0 so there are 9 slots in toatle. You want to remove three and that would leave 6 slots. The first page would have 6 screen shots, second page would also have 6 shots but it would skip shot 7 so where on screen shot 13 now. Third page would have 2 shots as it would skip a shot as well. Now you have 4 non- existant screenshots... What need to is make it work with 16 shots and not skip a shot... To remove the 404 is correct ofcourse. Tom

1 0

Software Freedom Law Center
by Jeremy White 02 Feb '05

02 Feb '05

Hi Folks, There is an exciting announcement out today: http://www.desktoplinux.com/news/NS7711938137.html Essentially, OSDL has funded a community oriented pro-bono legal service for Free and Open Source Software Projects. The Center is led by Eben Moglen, the chief counsel for the FSF. I've been speaking privately with Eben Moglen about this new effort, and he tells me that they would like to have the Wine Project as one if their very first clients. Candidly, this seems fantastic to me; one of the difficult things that I face when promoting Wine is peoples Fear, Uncertainty, and Doubt about the legality of Wine. Having an opportunity to clarify these legal issues is probably the most important thing that could happen for Wine, in my opinion (well, okay, maybe it's less important than support for Pirates! <grin>). However, before I go off to request the services of the SFLC, I thought I would post this announcement here and open it for any discussion. I'd particularly like to hear if folks can think of any reasons why this might be a bad thing. Finally, the key objectives from my standpoint are as follows: 1. Get an opinion written on Wine and copyright issues (imho, we have no IP issues here) 2. Get some legal research done on Patent issues I don't know how this will turn out, so I think we should wait for the research. 3. Investigate the legal doctrine surrounding what use a monopoly can make of its patents; I know that US antitrust law provides some restraints, but it would be great to have a legal opinion on the matter. Thoughts? Comments? Cheers, Jeremy

3 2

Re: Wine legalities
by Juan Lang 02 Feb '05

02 Feb '05

Mike wrote: > I'm sure Microsoft would be more than happy to charge you $400/hr > (or whatever their support rate is) to solve your problems running > Microsoft Office on Windows 2000, Wine/Linux, or even MS-DOS 3.1 > if you want. > > Just have your credit card details ready :) Heh. Yeah. In fact, I wouldn't be surprised if they're secretly a little supportive of Crossover (maybe less so for winehq): they _still_ get their Office revenue, but none of the support costs. If Linux ever got big enough on the desktop that they could make similar margins as they make on MacOS with Office, you can bet they'd make such a beast. But the support costs (for the desktop) are too high, and the revenue too low. The fact that you guys (codeweavers) can do it just shows a) you're not spending a small nation's GDP on marketing, and b) you're a whole lot smarter :) --Juan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Re: MSI: partially implement of AppSearch action
by Aric Stewart 02 Feb '05

02 Feb '05

Hi Juan, YAY! someone else doing action work.. However there are a few problems i want to point out so you can review your code and check. I have attached a patch i quickly made to avoid some problems i was having. But what you will want to look over and figure out is a) if the action returns anything other than ERROR_SUCCESS the install will halt at that action returning that error. So you need to make sure that you only return errors that should fully halt the install. b) Watch out for null fields. load_dynamic_stringW will return a NULL pointer for those but MSI_RecordGetInteger returns a special value. oh and i fixed that looks like a copy and paste error. -aric Juan Lang wrote: > ChangeLog: partially implement AppSearch action > > --Juan > > Index: appsearch.c =================================================================== RCS file: /cvstrees/crossover/office/wine/dlls/msi/appsearch.c,v retrieving revision 1.1.1.1 diff -u -r1.1.1.1 appsearch.c --- appsearch.c 1 Feb 2005 14:29:10 -0000 1.1.1.1 +++ appsearch.c 2 Feb 2005 02:44:15 -0000 @@ -127,7 +127,7 @@ maxVersion = load_dynamic_stringW(row,4); if (maxVersion) { - ACTION_VerStrToInteger(minVersion, &sig->MaxVersionMS, + ACTION_VerStrToInteger(maxVersion, &sig->MaxVersionMS, &sig->MaxVersionLS); HeapFree(GetProcessHeap(), 0, maxVersion); } @@ -610,6 +610,9 @@ } else rc = ERROR_OUTOFMEMORY; + + if (rc != ERROR_OUTOFMEMORY ) + rc = ERROR_SUCCESS; return rc; } @@ -689,7 +692,10 @@ ERR("Error is %x\n",rc); goto end; } - depth = MSI_RecordGetInteger(row,4); + if (MSI_RecordIsNull(row,4)) + depth = 0; + else + depth = MSI_RecordGetInteger(row,4); ACTION_ExpandAnyPath(package, buffer, expanded, sizeof(expanded) / sizeof(expanded[0])); if (sig->File)

2 1

Lostwages: introduction-2.diff
by Tom 01 Feb '05

01 Feb '05

Hello, In my first patch I had a incorrect link.. Tom Changelog: Fix a link

1 1

Richedit using program
by Shachar Shemesh 01 Feb '05

01 Feb '05

In case anyone is interested, there is an open source (GPL) notepad replacement which does syntax highlighting. You can grab it at http://notepad-plus.sourceforge.net/uk/site.htm. Shachar -- Shachar Shemesh Lingnu Open Source Consulting ltd. http://www.lingnu.com/

1 0

Re: MAPI32.dll.so - how to use in linux programs?
by Jon Griffiths 01 Feb '05

01 Feb '05

Hi Luke, >i noticed that Wine has a mapi32.dll.so. The current MAPI code is very, very far from complete. I have been implementing it in a bottom up manner (i.e. starting with the lower level/utility functions and working up toward constructing the higher order functions/objects). For example, there is no table support at present (I have an IMAPITable implemenation of sorts, but its not ready to be committed yet, pending cleanup, tests and thread safety checks). Providing the message stores etc must then be built on top of these objects. I believe Crossover Office runs MS Outlook so you may have more success using the native dlls at this moment in time. For the functions that are complete there is documentation in the source: "make htmlpages" from the base Wine dir will format these into readable html starting at documentation/html/index.html. >the test program relies on a test loader program, so i can't find a >"int main (char *argv[], int argc)" anywhere nor is it obvious >what's going on. Assuming you are referring to dlls/mapi32/tests/, the test framework is integrated to allow the tests to share common code and for multiple tests to be run from one place. The start_test() macro defined a test name which is then linked into the main mapi32_test.exe.so and available by running the test with that name as a parameter (see include/wine/test.h for the common code that supports this). Note that these tests don't yet test anything to do with mail per se, they are more concerned with ensuring the various low level functions in the dll are correct. If your tests will rely on an exchange server being present it is unlikely that you will be able to put them in the main wine tree, so a stand alone program is likely the best solution. As for sample programs, a quick google for "mapi sample program" and you will get a bunch of links, including some freely downloadable MS samples. I personally am doing my current testing directly against the native (XP) dll itself, it being too early at this point to attempt to get any 'real' programs running with the code. I have a fair amount of not yet submitted stuff for this dll; if you think it will help I could clean it up and pass it on for your perusal. Also if you create/discover anything that you think may be helpful to implementing parts of this dll (and you are free to distribute it), please feel free to send it to me. 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

5 5

wine
by te0543＠giga.net.tw 01 Feb '05

01 Feb '05

I use x86 solaris. I got these messages compiling wine-20050111. configure: WARNING: sys/reg.h: present but cannot be compiled configure: WARNING: sys/lwp.h: present but cannot be compiled configure: WARNING: pthread.h: present but cannot be compiled configure: WARNING: arpa/nameser.h: present but cannot be compiled configure: WARNING: GL/glx.h: present but cannot be compiled checking for assembler keyword for word values... configure: error: could not discover how to specify word values with assembler.

1 0

re: NPTL and Wine threads
by Dan Kegel 01 Feb '05

01 Feb '05

Luke wrote: > it's come to my attention that NPTL cannot cope with jumping out > of a cancellation handler. Tough noogies, as it were. See http://www.opengroup.org/onlinepubs/009695399/functions/pthread_cleanup_pop… > there is some code in FreeDCE which expects to be able to jump out > of a cancellation handler Then FreeDCE should be fixed to be POSIX-compliant, I think. Or is there something subtle going on here? - Dan -- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html

3 4

olepicture.c compile failure : "structure has no member named `UserData', implicit declaration of function `DGifOpen'"
by Rizwan Kassim 01 Feb '05

01 Feb '05

This has been reported as Bugzilla 1730. " olepicture.c: In function `_gif_inputfunc': olepicture.c:834: structure has no member named `UserData' olepicture.c: In function `OLEPictureImpl_Load': olepicture.c:923: warning: implicit declaration of function `DGifOpen' olepicture.c:923: warning: assignment makes pointer from integer without a cast make[2]: *** [olepicture.o] Error 1 " configure, apparently, doesn't check that both libgif.so and libungif.so are the correct versions. This was with latest CVS 2005-01-15, in /wine/dlls/oleaut32 Some slackware and debian installs that I've found have : /usr/lib/libgif.so -> libungif.so.3.0.0 /usr/lib/libungif.so -> libungif.so.3.0.0 libungif.so.4.1.0 was available, however. Running: ln -s /usr/lib/libungif.so.4.1.0 libungif.so ln -s /usr/lib/libungif.so.4.1.0 libgif.so in the wine/dlls/oleaut32 directory fixes the compile. I've added this fix to the (Unconfirmed) bug. Any input -- whats my next step? -- Thank you, Rizwan Kassim

3 3

my trouble
by pyd 01 Feb '05

01 Feb '05

hello all: I download one Game http://www.qf.com.cn/software/qfweiqi.exe run in WINE but It show me like this. ------------------------------------------------ pyd@linux:~/.wine/drive_c/qf> wine GoStoneClient.exe fixme:ole:CoRegisterMessageFilter stub wine: Unhandled exception (thread 002c), starting debugger... WineDbg starting on pid 0x2b In 32 bit mode. 0x404719c4 DebugBreak+0x4 in kernel32: popl %ebp Wine-dbg> ------------------------------------------------ I have allready install win98 dll store in wine.my system is SuSe8.2 pyd.

2 1

[AppDB] bug on links
by Raphael 01 Feb '05

01 Feb '05

Hi, try http://appdb.winehq.org/appview.php?appId=443&versionId=627 select the www.darkageofcamelot.com link .... bug :) Regards, Raphael

2 1

regression in
by tony_lambregts＠telusplanet.net 01 Feb '05

01 Feb '05

According to bug 2659 http://bugs.winehq.org/show_bug.cgi?id=2659 This patch http://www.winehq.org/hypermail/wine-cvs/2005/01/0232.html causes a regression in Shareaza. http://www.shareaza.com/?id=download -- Tony lambregts

1 0

Re: Slick build output
by Jason But 01 Feb '05

01 Feb '05

First, I apologise for the patch not being here... It appears that my attachment failed, I include it inline in the mail this time.. To Make.rules.in --------------------------------------------------------------------------- 20a21,32 > # Default running of (gnu)make causes a silent make with the NICE_ECHO > # macro expanding to the echo command. > # Running (make VERBOSE=yes) causes the NICE_ECHO to expand to the NULL > # shell command and cause no output. The output will be as per the > # original incarnation of the Makefile > ifneq ($(VERBOSE), yes) > .SILENT: > NICE_ECHO = @echo -e > else > NICE_ECHO = @: > endif > 118a131 > $(NICE_ECHO) " Compiling\t\t$<" --------------------------------------------------------------------------- There has been a range of comments to my original proposal. I make the following points. - I understand that there are those who desire to see the full output, for those running "make VERBOSE=yes" will produce exactly the same output as before. - To the suggestion of "make -s", this gives no output and is pretty useless. - I have been a developer for 20 years and nothing frustrates me more than make output that is over complicated. I see the point of printing the full command line when developing and debugging the Makefile and the make process. Once this is fixed however, I prefer a simple output from make telling me what is currently being compiled, I don't need to see all output every time. Finally, I have progressed a little further, but no patches for you yet. I have modified the *.in files for Make.rules.in, and in the libs and tools subdirectories. My current output (of make) is attached below for comment. I have similar output for "make install" and "make uninstall" (output is nicely lined up on fixed-width fonts :-) Jason. --------------------------------------------------------------------------- jbut-laptop# make Making in libs/ Making in libs/port/ Compiling ffs.c Compiling fstatvfs.c Compiling futimes.c Compiling getopt.c Compiling getopt1.c Compiling getpagesize.c Compiling gettid.c Compiling interlocked.c Compiling lstat.c Compiling memcpy_unaligned.c Compiling memmove.c Compiling mkstemps.c Compiling pread.c Compiling pwrite.c Compiling readlink.c Compiling sigsetjmp.c Compiling spawn.c Compiling statvfs.c Compiling strcasecmp.c Compiling strerror.c Compiling strncasecmp.c Compiling usleep.c Creating Library libwine_port.a Making in libs/unicode/ Compiling casemap.c Compiling collation.c Compiling compose.c Compiling cptable.c Compiling fold.c Compiling mbtowc.c Compiling sortkey.c Compiling string.c Compiling utf8.c Compiling wctomb.c Compiling wctype.c Compiling c_037.c Compiling c_424.c Compiling c_437.c Compiling c_500.c Compiling c_737.c Compiling c_775.c Compiling c_850.c Compiling c_852.c Compiling c_855.c Compiling c_856.c Compiling c_857.c Compiling c_860.c Compiling c_861.c Compiling c_862.c Compiling c_863.c Compiling c_864.c Compiling c_865.c Compiling c_866.c Compiling c_869.c Compiling c_874.c Compiling c_875.c Compiling c_878.c Compiling c_932.c Compiling c_936.c Compiling c_949.c Compiling c_950.c Compiling c_1006.c Compiling c_1026.c Compiling c_1250.c Compiling c_1251.c Compiling c_1252.c Compiling c_1253.c Compiling c_1254.c Compiling c_1255.c Compiling c_1256.c Compiling c_1257.c Compiling c_1258.c Compiling c_10000.c Compiling c_10006.c Compiling c_10007.c Compiling c_10029.c Compiling c_10079.c Compiling c_10081.c Compiling c_20866.c Compiling c_20932.c Compiling c_28591.c Compiling c_28592.c Compiling c_28593.c Compiling c_28594.c Compiling c_28595.c Compiling c_28596.c Compiling c_28597.c Compiling c_28598.c Compiling c_28599.c Compiling c_28600.c Compiling c_28603.c Compiling c_28604.c Compiling c_28605.c Compiling c_28606.c Creating Library libwine_unicode.so.1 Creating Library libwine_unicode.so Making in libs/wine/ Compiling config.c config.c: In function `init_server_dir': config.c:120: warning: right shift count >= width of type config.c:125: warning: right shift count >= width of type Compiling debug.c Compiling ldt.c Compiling loader.c Compiling mmap.c Compiling port.c Creating Library libwine.so.1 Creating Library libwine.so Making in libs/wpp/ Compiling preproc.c Compiling wpp.c YACCing ppy.y Compiling y.tab.c LEXing ppl.l Compiling lex.yy.c Creating Library libwpp.a Making in tools/ Compiling bin2res.c Linking bin2res Compiling fnt2bdf.c Linking fnt2bdf Compiling fnt2fon.c Linking fnt2fon Compiling makedep.c Linking makedep Compiling sfnt2fnt.c Linking sfnt2fnt Creating wineprefixcreate Making in tools/widl/ Compiling hash.c Compiling header.c Compiling proxy.c Compiling typelib.c Compiling utils.c Compiling widl.c Compiling write_msft.c write_msft.c:584: warning: 'ctl2_alloc_importinfo' defined but not used write_msft.c:622: warning: 'ctl2_alloc_importfile' defined but not used write_msft.c:920: warning: 'ctl2_find_nth_reference' defined but not used YACCing parser.y conflicts: 25 shift/reduce Compiling y.tab.c LEXing parser.l Compiling lex.yy.c Linking widl Making in tools/winebuild/ Compiling import.c Compiling main.c Compiling parser.c Compiling relay.c Compiling res16.c Compiling res32.c Compiling spec16.c Compiling spec32.c Compiling utils.c Linking winebuild Creating winebuild.man Making in tools/winedump/ Compiling debug.c Compiling emf.c Compiling le.c Compiling main.c Compiling misc.c Compiling msmangle.c Compiling ne.c Compiling output.c Compiling pe.c Compiling search.c Compiling symbol.c Linking winedump Making in tools/winegcc/ Compiling winegcc.c Compiling utils.c Linking winegcc Making in tools/wmc/ Compiling lang.c YACCing mcy.y YACCing mcy.y Compiling mcl.c Compiling utils.c Compiling wmc.c Compiling write.c Compiling y.tab.c Linking wmc Making in tools/wrc/ Compiling dumpres.c Compiling genres.c Compiling newstruc.c Compiling readres.c Compiling translation.c Compiling utils.c Compiling wrc.c Compiling writeres.c YACCing parser.y conflicts: 5 shift/reduce Compiling y.tab.c LEXing parser.l Compiling lex.yy.c Linking wrc

4 6

Re: wine/dlls x11drv/x11drv.h x11drv/winpos.c x11d ...
by Dimitrie O. Paun 01 Feb '05

01 Feb '05

On Mon, Jan 31, 2005 at 10:34:07AM -0600, Alexandre Julliard wrote: > Log message: > Only create an X window for top-level windows, not for child windows. > Get rid of the X client window too, it's no longer needed. Cool. Does this mean that the window management rewrite is done? -- Dimi.

3 5

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 February 2005