- Wine-Devel - list.winehq.org

Winamp 3
by Brian Vincent Dec. 19, 2003

Dec. 19, 2003

Looks like Nullsoft has released the Winamp 3 code as open source. I have no idea what their build process is like, but maybe porting it could be added to the Winelib page? http://www.wasabidev.org/ -brian

1 0

will not compile projects.
by Elizabeth Kowalsky Dec. 19, 2003

Dec. 19, 2003

hello: I am insterested in poring the Fluke Networks Linkware to Linux. I get the following when I issue the commands when I am in teh directory where I want to port the app from: [princessangry(a)localhost system]$ winemaker --lower-uppercase . Winemaker 0.5.9 Copyright 2000 Francois Gouget <fgouget(a)codeweavers.com> for CodeWeavers Scanning the source directories... Fixing the source files... Generating project files... . [princessangry(a)localhost system]$ ./configure --with-wine=/princessangry/.wine checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking how to run the C preprocessor... gcc -E checking whether ln -s works... yes checking for sqrt in -lm... yes checking for iswalnum in -lw... no checking for gethostbyname... yes checking for connect... yes checking for gcc strength-reduce bug... no checking whether we can build a Linux dll... yes checking whether we need to define __i386__... checking for egrep... grep -E no checking whether we need to define __sparc__... no checking whether we need to define __sun__... no checking whether we need to define __powerpc__... no checking for g++ -fpermissive option... yes checking for g++ -fno-for-scope option... yes checking for windef.h... configure: error: Could not find the Wine headers (windef.h) I cna not find the windef.h file anywhere!!! Please help!!! thanks PrincessAngry

3 2

Re: [Resend] SHLWAPI fixes.
by Dmitry Timoshkov Dec. 19, 2003

Dec. 19, 2003

"Flameeyes" <dgp85(a)users.sourceforge.net> wrote: > The attached patches fixes some functions of shlwapi I needed to run an > application I wrote with BCB that was using MS XML Parser. > I'm using it and works well AFAIK. > @@ -2346,6 +2376,9 @@ > } > StrCpyW(pszPointer, pszPath); > StrCpyW(pszUrl, pszNewUrl); > + > + LPWSTR slash; > + while((slash = StrChrW(pszUrl, '\\'))) *slash = '/'; > return S_OK; > } Your patch will not compile with older C compilers. You need to put variables on the top of the function body. Please resend. -- Dmitry.

1 0

DC ownerdrawn background mode
by Fabian Cenedese Dec. 18, 2003

Dec. 18, 2003

Hi I have a control derived from CListCtrl. It's completely ownerdrawn. The problem comes when some item is selected. The whole column is drawn selected but the text is drawn with the actual back color instead of transparent. As this is white I get white text on white background... very readable :) I found that the difference between Windows and wine is the background mode. In Windows it's transparent whereas in wine it's opaque. I never change the background mode in my app, I guess I just lived from the fact that it's default transparent. Where is this set? Is this a wrong default parameter in wine or do I explicitly have to set the background mode in my app? I can do this, then it shows ok. But that's another change to my application I have to do because of wine. Maybe other apps may have similar problems. bye Fabi // from my code: void CMyCtrl::DrawItem(LPDRAWITEMSTRUCT lpDrawItemStruct) { // Prepare and test device context CDC* pDC = CDC::FromHandle(lpDrawItemStruct->hDC); // this is 1 for windows but 2 for wine // pDC->GetBkMode(); // wine fix pDC->SetBkMode(TRANSPARENT);

2 1

Fwd:SourceForge.net Sitewide update: Dec 9th, 2003
by Ivan Leo Murray-Smith Dec. 18, 2003

Dec. 18, 2003

>Projects will need to ''opt-in'' in order to accept >donations. Dimi, are you going to opt in?

4 3

Fix for debugger breakage
by Mike Hearn Dec. 18, 2003

Dec. 18, 2003

Hi, What is the status of this problem? I tried setting WINELOADER to point to wine-pthread, and while that allowed winedbg to load symbols it spewed loads of errors while doing so. Is there a proper fix for this? BTW I think the recent URL Cache patch broke the IE setup program, I get a crash there calling InterlockedExchange with a null pointer dereference. thanks -mike

3 6

winedbg question
by Chris Morgan Dec. 18, 2003

Dec. 18, 2003

Should winedbg be able to load symbols up for non-wine libraries? After the export WINELOADER idea I've got wine symbols but I'm still trying to debug a bizzare crash in winejack where I get: ~/c$ wine sndrec32.exe Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: Segmentation fault and when running under winedbg: *** Invalid address 0x40017f40 (_end+0x2ff03f40) Loaded debug information from ELF '/usr/local/lib/wine/ midimap.drv.so' (0x41090000) In 32-bit mode. Wine-dbg>cont Stopped on breakpoint 1 at 0x0100d32e (sndrec32.exe.EntryPoint in sndrec32.exe) Wine-dbg>cont Invalid address for breakpoint 1, disabling it Invalid address for breakpoint 2, disabling it Process of pid=0000000a has terminated Wine-dbg> >From single stepping I've found the function where the segfault appears to occur but its inside of jack_activate() in libjack.so.0 but symbols for this library don't appear to be loaded: *** Invalid address 0x40017f40 (_end+0x2ff03f40) No debug information in ELF '/usr/local/lib/libjack.so.0' (0x40f56000) No debug information in ELF '/lib/tls/librt.so.1' (0x40f62000) nm libjack.so.0 lists a bunch of symbols and I'm able to set a breakpoint on jack_activate() using gdb on a native linux app so it looks like debug information is built into libjack.so.0. Thanks, Chris

4 5

Problem with "exec shield" workaround
by Troy Rollo Dec. 18, 2003

Dec. 18, 2003

The "exec shield" workaround (loader/main.c, libs/wine/port.c) has a side-effect of leaving a several thousand byte area of memory allocated just after the reserved pe_area. Under Windows, it is possible to fairly reliably map files or allocate memory explicitly using a fixed address of 0x10000000. The left-over memory from the loader causes programs that rely on this to fail. It seems that this workaround should either be a user setting or should mmap the memory area desired so that it can be removed without leaving behind a small fragment after that area.

1 0

default config file creation
by Chris Morgan Dec. 17, 2003

Dec. 17, 2003

I was chatting with Rudolf Kastl(che on #winehq) and he was mentioning the things that he was doing for the rpm package. One of the patches he applies to wine prior to packaging it is a patch that creates local user config files if they don't exist. This helps end users as they don't have to worry about the package maintainer providing valid config files. I thought this sounded like a pretty neat idea to improve usability. The patch currently copies files from /etc/* which means they would need to be installed there during the process. I was wondering if it would make more sense during the compile process to take the default configuration files, config, system.reg, user.reg and userdef.reg and convert these to binary form and compile them into the wine binary itself. We could detect the lack of these files at startup and install them for the user. Another feature could be a command line switch that would rebuild a users config, like: 'wine --rebuild-config' that would reset the users config back to the defaults. Sound like something reasonable? Should we instead be putting the default files somewhere on the users machine and copying them over like the patch does? Chris

2 3

Re: default config file creation
by Ivan Leo Murray-Smith Dec. 17, 2003

Dec. 17, 2003

> Trading off configurability with usability seems fine to > me. We aren't as one can tweak things with winecfg if he wants/needs to > The goal is to solve both > the lack of config files for binary installs, fixed by the > patches that Che has in his rpm package and Marcus has for > Suse, and for users that run 'make install' but never > create config files. All this can be solved by shipping a config file with with wine, get wine to adapt it to the users system, install it, install the registry and create the fake windows partition. This would work for all binaries on all distros, even on freebsd, and would work when installing from source. Only that someone has to implement it. And volunteers?

1 0