- wine-devel - winehq.org

Re: Documentation: Clarified need for conformance tests.
by Francois Gouget 07 Apr '04

07 Apr '04

On Wed, 7 Apr 2004, Michael Jacobsen wrote: > Hi there. This is my first go at submitting a patch. Let's see if it works. It needs a small s/avalible/available/ and it would be nice to follow the 2-space indentation used in the rest of the doc. Besides that it looks good. Thanks for your contribution. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Any sufficiently advanced Operating System is indistinguishable from Linux

1 0

article
by Pouech Eric DMI AEI CAEN 07 Apr '04

07 Apr '04

read on from lwn.net http://www-106.ibm.com/developerworks/linux/library/l-wine/?ca=dgr-lnxw04Fi…

1 0

Virus on wine-patches@winehq.org
by Rolf Kalbermatter 07 Apr '04

07 Apr '04

Could someone please remove the following postings from the archive as they contain viruses? http://www.winehq.org/hypermail/wine-patches/2004/04/0082.html http://www.winehq.org/hypermail/wine-patches/2004/04/0084.html Rolf Kalbermatter

3 2

Re: development speed
by Ivan Leo Murray-Smith 07 Apr '04

07 Apr '04

> The website stats are interesting too: Are these available somewhere? Ivan.

2 1

arch tip #1
by Mike Hearn 07 Apr '04

07 Apr '04

At Dimis request, I've added a new script to the root of the gateway tree. The genpatch program takes a series of patch ids as parameters and can generate and send an email to wine-patches with the combined diff of all the given commits. For example: let's say you are working on a feature. You do 3 commits, to keep the changes physically separate, however you decide the commits are too fine grained to submit all at once, so you want to submit them together. Genpatch makes that easy. Say you commit patch-4, patch-5 and patch-6: ./genpatch -m 4 5 6 will compute the combined differential of all those commits, take the commit log and summary of the first and generate an email from them. The patch will include and new files that were added. Have fun! thanks -mike

1 0

Re: wine/ include/config.h.in dlls/x11drv/xrandr.c ...
by Mike Hearn 07 Apr '04

07 Apr '04

On Tue, 06 Apr 2004 22:57:36 -0500, Alexandre Julliard wrote: > Log message: > Mike McCormack <mike(a)codeweavers.com> > Load the XRandR extension dynamically (with help from Alex Pasadyn). Are we sure this is a good idea? Dynamic version of the X extension libraries are not available on every distro, as traditionally XFree has shipped them statically. I'm not even sure they have stable interfaces. It seems wiser to just statically link libXrandr, seeing that it's only 7.7k

1 0

Window management thoughts
by Mike Hearn 07 Apr '04

07 Apr '04

So, me and Mike have been discussing some ideas for window management in Wine. Currently it hasn't turned into code, but I thought I'd write up what our thoughts were so others could comment and maybe be inspired to write patches. The problem: Currently Wine decides whether to make a window managed or not based on a series of heuristics, in is_window_toplevel in dlls/x11drv/window.c Unfortunately these heuristics are frequently wrong, as they have only limited information to work with (window styles, mostly). In CrossOver, is_window_toplevel is easily the most hacked function in the entire codebase. This manifests itself in a variety of ways: * Windows are marked unmanaged when they shouldn't be. For instance, see WinAmp, Trillian, the Counter-Strike CD Key screen etc: there are tons of examples of this problem. This at best means the window is "nailed" to the screen, at worst it makes the program unusable. * The classic "my game starts but I can't type" problem where keyboard input goes to the terminal instead of the window, due to the lack of focus management in unmanaged windows. * Some programs display splash screens and then pop up errors or question dialogs underneath them. Unmanaged windows are always-on-top -> you cannot get to the underlying managed window and the app appears to hang. * Fullscreen windows are really hard to do properly because they must be managed to work correctly in KDE/GNOME. We currently make certain windows unmanaged typically because we need to control their position or rendering with a high degree of accuracy. Unfortunately some X window managers ignore positioning hints, even when we ask them not to. There is no way to make things like menus and tooltips work correctly with these WMs, so we take the window out of the usual window management mechanism entirely. Unfortunately due to the design of the win32 API there is no simple way to tell the difference between a large menu and the Trillian main window. We could mark our own menus specially to make them unmanaged and have everything else be managed, but we then run into problems with programs that draw their own menus and tooltips, of which there are a truly shocking number. So what is a possible solution? Well, one way forward is to implement another mode, in which Wine makes all windows managed and uses a variety of WM hints to get the desired behaviour. For instance, the PPosition flag asks the WM to place the window where the application requests it to. Some WMs respect this, others do not, in yet others it's a toggleable option. For people with WMs that meet the requirements of Wine all windows could be made managed, and for people that don't use such WMs the old way can still be used. IIRC it's possible to ask the WM for identification which means this setting could be largely autodetected by having blacklists of WMs to use the old mode for (or vice-versa). Unfortunately there's no way to know how well this approach would work, or even if it would work at all, short of trying it. thanks -mike

5 6

Re: Re: wineserver: correctly free the debug ctx
by Pouech Eric DMI AEI CAEN 07 Apr '04

07 Apr '04

> It seems to me this will cause the context to never be freed. I don't > understand the problem with multiple processes, the context is bound > to the debugger thread so it shouldn't make any difference how many > processes are being debugged. Could you please give more details on > the problem? well, problem (sigsev in wineserver) happened when quitting windbg after debugging several processes. I'll try to reproduce it over this weekend. A+

1 0

Re: Game support
by James Perry 07 Apr '04

07 Apr '04

Sorry, meant to send this to the list first time around... >> But I narrowed it down to 3 Wine calls in the >> critical loop: SetEvent, WaitForSingleObject and ResetEvent. >> I tried wrapping each of these functions with >> __asm__("pushfl\n"); at the start and __asm__("popfl\n"); at >> the end to preserve the flags - with this, PECrypt works >> fine and the game gets as far as trying to initialise >> DirectX. Not exactly a neat fix though. > > > Did you have to do all of them, or is it just one function that needs this > treatment? SetEvent definitely needs it. The others possibly don't. But I think it would be more robust to preserve the flag through all of them anyway, in case someone makes a change in future that causes one of the others to clear the direction flag too, which seems quite possible. > Are you sure it's not that we need to set the flag before > jumping to the entrypoint? The flag is normally cleared. PECrypt sets it explicitly, then expects it to remain set across those three API calls. > PECrypt sounds like it should run very early on > in the programs lifetime: how much stuff does it do before hitting this > bug? AFAIK, PECrypt just decrypts and decompresses the executable at startup, then it goes away and the program runs as normal. This bug does happen very early on. > If there is really widespread software that depends on > this behaviour though there is precedent for including a hack for it - see > the DllMain wrapper which preserves %ebx for an example. Certainly anything compressed with PECrypt will depend on the flag being preserved. In general I'd imagine it's quite rare for programs to run with the direction flag set for long periods though. Cheers, James

1 0

ole32.dll_CoRegisterPSClsid
by Paul Ortyl 06 Apr '04

06 Apr '04

Hi, If only ole32.dll.CoRegisterPSClsid() is implemented (empty stub returning '1' is enough) then the application "GeoGeogrid® for Windows©" starts and allows at least some basic operations. (tested with "Baden-Würtemberg AMTLICHE TOPOGRAPHISHE KARTEN" Top50, Version 4) For more info on GeoGrid you may look at: http://swpat.ffii.org/patents/effects/geogrid/index.en.html http://www.eads.net/frame/lang/en/xml/content/OF00000000400004/4/20/534204.… Basically all official topographical maps in Germany are available only through this proprietary application. It would be really useful if ole32.dll.CoRegisterPSClsid() could be implemented in (next) release... TIA Paul Ortyl -- Don't take life too seriously; you will never get out of it alive. -- Elbert Hubbard

1 0

AbiWord on ReactOS
by Steven Edwards 06 Apr '04

06 Apr '04

Note there are still a few minor bugs but for the most part it seems we have a real application working on ReactOS. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/

1 0

Re: WININET: move to Windows sockets
by Juan Lang 06 Apr '04

06 Apr '04

> Geoff wrote: > > Or we write our own BIO that wraps up whatever > > glue is desirable on the wine-side. Worst-case > > (and it's not that bad an alternative) is that > > you use a memory-base BIO to encapsulate all I/O > > and worry about moving data to and from "sockets", > > whatever they look like, afterwards. > > That's what I've always done. <snip> > So it's not a bad way to go at all. Yep, in fact the "real" way to do this as far as Wine is concerned is to implement SSL in secur32.dll, since this is where Windows does it. It looks about like this, although as Geoff pointed out to me the API is a bit broken. Doing a BIO inside wininet.dll might be more expedient for Hans, who I think is trying to get as much of Wine as possible ported to MinGW. You guys that know SSL better than I do: patches welcome :) --Juan __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/

2 1

Re: Game support
by Ivan Leo Murray-Smith 06 Apr '04

06 Apr '04

> btw, are there already any automated tools for parsing Wine logs? There is the examine-relay perl script in the tools directory, but it's only for relay traces. Ivan.

1 0

Re: development speed
by Brian Vincent 06 Apr '04

06 Apr '04

> Check that out - 5mb of patches for the last 3 months running. A meg of > patches just 6 days into the new month already! > > It seems Wine is moving faster than ever before. The website stats are interesting too: Daily Avg | Monthly Totals Hits Pages Visits| Sites KBytes Visits Pages Files Hits Mar 2004 267733 75495 16582 |268931 157346721 514060 2340347 7064537 8299737 Feb 2004 278180 79217 17199 |279399 203400907 498774 2297305 6994822 8067232 Jan 2004 135477 44930 8341 |154109 90054340 258586 1392848 3591136 4199791 Dec 2003 213993 71246 14408 |243882 138401056 446653 2208643 5725553 6633804 Nov 2003 244427 85277 15766 |254363 153748583 472983 2558310 6268477 7332826 Oct 2003 275663 111913 17352 |260400 161803798 537913 3469326 7430846 8545582 Sep 2003 156860 50508 10393 |173365 93441224 311790 1515269 4048260 4705814 Aug 2003 209530 69084 12812 |218040 124270932 397177 2141613 5612004 6495449 Jul 2003 243646 105136 12253 |197296 123038700 379853 3259216 6704428 7553047 Jun 2003 253998 109167 12250 |160468 91985851 306270 2729185 5642823 6349961 May 2003 262218 111683 13764 |207954 105320483 399181 3238809 6336486 7604349 Skipping to the KBytes and Hits columns, things are up. Even more interesting is in Feburary we got Slashdotted and in March we didn't. So it appears people are interested. Generally things begin to taper off as we approach summer. Last year we got some good PR by doing an interview series, so I'm planning on doing that again. Anyone know what happened on October 5th and 6th that generated so many hits? -Brian

1 0

Compiling Wine with BiDi support - instructions
by Shachar Shemesh 06 Apr '04

06 Apr '04

Hi list, Here are the formal instructions for compiling Wine with bidi support. When doing so, it is recommended that you use a fairly recent version of ICU (2.6 and up), or else there is going to be a runtime soft dependancy on some ICU files in the resulting Wine. No big deal - if these files are not there, Wine will work just fine, only without BiDi support. Still, this is not necessary. Instructions: 1. If you use a precompiled package (relatvely rare for ICU, unfortunatly), make sure it has the static libraries as well. ICU does not have these by default. If they are there, you may skip to step 8. Please note, however, that this will add about 7MB to the size of the resulting gdi.dll.so. 2. Grab ICU from the web http://oss.software.ibm.com/icu. 3. Extract the sources file. 4. CD into the ICU directory, and then into the "source" subdirectory. 5. Delete all files with the "mk" extension under icu/source/data. e.g. run "find data -name \*.mk -exec rm \{\} \;". Please trust me on this one, it's ok to do it. This step saves the aforementioned 7MB. 6. ./runConfigureICU LinuxRedHat --enable-static. If you are only building this for use with Wine, you can also add "--enable-shared=no --enable-64bit-libs=no --prefix=~/icuinstall". If not, you may wish to skip the previous step as well. 7. run "make" and "make install". Grab a lunch. Just one will do. 8. If your ICU library files are installed in /usr/lib and /usr/include, compile wine as usual. If they are installed anywhere else, you will need to set the "ICU_LIB_DIR" environment variable to wherever it was that they are installed. You will also have to add the include path. For example, if you compiled and installed icu according to my example above, you will need to set ICU_LIB_DIR to "~/icuinstall/lib", and also CPPFLAGS to "-I~/icuinstall/include". 9. Make sure that including "ubidi.h" and the following linking step passes in "configure". Also check whether include/config.h has "HAVE_ICU" set. 10. To be really sure that your wine supports BiDi, run the program given in this email. A few things to note: * The above assumes that your Wine already has http://www.winehq.org/hypermail/wine-patches/2004/04/0088.html integrated. * If you are compiling Wine on Debian, and want to use the Debian supplied ICU library for whatever reason (for example - because the packaging system pretty much requires you to), the above procedure needs to be slightly altered. ICU changed their static library naming scheme over some recent version. The Debian packaged ICU (2.1) still uses the old scheme. Either use Wine without the aforementioned patch, or set ICUUC_LIB and ICUDATA_LIB to the full path to libicuuc.a and libicudata.a respectively (they are called "libsicuuc.a" and "libsicudata.a" in newer version of ICU). Please note that this means there is a runtime dependancy on some ICU files for BiDi to work, as explained above. Instead of reposting the program for testing whether Win32 supports reordering, the link to the file in the list's archive is at http://www.winehq.org/hypermail/wine-devel/2003/08/att-0175/01-biditest.c. Enjoy -- Shachar Shemesh Lingnu OpenSource Consulting http://www.lingnu.com/

1 0

Re: Dos INT15
by Dmitry Timoshkov 06 Apr '04

06 Apr '04

"Florian Goth" <Captainsifff(a)gmx.de> wrote: > Added some more stubs after examining the dosbox source code Could you please try to stick to the formatting style used in the file in your changes? -- Dmitry.

1 0

development speed
by Mike Hearn 06 Apr '04

06 Apr '04

Hey guys, http://www.winehq.org/hypermail/wine-patches/ Check that out - 5mb of patches for the last 3 months running. A meg of patches just 6 days into the new month already! It seems Wine is moving faster than ever before. To put things in perspective, the Wine source tree is 10mb - that means in only 2 months as many lines of patch were generated as exists in Wine itself! thanks -mike

2 2

Re: WININET: move to Windows sockets
by Dan Kegel 06 Apr '04

06 Apr '04

Geoff wrote: > Or we write our own BIO that wraps up whatever glue is desirable on the > wine-side. Worst-case (and it's not that bad an alternative) is that you > use a memory-base BIO to encapsulate all I/O and worry about moving data > to and from "sockets", whatever they look like, afterwards. That's what I've always done. And it seems I've managed (via the rant at http://kegel.com/ssl/api.html) to convince Sun to make that the standard way to do ssl with NIO under the next JDK, kinda. So it's not a bad way to go at all. - Dan -- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change

1 0

Re: appdb - improvement in serching out bugs
by tony_lambregts＠telusplanet.net 06 Apr '04

06 Apr '04

Quoting hatky <hatky(a)hatky.myz.info>: > > On Sunday 04 April 2004 06:21, tony_lambregts(a)telusplanet.net wrote: > > The current code can get bugs that have nothing to do with the AppDB. > This > > should fix it. > > > > -- > > > > Tony Lambregts > > I think this is wrong, you are saying the url in bugzilla should be exactly > "appdb #" where it should realy be > "http://bugs.winehq,org/show_bug.cgi?id=#" > > No, no, no... read the patch again. The current code is correct as far as it goes, but it grabs the substring. So when the appdb# is 68 it grabs bugs that for appid 680, 681... 689. It will also grab bugs that just happen to have 68 in the url. My testing with this has been limited somewhat since I have not been able to set up the appdb on my machine but I know enough to know that the code as I have submitted will do what it needs to do. -- Tony Lambregts

2 1

DDraw issues, etc.
by Tim Hentenaar 06 Apr '04

06 Apr '04

Hi all, I've implemented SetClipList and GetClipList in the DirectDraw Clipper, and I'm wondering how I should go about implementing clipping in DirectDraw's Blt() (if it isn't already done somewhere). M$'s documentation isn't too great, so I figured I should ask around. There's a game one of my relatives wants to run under Linux (it's a children's program), and the major problem is that it dosen't seem to handle clipping properly when blitting. (e.g. every time you move the mouse, it calls SetClipList). FYI, the binkw32.dll that came with the program was originally causing it to hang, but I patched the DLL and it works fine. If anyone else has had such problems, I could provide a patch. Also, I'm going to take a look at some of the DirectSound stuff too. The sound isn't very good quality for some reason, but under the WineX 3.3 CVS, sound works perfectly. Tim

3 11

Re: WININET: move to Windows sockets
by Juan Lang 06 Apr '04

06 Apr '04

Hans wrote: > On Monday 05 April 2004 19:24, Alexandre Julliard > wrote: > > There's no real reason that we cannot use Unix > > sockets on Unix and Windows socket on Reactos with > > the same code, it just needs a bit of header magic; > > and this will be useful for Winelib apps too. > > Hmm, I'd like to agree with that. I'd be rather nervous about the mixing of OpenSSL with the use of Winsock, at least as is. OpenSSL is itself using socket read/write calls, and it expects them to be the correct ones: in particular, the UNIX ones. I believe the only way to do this correctly is to write a new OpenSSL BIO that uses the same read/write/open/close calls as the rest of netconnection.c, and this can be combined with the aforementioned header magic to get what you're after. Copying and pasting an existing OpenSSL BIO would probably suffice. --Juan __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/

2 1

Re: wineserver: correctly free the debug ctx
by Alexandre Julliard 05 Apr '04

05 Apr '04

Eric Pouech <pouech-eric(a)wanadoo.fr> writes: > when a debugging thread is attached to several processes, the debug > context (shared across all processes) is destroyed when the first > process terminates. This patch destroys it when the last process > attached terminates. It seems to me this will cause the context to never be freed. I don't understand the problem with multiple processes, the context is bound to the debugger thread so it shouldn't make any difference how many processes are being debugged. Could you please give more details on the problem? -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: WININET: move to Windows sockets
by Steven Edwards 05 Apr '04

05 Apr '04

Hello Hans, --- Hans Leidekker <hans(a)it.vu.nl> wrote: > > This makes wininet build on MinGW. > > Changelog: > Move to Windows sockets. > I asked Alexandre about a patch to move Wininet to Winsock and he said it took to much of a performance hit to merge. Is there a way we can bench mark it to show how much of a hit Winsock vs Unix sockets is going to give us? He suggested that we find a way to make Wininet use Unix sockets on Unix and Winsock on Windows. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/

6 7

Re: appdb - improvement in serching out bugs
by hatky 05 Apr '04

05 Apr '04

On Sunday 04 April 2004 06:21, tony_lambregts(a)telusplanet.net wrote: > The current code can get bugs that have nothing to do with the AppDB. This > should fix it. > > -- > > Tony Lambregts I think this is wrong, you are saying the url in bugzilla should be exactly "appdb #" where it should realy be "http://bugs.winehq,org/show_bug.cgi?id=#" -- Hatky, Worshiper of wine (http://www.winehq.org/), Impossible is only an opinion.

1 0

CryptoAPI
by "Jacek [KRunch] Chałupka" 05 Apr '04

05 Apr '04

Has anybody started implementing CryptoApi in WINE?? If no mayby someone can give me some clues how to start... I am not bad i C++ I think, but I have never make thing like that. I don't promise I will do that, but I can try... :)

3 2

Re: CryptoAPI
by Juan Lang 05 Apr '04

05 Apr '04

Jacek wrote: > Has anybody started implementing CryptoApi in WINE?? > If no mayby someone can give me some clues how to > start... I am not bad i C++ I think, but I > have never make thing like that. I don't promise I > will do that, but I can try... :) Hi Jacek, take a look at Wine's rsabase.dll, that DLL doesn't do very much yet. All its functions (CPAcquireContext, etc) are described here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/security/s… If you have access to a Windows box it's easier: you can load the DLL itself and call all the functions and try to reproduce what it's doing. Good luck, --Juan __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/

1 0

Re: Fwd: Re: appdb - improvement in serching out bugs
by tony_lambregts＠telusplanet.net 05 Apr '04

05 Apr '04

Quoting hatky <hatky(a)hatky.myz.info>: >> No, no, no... read the patch again. > Ok, sorry wasn't what I tought you are trying to do, this patch is ok > p.s. I didn't think someone actually changed the urls in bugzilla. sweet :). I have been going through them 100 at a time. I've got 1-400 done at this time. I figure I will be done sometime before Christmas :P. If anyone wants to help with this I would be glad to have the help... Check out http://bugs.winehq.org/show_bug.cgi?id=560 for more more on this. -- Tony Lambregts

1 0

NtPulseEvent
by Robert Lunnon 05 Apr '04

05 Apr '04

What is the status of NtPulseEvent it emits a diagnostic messages fixme:ntdll:NtPulseEvent (7c,0) yet it looks to me that NtPulseEvent is implemented but the fixme is bogus Anyone know about this ? BTW Has anyone experience with the Skype application under linux, does it work there ? Bob b

2 1

Should winemaker be able to handle this
by Bill Medland 05 Apr '04

05 Apr '04

I haven't been following the winemaker stuff so I don't know whether it is supposed to be able to handle this (and is broken) or not. I am having to play with the "build a builtin dll to wrap a linux so" concept again after a year or so since the last time, as discussed in the Winlib manual, chapter 5. I see that winemaker has changed since then. In particular the bit that is not working for my case is the -D, -I, -L and -l options. What I want is to run winemaker to generate the build environment and then do the build. What I used toi have was: #! /bin/bash # Run this script in order to pass the correct arguments to winemaker so that # it can set up the build environment winemaker --nosource-fix --nogenerated-specs --dll --single-target mytarget --nomfc -DMY_SETTING -I$MY_INC_DIR -L$MY_LIB_DIR -lmylinuxso . I see that we don't bother with generating spec files any longer. However I see that the -D, -I, -L and -l options don't find their way into the Makefile these days. Is that by design or a bug? (i.e. do I have to fix winemaker or do I need to look at a different way of doing it) -- Bill Medland mailto:billmedland@mercuryspeed.com http://webhome.idirect.com/~kbmed

4 5

RE: Handling dialogs created without using templates
by Santosh Siddheshwar 05 Apr '04

05 Apr '04

Hi, Thanks. Would you be able to share details of the changes you did for handling MDI windows? Regards Santosh > -----Original Message----- > From: Dmitry Timoshkov [SMTP:dmitry@baikal.ru] > Sent: Tuesday, March 30, 2004 7:40 PM > To: Santosh Siddheshwar > Cc: wine-devel(a)winehq.com > Subject: Re: Handling dialogs created without using templates > > "Santosh Siddheshwar" <santosh.s(a)sonata-software.com> wrote: > > > Yes attached is a sample which is pretty similar to what I described > > below. > > Thanks. Now I see where the problem is. We have to hook dialog creation > code into common window creation code, something similar to what I've done > recently for MDI. Alexandre, are my thoughts correct? > > -- > Dmitry. ********************************************************************* Disclaimer: The information in this e-mail and any attachments is confidential / privileged. It is intended solely for the addressee or addressees. If you are not the addressee indicated in this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. *********************************************************************

2 1

Re: Re: dbghelp
by Pouech Eric DMI AEI CAEN 05 Apr '04

05 Apr '04

> UnDecorateName is still a stub, while our winedump has some a good > framework for UnDecorateName, also translating into a GCC way and not in a > VC++ way. How should these things go together? See the comment in dbghelp.c !! My first thouhgt would be to make a .a lib out of winedump code, and use it in winedump and msvcrt and / or dbghelp. I haven't studied yet the best way to share the code between msvcrt and dbghelp A+

1 0

Re: appdb - improvement in serching out bugs
by tony_lambregts＠telusplanet.net 04 Apr '04

04 Apr '04

Quoting hatky <hatky(a)hatky.myz.info>: > > On Sunday 04 April 2004 06:21, tony_lambregts(a)telusplanet.net wrote: > > The current code can get bugs that have nothing to do with the AppDB. > This > > should fix it. > > > > -- > > > > Tony Lambregts > > I think this is wrong, you are saying the url in bugzilla should be exactly > "appdb #" where it should realy be > "http://bugs.winehq,org/show_bug.cgi?id=#" > > No, no, no... read the patch again. The current code is correct as far as it goes, but it grabs the substring. So when the appdb# is 68 it grabs bugs that for appid 680, 681... 689. It will also grab bugs that just happen to have 68 in the url. My testing with this has been limited somewhat since I have not been able to set up the appdb on my machine but I know enough to know that the code as I have submitted will do what it needs to do. -- Tony Lambregts

1 0

Re: dbghelp
by Uwe Bonnes 04 Apr '04

04 Apr '04

>>>>> "Eric" == Eric Pouech <pouech-eric(a)wanadoo.fr> writes: Eric> Eric Pouech a écrit : >> This is a first (and incomplete) shot at implementing the dbghelp >> DLL. Eric> forgot to say that: - this patch must be applied before the ones Eric> on imagehlp & taskmgr - code is highly derivated from winedbg Eric> current code Eric> I'm also working on a winedbg version based on this DLL, but it Eric> isn't ready yet (as dbghelp seems to get a bit more mature, I Eric> thought some people might be interested in testing it) UnDecorateName is still a stub, while our winedump has some a good framework for UnDecorateName, also translating into a GCC way and not in a VC++ way. How should these things go together? Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

1 0

Personal tree with interesting patches
by Mike Hearn 04 Apr '04

04 Apr '04

Hi, As I'm pretty busy right now and won't have time to work on the various misc projects I've been working on up until recently for the foreseeable future, I'm checking them into my personal arch archive for people to play with and maybe work on themselves. My archive co-ordinates: http://navi.cx/~mike/archive/2004 mike(a)navi.cx--2004 so, you'd use: $ tla register-archive http://navi.cx/~mike/archive/2004 There are currently only two interesting branches: wine--mainline--0.9: misc patches that were never applied for whatever reason, debug delay, lockwindowupdate (disabled), that sort of thing as i find more patches around my system i'll check them in for safekeeping wine--loadarea-reserve--0.9 execshield/prelink work, see the log message in patch-1 for details on what remains to be done Have fun! thanks -mike

2 2

installation program
by Brian Vincent (C) 04 Apr '04

04 Apr '04

On the To Do List (c.4) is an item for having a new graphical Wine install program. Anyone ever looked at Frank Hendrickson's WineTools program? http://franksworld.net/winetools.html It used to be written in some funky language, now it's all shell script. Anyway, if you look at the script (wt210) you'll notice he uses xdialog ( http://thgodef.nerim.net/xdialog/ ) for the GUI. So here's what I'm wondering.. How feasible would it be for Wine to create a new Winelib program (say, wdialog) and use a similar concept as Frank? wdialog would simply replicate the functionality of xdialog. We could potentially fail gracefully into shell mode if Wine can't start. It might be a cheap and simple way to get a GUI front-end. Of course, all this requires sane defaults so Wine can actually run wdialog. Any thoughts? --------------- Brian Vincent Copper Mountain Telecom vincentb(a)coppercolorado.com

1 0

Microsoft SDK samples
by Jonathan Wilson 04 Apr '04

04 Apr '04

Has anyone given thought to using the Microsoft SDK samples (e.g. DirectX samples) to improve WINE? i.e. take a particular sample and work away at it untill what you get in WINE matches what you get in Windows. Although I suspect that there are things that the MS samples dont cover :)

2 1

winapi_stats
by Tom 03 Apr '04

03 Apr '04

Hi, http://www.winehq.org/site/winapi_stats Is incorrect as it shows Total 19640 100% 100% would be nice but its incorect! Tom

3 6

Re: Documentation for GDI Region Functions
by Alexandre Julliard 03 Apr '04

03 Apr '04

Robert Shearman <R.J.Shearman(a)warwick.ac.uk> writes: > and renamed the variables to Microsoft conventions. Please don't do that. The variable names don't matter at all for compatibility, so we don't have to follow the brain-damaged Microsoft conventions for them. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: Developer's path to Windows/*NIX multi-platform?
by Dimitrie O. Paun 03 Apr '04

03 Apr '04

You ask: > I am willing to re-write my best Windows software from scratch, but I > insist that the result is native or almost on Linux so there are not any > weird GUI glitches. Do you think Wine is the way to go for me, or am I > better off writing individual versions and keeping the Windows software > native and then producing QT or GTK versions for *NIX? I'm at a cross-roads > here, since I'll be dedicating years of work in whatever direction I take. IMO Wine is the perfect tool for you. We know, it's not perfect. But the best use of your time (and the most efficient) would be to: 1. Fix any problems in your apps (like reliance on strange Windows corner cases, use of very obscure features) 2. Help out fix Wine so that your apps run properly. This will not only help us a lot, but it will help you make good use of your time, and it will allow you to do cross platform development (even for Windows) from your Linux box. Please direct questions to wine-devel(a)winehq.org, where people can help you out. -- Dimi.

7 9

W95INF32 implementation, incase it's useful to anybody
by Mike McCormack 03 Apr '04

03 Apr '04

Hi All, In the process of understanding another bug, I did a little work to implement w95inf32, which appears to be a small IE/win9x only DLL and which is probably of not much use to Wine. It appears to be a think wrapper 32bit around 4 functions in SETUPX. So this is just for documentation purposes, and incase anybody is curious or finds a real need for this DLL. Mike --- /dev/null 1994-07-18 08:46:18.000000000 +0900 +++ dlls/w95inf32/Makefile.in 2004-03-30 12:03:27.000000000 +0900 @@ -0,0 +1,20 @@ +#MKDLL_SKIP +TOPSRCDIR = @top_srcdir@ +TOPOBJDIR = ../.. +SRCDIR = @srcdir@ +VPATH = @srcdir@ +MODULE = w95inf32.dll +IMPORTS = setupapi kernel32 +ALTNAMES = w95inf16.dll + +SPEC_SRCS16 = $(ALTNAMES:.dll=.spec) + +C_SRCS = \ + w95inf32.c + +@MAKE_DLL_RULES@ + +w95inf16.spec.c: w95inf16.spec + $(WINEBUILD) $(DEFS) $(DLLFLAGS) -o $@ --main-module $(MODULE) --spec $(SRCDIR)/w95inf16.spec + +### Dependencies: --- /dev/null 1994-07-18 08:46:18.000000000 +0900 +++ dlls/w95inf32/w95inf32.c 2004-03-29 17:07:20.000000000 +0900 @@ -0,0 +1,91 @@ +/* + * W95INF32 - This is a small 32bit interface to SETUPX + * + * Copyright 2004 Mike McCormack for CodeWeavers + * + * This library is free software; you can redistribute it and/or + * modify it under the terms of the GNU Lesser General Public + * License as published by the Free Software Foundation; either + * version 2.1 of the License, or (at your option) any later version. + * + * This library is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + * Lesser General Public License for more details. + * + * You should have received a copy of the GNU Lesser General Public + * License along with this library; if not, write to the Free Software + * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + * + */ + +#include <stdarg.h> +#include "windef.h" +#include "winbase.h" +#include "winuser.h" + +#include "setupapi.h" + +#include "wine/debug.h" + +WINE_DEFAULT_DEBUG_CHANNEL(w95inf32); + +BOOL WINAPI CtlSetLddPath32( LPSTR x, LPSTR y ) +{ + FIXME("%s %s\n", debugstr_a(x), debugstr_a(y) ); + return FALSE; +} + +BOOL WINAPI GenFormStrWithoutPlaceHolders32( LPSTR dst, LPCSTR src, LPCSTR filename ) +{ + HINF hinf; + DWORD ret = 0; + + FIXME("%p %s %s\n", dst, debugstr_a(src), debugstr_a(filename) ); + + hinf = SetupOpenInfFileA( filename, NULL, INF_STYLE_WIN4, NULL ); + if( !hinf ) + return GetLastError(); + + /* FIXME: call LookupStringInTable? */ + strncpy(dst, src, MAX_INF_STRING_LENGTH ); + + SetupCloseInfFile( hinf ); + + return ret; +} + +DWORD WINAPI GenInstall32(LPCSTR filename, LPCSTR section, LPCSTR directory, DWORD flags) +{ + HINF hinf; + void *context; + DWORD ret = 0; + + ERR("%s, %s, %s, %08lx\n", filename, section, directory, flags ); + + hinf = SetupOpenInfFileA( filename, NULL, INF_STYLE_WIN4, NULL ); + if( !hinf ) + return GetLastError(); + + context = SetupInitDefaultQueueCallback( 0 ); + if (!SetupInstallFromInfSectionA( 0, hinf, section, flags, 0, NULL, + SP_COPY_NEWER_OR_SAME, SetupDefaultQueueCallbackA, + context, 0, 0 )) + { + ret = GetLastError(); + ERR("Failed %08lx\n",ret); + } + + SetupTermDefaultQueueCallback( context ); + + SetupCloseInfFile( hinf ); + + return ret; +} + +BOOL WINAPI GetSETUPXErrorText32(long a, long b, long c) +{ + FIXME("\n"); + return FALSE; +} + --- /dev/null 1994-07-18 08:46:18.000000000 +0900 +++ dlls/w95inf32/w95inf32.spec 2004-03-29 17:04:15.000000000 +0900 @@ -0,0 +1,9 @@ +# w95inf32 functions have @nn in their names... +# winebuild removes the last @xx in a function name. + +1 stdcall CtlSetLddPath32@8@8(str str) CtlSetLddPath32 +2 stdcall GenFormStrWithoutPlaceHolders32@12@12(ptr str str) GenFormStrWithoutPlaceHolders32 +3 stdcall GenInstall32@20@20(str str str long) GenInstall32 +4 stdcall GetSETUPXErrorText32@12@12(long long long) GetSETUPXErrorText32 +5 stub w95thk_ThunkData32 +

1 0

When saving a file with staroffice it is not saving with extension.
by Ravi Kumar 02 Apr '04

02 Apr '04

Hello Sir, I am working with wine for some time now. I faced with a problem, whenever i am saving a file from Windows version of Staroffice from wine it is saved without extension. I think it is a problem with wine, as staroffice in windows stores files with extensions. I am using wine-20031118 version. Can anybody help me out in this regard. I will also check out to see if it has been solved in later versions. Thanking in advance. regards, ravi.

3 2

Development CDs for Windows
by Steven Pignataro 02 Apr '04

02 Apr '04

I have a large amount of Windows Development CDs....i am wondering if these would be of any interest to the Development team of Wine.... I think that these would become very usefull at developing for Wine as well as alot of what Windows does is still most of the same. They are Windows NT 4 development kits and much much more. We where going to chuck them at my school...but salaviged them Please let me know Thanks -- Steven Pignataro A+ Partner/ CSO Computer Vision Networks, Inc. Toll Free: 866-897-8896 Phone: 269-979-5582 Fax: 269-288-0418 http://www.computervisions.net/ (c)2002-2004 --

1 0

Re: Developer's path to Windows/*NIX multi-platform?
by greensh＠knology.net 02 Apr '04

02 Apr '04

> integration. Ideally, we will have a GTK theme and a QT theme > that just calls the respective toolkit's theming code, so a > Wine app will look native both in GNOME and in KDE. I 100% agree > that native integration is paramount, and this is why we will > have it. This sounds very good. Maybe someday. > Since you've mentioned the toolkits, a small comment on that. > Of the two only QT is a serious option for cross-platform development. > It's a good option, but it's not perfect because your application > will not be native in GNOME, Well not to start a KDE vs Gnome debate, but Gnome is way behind KDE development... it doesn't even support Superkaramba (last I checked). Gnome users typically do not prefer KDE or Qt, and part of that stems from that KDE was developed using Qt and it's integration is woven throughout. > you will not be using the native toolkits > in Windows, you have to pay a lot of licensing fees, etc. You only pay licensing if your Qt app is commercial. The free version is perfect for opensource (ie GPL software) hence why it's included in almost all linux distros and you can D/L the same version for winders. Maybe > wxWindows is a better option... It requires too many code changes (at least in Python) for easy cross-compiling. In Qt you simply generate a .pro file for the platform. Shaun > > -- > Dimi. > > > > >

2 1

Re: GDI: Merge the enhmfdrv into one .c file.
by Mike McCormack 02 Apr '04

02 Apr '04

I object! Being one of the people who sometimes works on EMFs, I don't like this change. A flat namespace in my mind meants that we have one dll's code in each subdirectory in wine/dlls, not that there's no other subdirectories under those. It's a bad precedent to set that each dll can have no further subdirectries. I don't think this change is necessary, and it's going to make the EMF code harder to manage, since the file you've created is very big. Ditto for the MF change. Mike Dimitrie O. Paun wrote: > Merge the entire enhmfdrv into one .c file. > It's not big, and it's the way we usually do > things in wine (e.g. dlls/comctl32/*.c). > Moreover, we get rid of the extra dir in > dlls/gdi/, and gets us closer to a flat > dlls/*/ namespace.

2 2

Re: Developer's path to Windows/*NIX multi-platform?
by greensh＠knology.net 02 Apr '04

02 Apr '04

At work we write A LOT of 3D graphics code that has requirements to run on winders/linux/macintosh. Qt has definitely proved the way to go (5 years now) with only minor changes required and then it worked on ALL platforms. Java and Python were too slow and required too many code changes for each platform, whereas Qt worked with our existing C/C++ code nicely. BTW, a real good book that's out now is "C++ GUI Programming with Qt 3" by Jasmin Blanchette and Mark Summerfield. It starts very basic from Hello World. It's worth the $30. I'd have to say, so far from what I've seen Wine still has a long way to go before it's ready for production, and reliable use... it's getting there but just not there yet. It's great for porting apps, but too poorly documented for actual development. I mean this forum is about it and you're lucky if you can get answers. But thanks to all the helpful people here, maybe it will grow. Shaun On Thu, 1 Apr 2004 17:39:14 -0500 (EST), "Dimitrie O. Paun" <dimi(a)intelliware.ca> wrote : > > You ask: > > > I am willing to re-write my best Windows software from scratch, but I > > insist that the result is native or almost on Linux so there are not any > > weird GUI glitches. Do you think Wine is the way to go for me, or am I > > better off writing individual versions and keeping the Windows software > > native and then producing QT or GTK versions for *NIX? I'm at a cross-roads > > here, since I'll be dedicating years of work in whatever direction I take. > > IMO Wine is the perfect tool for you. We know, it's not perfect. > But the best use of your time (and the most efficient) would be to: > 1. Fix any problems in your apps (like reliance on strange Windows > corner cases, use of very obscure features) > 2. Help out fix Wine so that your apps run properly. > > This will not only help us a lot, but it will help you make good > use of your time, and it will allow you to do cross platform > development (even for Windows) from your Linux box. > > Please direct questions to wine-devel(a)winehq.org, where people > can help you out. > > -- > Dimi. > > > > > > >

2 1

abnt2 delete keys problem
by Rafael Ávila de Espíndola 02 Apr '04

02 Apr '04

I am having the following problem with a abnt2 (Brazilian) keyboard: When the numlock is off both delete keys work correctly. If the numlock is on both key produce a delete plus a comma. The message http://www.winehq.org/hypermail/wine-patches/2002/12/0329.html appears to describe the same problem. But the proposed patch didn't work for me. Attached is a xev log. The numlock is initially on. Them the I press the middle keyboard delete, keypad delete, numlock, middle keyboard delete and keypad delete. Thanks for any help. Rafael Ávila de Espíndola

2 4

MFC app compile problems with AFX
by greensh＠knology.net 01 Apr '04

01 Apr '04

Since I was told the winlib docs are out of date, I'll try posting this problem. winemaker --interactive seems to have worked and converted the 'winders' source .cpp and .h files and made the backups fine. It only created one file; Makefile When I type 'make' it produced a bunch of afx errors needing only five afx*. h files, so I copied these over from the VS6 directory, ran 'make clean', but hen it needed a ton more, so I copied them all afx*.h and afx*.inl. Then 'make' gets all the way down to the first errors; /usr/local/include/wine/windows/rpcndr.h:383: error: non-local function ` <anonymous struct>* NDRSContextUnmarshall2(void*, void*, long unsigned int, void*, long unsigned int)' uses anonymous type In file included from afxdtctl.h:19, from StdAfx.h:18, from ArbreNiv.cpp:2: afxdisp.h:75: warning: malformed '#pragma pack(push[, id], <n>)' - ignored afxdisp.h:1182: error: friend declaration requires class-key, i.e. `friend struct COleDateTimeSpan' afxdisp.h:1259: error: friend declaration requires class-key, i.e. `friend class COleDateTime' afxdisp.h:1408: warning: #pragma pack (pop) encountered without matching #pragma pack (push, <n>) In file included from afxdisp.h:1413, from afxdtctl.h:19, from StdAfx.h:18, from ArbreNiv.cpp:2: afxole.inl: In constructor `COleVariant::COleVariant(const CHAR*)': afxole.inl:97: error: `vt' undeclared (first use this function) afxole.inl:97: error: (Each undeclared identifier is reported only once for each function it appears in.) afxole.inl: In constructor `COleVariant::COleVariant(unsigned char)': afxole.inl:101: error: `bVal' undeclared (first use this function) afxole.inl: In constructor `COleVariant::COleVariant(const COleCurrency&)': afxole.inl:103: error: `cyVal' undeclared (first use this function) afxole.inl: In constructor `COleVariant::COleVariant(float)': afxole.inl:105: error: `fltVal' undeclared (first use this function) afxole.inl: In constructor `COleVariant::COleVariant(double)': afxole.inl:107: error: `dblVal' undeclared (first use this function) afxole.inl: In constructor `COleVariant::COleVariant(const COleDateTime&)': afxole.inl:109: error: `date' undeclared (first use this function) afxole.inl: In member function `DWORD COleSafeArray::GetDim()': afxole.inl:283: error: `parray' undeclared (first use this function) Can anyone help? Any ideas for me to try? I can run the winders executable with wine, but it's very buggy and will crash easily, so I wanted to use winelib. Shaun

2 1

ANNOUNCE: CVS to arch gateway
by Mike Hearn 01 Apr '04

01 Apr '04

Hi everybody, I'm pleased to announce the public availability of a gateway from WineHQ CVS to the GNU arch version control system. It marks the beginning of an experiment not just in new forms of source control, but in new ways for the Wine project to be organized and function. Nobody knows if it will catch on, but a few of us (me, dimi and alexandre) have been discussing trying out arch for some time. Carpe dium! ==================================================================== For those who already know arch, here are the details: archive coordinates: http://navi.cx/mike/wine/archive mike(a)winehq.org--wine/wine--mainline--0.9 It is synchronised with CVS on the hour, every hour and a cacherev is generated once a week. There are a couple of useful scripts in the root directory, branch and merge which are described in the README.ARCH file. It is mirrored here: http://mirrors.sourcecontrol.net/mike@winehq.org--wine/ For your convenience, and for people who have never used arch before, here is an adapted form of the README file. It's available in pseudo-HTML here: http://navi.cx/~mike/wine/ ===================================================================== README.ARCH Mike Hearn <mike(a)navi.cx> GNU arch is a distributed source control system. Unlike CVS, arch trees can be branched and branched again with no write access to the original archive. It has a variety of other interesting features - for instance, it uses atomic commits and can operate using a variety of network protocols. For more information see http://wiki.gnuarch.org The rest of this readme is going to take the form of a tutorial on how to use arch with Wine. We'll start with the really basic tasks that even non-developers may wish to use, and work up to advanced usage (branching and merging). It will not answer every question you have, for that use the wine-devel mailing list for discussion :) * Tracking Wine development --------------------------- You might not be reading this file from an actual arch project tree, so let's start with how to get a copy of the gateway tree. First of all you need to install "tla", the reference implementation of arch. You can get it from the gnuarch.org website, but a simpler way is to use the prebuilt binary available here: http://www.navi.cx/~mike/wine/tla Download, chmod +x, copy to /usr/local/bin and you're set. The binary should work on any Linux distro. Yes, it's large, the arch build system contains local copies of various libraries. Now it's installed, run the following command: tla register-archive http://www.navi.cx/~mike/wine/archive/ Once it's registered succesfully (you get a message when that happens), you can run the following command to check out the tree: tla get mike(a)winehq.org--wine/wine--mainline--0.9 winehq This will place a copy of the gateway tree into the winehq/ directory. "winehq" is a good name to use, because you may later wish to download other branches or even make your own, but there will only ever be one WineHQ tree - the one controlled by Alexandre Julliard. Yes, I know mike(a)winehq.org isn't a valid email address, it doesn't matter, the email is only for namespacing and identification reasons :) The checkout will take a long time even on a fast link: the Wine sources are 10mb. Once downloaded, updating the tree is easy: tla update So, now you have an arch project tree, what can you do? Arch has a lot of interesting commands, try "tla changelog | less" and "tla missing -s". Have fun! * Simple development ==================== The easiest way to use arch for development is the same way we use CVS: by making changes in a tree, generating a diff from those changes, then emailing in the patch. Let's see how that works. First of all, we make a change to the tree. Then we use: tla changes --diffs to get a patch. In fact, this will generate a lot of extra stuff that you don't really need - feel free to remove it, but it's not required; patch can strip out garbage from patches automatically. You can get diffs for individual files with "tla file-diffs". Be warned! These commands work against the last revision you updated to, they do *not* work against the latest version in the remote archive like CVS does. So you probably want to update first. However, unlike people just tracking the tree, you DO NOT want to use update! What update does, roughly speaking, is reverse changes made to the tree, apply the missing patches in turn, then reapply the changes. If there are any conflicts they appear in patch style .rej and .orig files. There is a better way. Arch has a very interesting and powerful command called "star-merge". Star-merge allows you to merge your tree with another tree (subject to certain rules), in a Just Works(tm) fashion. It will deal with repeated merges, and it works if the person you are merging from previously merged with you. To make this simpler, I've written a script that figures out what you branched from (if anything), and then merges from it. In effect, this is like "cvs update". ./merge This operation can be quite slow (because it involves constructing multiple trees and comparing etc), but it is generic and will work both with the gateway tree and branches - and it gives 3-way merge inline conflict markers too. If you want to do it faster, and you don't mind having patch style .rej files generated in the case of conflicts, try: tla replay which simply downloads and applies each patch in turn. "tla update" does work too, why not try them all to see which you prefer? * More advanced development =========================== So, here comes the interesting part. Now we've covered the basics, it's time to find out how to make our own branches and commit to them. You need to do a bit of setup. Firstly, you need to tell arch who you are: tla my-id 'Mike Hearn <mike(a)navi.cx>' You have to use an ID of this form, arch won't accept others. Now you need to create your own archive. An archive is a rough equivalent of a CVS repository with one key, fundamental difference: an archive is a personal thing which can contain trees from many different projects. Typically a person has only one archive, though there's nothing to stop you having more. Archives are just directories and files, no special server software is required to run one. You just need some web space. The basic workflow with arch goes something like this: 1) Write patch 2) Commit to branch 3) Upload to a mirror of your archive Your actual archive is usually kept locally, which means you can work and commit offline. You then mirror the archive on a remote machine so others can access it. If people want to work on your tree, they branch it, set up their own archive and then you pull from that. In other words, only you have write access to your own archive. So, you need to create a directory to hold your archive, like this: tla make-archive mike(a)navi.cx--2004 ~/Code/Arch/2004 tla my-default-archive mike(a)navi.cx--2004 The named directory should not exist, but its parents should. An archive name must have the form of an email address followed by two dashes followed by a name. I've named it after the year of creation which is pretty common, but it can be called anything. Now, to speed things up, you probably want to create a revision library. This is basically a cache (using hard links to be space efficient) of revisions. You probably want it. Make one like this: mkdir ~/Code/Arch/RevLib tla my-revision-library ~/Code/Arch/RevLib tla library-config --sparse --greedy ~/Code/Arch/RevLib OK. Now you just need some web space. Arch can write to web space using ftp, sftp (ssh), or WebDAV. You probably want sftp. If you don't have any web space you can use talk to me and I'll put you in touch with people who can give you some space specifically for hosting archive mirrors. For now, don't bother with a remote mirror. Just play with a local copy, that way you can delete things if you make a mistake (you can delete a branch with rm -rf inside the archive, nothing will break). Let's say you wish to branch the WineHQ tree, and start work on the winecfg program. The simplest way to do this is to create a directory somewhere that you will keep all your wine trees in. I use /source/wine/arch. Then do this: tla get mike(a)winehq.org--wine/wine--mainline--0.9 winehq cd winehq ./branch winecfg The branch script is in the root of the gateway tree, and is written by me. It's designed to let you rapidly branch a given Wine tree. It works by "tagging" the new tree in arch, then duplicating the current tree using hard links before finally forcing the duplicate tree to the new branch. WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! If you use the branch script you MUST use an editor that breaks hard links. emacs does by default, vim does if you :set bkc=no (though be warned, this will interfere with some programs that invoke vim like crontab -e). zile does not. If you want to use an editor that does not break hard links you must remove the -l option from cp in the branch script so a real duplicate is made. This uses more disk space and is slower to copy, but is safer. The result is a new directory called winecfg/ created as a sibling of the current directory. You can now commit to this tree however often you like. Running merge will update the branch from the tree you branched from (in this example, the gateway tree). You can branch from that tree again, and so on. Other people can branch from your tree in the same way! Feeling giddy with power yet? No? Good. Remember that patches which aren't in the mainline tree aren't reaching 99.9% of the users - being able to branch is useful but don't use it as an excuse to not get patches upstreamed! The new branch is put in the default archive and the name is derived from the current, for instance running branch in mike(a)winehq.org--wine/wine--mainline--0.9 with the parameter "winecfg" produces a branch with the name mike(a)navi.cx--2004/wine--winecfg--0.9 Now you need to publish a mirror: tla make-archive --mirror mike(a)navi.cx--2004 sftp://navi.cx/home/mike/public_html/archive and update it when you have done some commits tla archive-mirror which actually uploads the changes. If you are always connected, you can run the first make-archive command (back when you created your archive) with a remote location straight away, but doing it locally then mirroring is more common. Finally, tell people the URL of your archive so they can register it and grab your tree. That's it! Have fun! If you have any questions ask them on the wine-devel mailing list.

3 4

Ping: Gerald Pfeifer
by Dimitrie O. Paun 01 Apr '04

01 Apr '04

Hi Gerald, It seems nobody can send you email because: Recipient: <pfeifer(a)dbai.tuwien.ac.at> Reason: Service unavailable; Client host [fep03-mail.bloor.is.net.cable.rogers.com] blocked using abuse.rfc-ignorant.org; Not supporting abuse@domain; See http://www.dbai.tuwien.ac.at/block.html Nice, but that make the email account a bit useless, no? :) Anyway, I had a small question for you: what version of FreeBSD are you building Wine for? -- Dimi.

1 0

Re: shell32 patch 28
by Alexandre Julliard 01 Apr '04

01 Apr '04

"Martin Fuchs" <martin-fuchs(a)gmx.net> writes: > Changelog: > _ILCreateFolder(), _ILCreateValue(): check for NULL in AlternateFileName cAlternateFileName is an array, it cannot possibly be NULL. -- Alexandre Julliard julliard(a)winehq.org

1 0

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