- Wine-Devel - list.winehq.org

Mystery solved: acoc breaks Wine's configure!
by Dan Kegel Oct. 23, 2005

Oct. 23, 2005

Here's the strangest thing I've seen for a while. I was tracking down why I could build Wine, but another guy on the same machine could only build a slightly broken Wine that gave the error Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5. whenever you tried to use it. The first clue was funny output from Wine's configure script, though it was hard to see until I diff'd against good output, and used cat -v to make invisible chars visible: --- configure.log.good.txt 2005-10-20 10:57:21.000000000 -0700 +++ configure.log.bad.txt 2005-10-21 14:41:59.000000000 -0700 ... -checking for ldd... /usr/bin/ldd -checking for -lX11 soname... libX11.so.6 -checking for -lXext soname... libXext.so.6 ... +checking for ldd... /home/mmoss/bin/ldd +checking for -lX11 soname... libX11.so.6^[[0m +checking for -lXext soname... libXext.so.6^[[0m And what's that funny ldd? And what are those escape sequences? Turns the ldd is one wrapped by acoc (http://www.caliban.org/ruby/acoc.shtml) which colorizes the output, which also explains the funny escape sequences. This error went away when we stopped using acoc to colorize the output of commands like ldd. We had been using acoc-0.5.2, but the latest version (0.7.1) also exhibits the problem. I hope this helps somebody else who's scratching their head over strange build failures! - Dan

2 1

Re: shell32: Remove redundant .\\ from test files
by Jakob Eriksson Oct. 23, 2005

Oct. 23, 2005

James Hawkins wrote: >Hi, > >I started by removing all .\\ from the shlfileop.c test file in msvc >and the tests all passed , but three of the tests failed in wine. > > If the tests fail on wine, should they not be todo_wine{} then? regards, Jakob

2 1

Re: Shell32 File Property dialog
by Mike McCormack Oct. 23, 2005

Oct. 23, 2005

Johannes Anderwald wrote: > I have a patch which adds file property dialogs to shell32 Looks like you've written the patch for ReactOS... it doesn't apply to the current Wine tree. I think you need to do a little bit more work to get it ready for submission: * use TRACE instead of DPRINT * don't use %S in debug statements (with TRACE) it's not portable, use %s and debugstr_w(str) instead * in SH_FileVersionDlgProc you miss a break at the end of WM_COMMAND * the formatting is all over the place. 4 space indent, no tabs is prefered * make sure to use the A or W functions and types explicitly. eg. you use PROPSHEETPAGE where you should use PROPSHEETPAGEW. * this comments looks dodgy: "SH_FileTimerProc is invoked every 100ms to check if the property sheet should be closed required because the property sheet pages are MODELESS" Your Window proc will get a WM_CLOSE when you need to close, or WM_DESTROY when it is destroyed. Freeing memory and other things that need to be done when the window is closed should happen in the Window procedure, and there should be no need for a timer. Please take the time to build you patch with and generate it against the CVS version of WineHQ. thanks for the patch, Mike

1 0

Solaris Updates
by Robert Lunnon Oct. 22, 2005

Oct. 22, 2005

I have posted my local patches to wine-patches. Note that for 0.9 I have posted most of the patches that are likely to be essential to build a working Wine package (other than those previously rejected) regardless of the shape the code is in. Some of it is very ugly and lacks integration for other OSen, I have noted these. Since this code is maintained as a delta from CVS wine specific to Solaris and only used for binary packages, it's not necessary to start out with the niceties all there (This particularly happens when I get deep into week long debugging sessions). Patches not sent are listed hereunder long with the reasons... Possibly essential (Show stoppers) ptrace stub patch - Disable debugger by returning error for all ptrace calls, add ptrace stubs (framework) to allow work on ptrace emulation layer for wine. -Previously rejected linking patch - since libwinecrt0.a was added wine has been broken due to the linker wanting to import main() in dlls, this results in unresolved symbols. I have temporarily worked around this and can build wine with a change to winegcc that links another archive (I call winedllcrt0.a) which omits the main() definitions in the case where -shared is passed to winegcc. Alexandre has asked that I keep looking for a way to make the Solaris linker successfully link an archive containing main() to dlls without the need to have two runtime startoff libraries. Patch won't be submitted until a final solution is found. Recommended functionality patches cpuid patch - CPUID detection using x86 cpuid instruction - previously rejected wineconsole/curses.c - Patch non-essential and FAR too hacky at this point - just removes all mouse code. Other Patches tools - automation patches to allow unattended build No interest to Wine project Debugger - work in progress, not working A complete set of patches (even the gross ones) are maintained at http://www.blastwave.org/wine

1 0

Re: dinput: Fix mouse poll and few other bugs
by Stefan Dösinger Oct. 22, 2005

Oct. 22, 2005

Am Samstag, 15. Oktober 2005 18:49 schrieb Magnus Olsen: > Hi > This change allown me run all MS DirectInput sample with out any problem. > it also take care of bad writen dinput program that try getting the mouse, > Without calling on right api, see my commmect in dinput. I have not > tested in wine, But I have tested it in ReactOS and Windows. Did you forget to attach the patch?

1 0

autoexec.bat and pif's which run batch files
by paul Oct. 22, 2005

Oct. 22, 2005

I have not seen this one problem listed and it may be a 1.0 target. Filed bug 3638. Legacy installers modify autoexec.bat to add the install directory to the path and may also use set's. After the installer installs the program will not run as it's bin directory is not in the path. This also could be a reason why many applications only work when run from the directory it is installed in. If windows type is set to 95 or less in winecfg then autoexec should be processed before running the program. I also have programs which uses a pif to run a batch file. The batch in a pif is disabled/stubbed. I plan to look at filling it that feature when I get some time. Paul Romanyszyn

1 0

Roadblock #1 for VB installers: MDAC
by Dan Kegel Oct. 22, 2005

Oct. 22, 2005

A lot of VB apps use MDAC (http://msdn.microsoft.com/data/mdac/downloads/) They tend to include mdac_typ.exe, the mdac installer, and run it, but unfortunately, Wine doesn't seem to run it properly. (I'm testing using mdac 2.7 sp1, fwiw.) First, the MDAC installer refuses to run unless the registry key for IE6 is present. (OK, that's easy to work around... if you're a programmer. It probably ought to be a winecfg pulldown.) Second, even if the MDAC installer runs, all it does is install a bunch of directories under c:\windows\RegisteredPackages. The DLLs needed by the VB app are locked up in .cab's in those directories. In the app I'm trying to install, the installer then fails with err:module:import_dll Library MSDART.DLL (which is needed by L"C:\\windows\\system32\\msadox.dll") not found Something, somehow, is supposed to be triggering an unpack, but it's not happening. (See http://msdn.microsoft.com/workshop/delivery/download/download_node_entry.asp for a discusion of how the unpacking is supposed to go on Windows.) I've filed a bug report at http://bugs.winehq.org/show_bug.cgi?id=3636

1 0

Are Visual Basic install problems common?
by Dan Kegel Oct. 21, 2005

Oct. 21, 2005

Is it common for Visual Basic applications to have problems installing under Wine? Take the recent post by Denis, for instance. He's trying to install a fairly complex Visual Basic app that uses MDAC, and the installer just won't run properly under Wine. (I've corresponded with him privately, and can give more details if desired.) I have this feeling that this isn't an isolated instance. Maybe there are hundreds of thousands of businesses and government offices that have large collections of VB apps written in-house, not yet ported over to VB.NET, which they'd like to run under Wine -- but they take one look at the trouble they have installing, and give up. Does anyone have experience rolling VB (not VB.net) apps here? Is it easy to create VB apps that install fine under Windows, but not under Wine?

3 6

version: updated trace for VERSIONED_PRINTER (v3)
by Detlef Riekenberg Oct. 21, 2005

Oct. 21, 2005

Changelog: > - updated trace to support VERSIONED_PRINTER > This time without deleting the TRACE for the flags. Informations on the Web: "Specifying Printer Driver Version Numbers" > http://msdn.microsoft.com/library/en-us/graphics/hh/graphics/prtinst_17e31a… > -- By By ... ... Detlef

1 0

ActiveX controls in MSHTML?
by Dan Kegel Oct. 21, 2005

Oct. 21, 2005

A systems integrator mentioned that many commercial ERP applications use ActiveX terminal emulator controls embedded in web pages. (I think http://www.zephyrcorp.com/terminal-emulator-activex-document.htm is an example of such an ActiveX control.) Presumably these will run in IE on Wine, but will they run in the new MSHTML browser that's part of Wine? (Sorry if my terminology is a bit off - I haven't played with mshtml ever.)

3 2