January 2003 - Wine-Devel - list.winehq.org

Re: Conformance tests status update

by Steven Edwards

--- Francois Gouget <fgouget(a)free.fr> wrote: > > Yesterday I compiled and uploaded new Windows binaries for the > conformance tests. The new binaries contain a ton of fixes, in > particular for the following tests but there are more: If I start making binaries of the dlls we can build under Mingw such as comctl, shlwapi and ole* can someone test them using the conformance suite under NT/2K/XP or something mabey in bochs or VMware? Thanks Steven __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

Jan. 7, 2003

Re: Wine Fun v0.3

by Steven Edwards

I remeber seeing in the mingw-users list someone was able to build QT under Mingw although they were having issues with the size of the library and programs due to odd linking issues with libstdc++. I dont remeber the exact details except that the resulting binary was way larger then the Unix or MS_VC counter-part. Thanks Steven --- "Dimitrie O. Paun" <dpaun(a)rogers.com> wrote: > Hi folks, > > I haven't released a version of the Fun page in a loooong time, and a > _lot_ of things changed. In fact, I would say at least 90% of it has > changed since last time. Here it is for your viewing pleasure: > http://www.dssd.ca/wine/Wine-Fun-0.3.html > > Check it out, maybe you'll find something that tickles your fancy! ;) > > -- > Dimi. > > __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

Jan. 7, 2003

Re: getting started

by Dimitrie O. Paun

On January 7, 2003 03:39 am, Francois Gouget wrote: > 1. get the sources to a Linux machine > 2. run winemaker on the sources to generate Makefiles We should modify winemaker to use winegcc. There's now a lot of (bad) duplication between winemaker, and winegcc, like wrapper support, linking, etc. Moreover, having winegcc handle the linking details automatically, we (1) shield the users from all that nastiness, and (2) retain more freedom on changing things in the build process. More importantly, we should generate Makefiles that work as is on mingw as well. This would increase their usefulness considerably. My Perl knowledge approaches zero asymptotically, so I can't quite do this myself, but I am willing to help on it with what's needed. -- Dimi.

Jan. 7, 2003

Re: Agent File Access

by Oliver Sampson

On Sun, 05 Jan 2003 17:05:36 +0000, Oliver Sampson <olsam(a)quickaudio.com> wrote: >looking at the code, and since it was a *real* simple fix, it sorta >just fell by the way side.) Ahem. "since it was *not* a real simple fix...." No wonder no one understands me anymore. :-) ==================================================== Oliver Sampson olsam(a)quickaudio.com http://www.oliversampson.com

Jan. 7, 2003

Re: Agent File Access

by Oliver Sampson

Hi, I'm not sue what winepath does, and the 'winepath --help' doesn't seem to do much. What I'm talking about for Agent in particular, is that when Agent as a Windows program communicates with (for example) gimp as a unix program and passes a command line parameter, like a file path (it still thinks it's in C:\Data\agent rather than "~/data/agent", to open, all of the back slashes should be changed to forward slashes. How would I use winepath in this situation? Thanks, Oliver On Tue, 07 Jan 2003 12:03:30 +0100, Rein Klazes <rklazes(a)xs4all.nl> wrote: >On Sun, 05 Jan 2003 17:05:36 +0000, you wrote: > >> Howdy, >> I'd like to (finally) get around to fixing something that Agent does >> that's really annoying. When launching programs, it sends a string >> with backslashes for directory markers instead of forward slashes. >> >> Anyhow, if I'm going to start looking at the problem, could someone >> point me at the right file to begin looking at? I think I asked this >> some time ago, but I can't seem to find the email. (I remember >> looking at the code, and since it was a *real* simple fix, it sorta >> just fell by the way side.) > >Since then the tool winepath has been added. > > $ winepath 'E:\BIN\Agent\agent.ini > /dos/e/bin/Agent/agent.ini > >I think the recommended way is now to create a small script that uses >winepath. > >Rein. ==================================================== Oliver Sampson olsam(a)quickaudio.com http://www.oliversampson.com

Jan. 7, 2003

Re: dlls/Makefile.in

by Jeff Smith

>From: Marcus Meissner <mm(a)lst.de> > > >And I don't see a reason for this change, these entries are > > >generated by a script and who should care if they are longer or not? > > What script? > >dlls/make_dlls I did not see the line at the top of dlls/Makefile.in. Oh well, nevermind then. -- Jeff S _________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail

Jan. 7, 2003

Re: Agent File Access

by Rein Klazes

On Tue, 07 Jan 2003 14:44:53 +0000, you wrote: > Hi, > I'm not sue what winepath does, and the 'winepath --help' doesn't seem > to do much. I hoped the example would be enough. It does what I think you asked for, put path(s) known under wine and convert it to the unix path(s). > > What I'm talking about for Agent in particular, is that when Agent as > a Windows program communicates with (for example) gimp as a unix > program and passes a command line parameter, like a file path (it > still thinks it's in C:\Data\agent rather than "~/data/agent", to > open, all of the back slashes should be changed to forward slashes. > > How would I use winepath in this situation? The command: winepath 'C:\Data\agent' will output: /home/yourself/data/agent Use that in a little script, call it perhaps winegimp, that calls gimp with the correct (unix) path. Something like: #!/bin/sh gimp `winepath "$@"` I use something similar to launch gvim on the patches on the mailing list. Rein. -- Rein Klazes rklazes(a)xs4all.nl

Jan. 7, 2003

Re: [RFC] __WINESRC__ & public headers

by Dimitrie O. Paun

On January 7, 2003 10:44 am, Steven Edwards wrote: > Hehe I'm happy someone else wants to see this now. If there is someway we > can script testing with other headers mabey with perl or something (now > that MSYS has a decent perl) we can find where the WINE headers and others > are not in sync. If such as system was in place I would be happy to add it > to my testing routine. The hard part is getting Wine to compile with other headers. Once that's done, I don't think we need any script: just capture the compiler output, and go fix the warnings... We can go fancy if we want to do this automatically from time to time, but this is just us geeks going crazy. Let's get first Wine to compile with w32api (or even better with the MSVC headers!), that's where the hard work is. -- Dimi.

Jan. 7, 2003

Re: Conformance tests status update

by Dimitrie O. Paun

On January 7, 2003 10:20 am, Steven Edwards wrote: > If I start making binaries of the dlls we can build under Mingw such as > comctl, shlwapi and ole* can someone test them using the conformance suite > under NT/2K/XP or something mabey in bochs or VMware? Why in bochs or VMware? Just throw them in Linux Wine, they should work just fine. And it would be a fine experiment, BTW. Just put them in you fake windows/system dir, and run with --dll <name>=n. -- Dimi.

Jan. 7, 2003

Re: Wine Fun v0.3

by Dimitrie O. Paun

On January 7, 2003 10:16 am, Steven Edwards wrote: > I remeber seeing in the mingw-users list someone was able to build QT under > Mingw although they were having issues with the size of the library and > programs due to odd linking issues with libstdc++. I dont remeber the exact > details except that the resulting binary was way larger then the Unix or > MS_VC counter-part. If you know more about the port, I'd love to take a shot of making it work under Wine. Even if it doesn't link, it's not a big deal -- the important part is the compilation. Maybe you can find it again... <g> -- Dimi.

Jan. 7, 2003