wine-devel

wine-devel@winehq.org

3 participants
84471 discussions

AutoCad 2000 latest status ?
by John 06 Jan '04

06 Jan '04

I know there are interests in autocad 2000 status with wine. I was happy to read in http://appdb.winehq.org/appview.php?appId=86&versionId=102 that autocad 2000 actually starts up now, although there seams to be a file open problem. I just wanted to forward this news in case someone is interested in fixing the details now that it at least starts up. ________________________________________________________________________ Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html

2 1

Hack for the '-pthread' at make depend
by P. Christeas 06 Jan '04

06 Jan '04

On my configuration, the 'artsc-config' script outputs '-pthread' along with the '-Isth' entries. That broke the 'makedep' procedure. It's trivial. The following patch handles this.

3 6

Re: install default config files to $PREFIX/share/wine
by Boaz Harrosh 06 Jan '04

06 Jan '04

<Patch> Index: include/olectl.h =================================================================== RCS file: /home/wine/wine/include/olectl.h,v retrieving revision 1.19 diff -u -r1.19 olectl.h --- include/olectl.h 5 Sep 2003 23:15:44 -0000 1.19 +++ include/olectl.h 5 Jan 2004 08:24:39 -0000 @@ -97,7 +97,11 @@ BOOL fStrikethrough; } FONTDESC, *LPFONTDESC; -#define FONTSIZE(n) { n##0000, 0 } +#ifdef __cplusplus +# define FONTSIZE(n) ( n##0000, 0 ) /*use constructor*/ +#else +# define FONTSIZE(n) { n##0000, 0 } +#endif /*__cplusplus*/ #define PICTYPE_UNINITIALIZED (-1) #define PICTYPE_NONE 0 </Patch> Some simple fix for C++ with the macro FONTSIZE So ATL and MFC can compile.

2 2

Re: Re: Using winebuild explicitly
by Dimitrie O. Paun 06 Jan '04

06 Jan '04

> There is at least one difference in using a wrapper & dll vs. > using a single executable: The function GetModuleFileName > doesn't yield the path to the program (the wrapper) with the > wrapper-approach (there was some discussion on this in another > recent thread). Thus, having such flag in winegcc would indeed > be nice... Alexandre is working on a patch to completely remove the need for such wrapper. Hopefully it will be committed soon enough so we will not have to create such an option. > Did so. wineg++ invokes winewrap (without passing on the > "-v" flag, though) which in turn generates same files > and compiles them. Yes, it doesn't, but you can just copy the winewrap command, add the -v and invoke it manually. > The directory in which libwine.so.1 lives, is contained in my > /etc/ld.so.conf. Are you saying this should be enough for gcc > to find the library file? Right, that's how I thought it's supposed to work. Did you rebuild the ld cache after updating /etc/ld.so.conf? -- Dimi.

2 2

Re: Re: install default config files to $PREFIX/share/wine
by chmorgan＠charter.net 06 Jan '04

06 Jan '04

Registering the dlls? Is this the same as loading them? How would we know which dll was responsible for creating which registry entries? Is it that clear which one should do it? Would the code called during registration check to see if the default keys existed and if it didn't install the default values? Would the inf file be mostly keys we've added for workarounds with apps like installshield installers? I'm asking because I'd really like to have wine create its own default config to simplify the users life and wineinstall, and I'd also like to simplify package managers lives so they don't need to many special scripts. I'm also interested in integrating the ~/.wine/config file into the registry. So feel free to suggest places to look, work and what direction to head. Chris > > From: Alexandre Julliard <julliard(a)winehq.com> > Date: 2004/01/05 Mon PM 04:46:59 EST > To: cmorgan(a)alum.WPI.EDU > CC: <wine-devel(a)winehq.com> > Subject: Re: install default config files to $PREFIX/share/wine > > <chmorgan(a)charter.net> writes: > > > How do we plan to get rid of having default config files? Where would the default registry go? > > It will be created on the fly by registering the various dlls and > creating the remaining needed keys, most likely through a setupapi > .inf script. > > -- > Alexandre Julliard > julliard(a)winehq.com > >

2 1

Any experts on IsDialogMessage
by Bill Medland 06 Jan '04

06 Jan '04

Hi All Happy New Year to everyone and Welcome Back to Alexandre I am just about to start concentrating on IsDialogMessage, especially in the non-dialog context. Our program (suite) uses ActiveX controls extensively and is difficult to use because the TAB handling in particular is totally wrong. I will be using a trivial program with IsDialogMessage inserted into the main loop and will be trying to figure out the undocumented behaviour of this function (e.g. I am sure it internally handles redirecting to children etc.) The only comments I've noticed so far (about a year back) suggest that we really don't know much about this function, but I thought I'd ask if someone else has notes about what is wrong with it, how it should work, alternative web sites etc. or has uncommitted patches etc., just so that I don't duplicate work. All comments welcome -- Bill Medland

2 4

[Bug 1903] using dead_diaeresis i.e. e + ¨ hangs wine
by grant williamson 06 Jan '04

06 Jan '04

Hi, not sure if anyone else has experienced this. since patch http://cvs.winehq.com/patch.py?id=10332 was added to cvs (20031205), if I type a dead_diaeresis - "¨" followed by a letter, which would normally produce a "ë" or a "ü" it simply makes wine hang. removing this patch(I removed it on latest cvs) and the problem goes away, can someone find out why this causes an issue? -- grant williamson <traxtopel(a)fastmail.fm>

4 4

Windows dll replacement with Linux library
by Dan Timis 06 Jan '04

06 Jan '04

Hi, I wrote to the list a few weeks ago. I needed to support a USB device without changing the Windows dll that I have to use. I was trying to hack into wine to implement support for the USB device using CreateFile() and DeviceIoControl(). That was not a clean solution. The author of the Windows dll has agreed to support a mid level dll that would implement functions like USBDeviceOpen(), USBDeviceClose(), USBDeviceRead(), and USBDeviceWrite(). On Windows those would use CreateFile() and DeviceIoControl(), while on Linux they would use libusb calls. I followed the example from winelib user guide, chapter 5 "Using Linux libraries as DLLs" As an example I will talk just about USBDeviceOpen(). Here it is how it is declared together with a proxy function: HANDLE WINAPI USBDeviceOpen(const DWORD in_dwIndex); HANDLE WINAPI USBDeviceOpenProxy(const DWORD in_dwIndex); This function opens a specific device from a specific manufacturer. If more than one device connected In the spec file I put: 101 stdcall USBDeviceOpen (long) USBDeviceOpenProxy I used winemaker, configure, make, and make install. Now I have "USBUtils.dll.so in /

2 5

Re: netapi32: implement NetServerEnum and NetShareEnum
by Alexandre Julliard 06 Jan '04

06 Jan '04

Juan Lang <juan_lang(a)yahoo.com> writes: > Relies on previously submitted SMB patch, > http://www.winehq.org/hypermail/wine-patches/2003/12/0231.html > > ChangeLog: partially implement NetServerEnum and > NetShareEnum using RAP over SMB You can't share C files across dlls, this violates dll separation and it won't build properly. -- Alexandre Julliard julliard(a)winehq.com

8 23

#5 - Re: #pre5 - comdlg32 MS_VC + PSDK porting
by Steven Edwards 05 Jan '04

05 Jan '04

--- Alexandre Julliard <julliard(a)winehq.com> wrote: > > I am calling this patch pre5 rather than #5 because it doesnt fully > > address the rest of the PSDK porting issues and one of my new years > > resolutions for 2004 is for every patch I send to winehq to be good > > enough to go right in to CVS. ;) > > That's certainly won't happen if you don't attach the patch <g> Hehe your right. Its a good thing it was called pre5. After this one there are still a few minor things with one of the source files calling Heap_StrsupWtoA that needs to be moved inline and the NONAMELESS stuff. I have not done any work to address the NONAMELESSSTRUCT stuff except to just remove all cases of s1.u1 in ReactOS sources I ported. None of my patches to wine-patches reflect this change. If this is accepted I will send a patch in a few days to remove printdlg.h and to move a strdupW2A function inline in the offending source file. Once these changes are done and the NONAMELESS stuff is solved then comdlg32 will be mostly done of all Win16/32, PSDK and Wineism cleanups. I think there is a function or two left that I need to check the declairations of like I have been with NetAPI32 and Setupapi. Thanks Steven __________________________________ Do you Yahoo!? Find out what made the Top Yahoo! Searches of 2003 http://search.yahoo.com/top2003

1 0

Is there already a function for this?
by Bill Medland 05 Jan '04

05 Jan '04

Does anyone know if we already have a function that measures the true length of a window's text in the following way l = SendMessage (hwnd, WM_GETTEXTLENGTH,..) presumably allocate a buffer SendMessage (hwnd, WM_GETTEXT, 2(l+1)..) Then actually measure the retrieved text. -- Bill Medland mailto:billmedland@mercuryspeed.com http://webhome.idirect.com/~kbmed

1 0

Using winebuild explicitly
by Ralf Juengling 05 Jan '04

05 Jan '04

Hi Dimi, On Wed, 2003-12-31 at 16:47, Dimitrie O. Paun wrote: > On December 31, 2003 07:42 pm, Ralf Juengling wrote: > > okay, now it's as before: > > As I said, I think there's something wrong with your > ld setup. You need to have /usr/local/lib (where > the libwine library is) in your /etc/ld.so.conf: I tried this today, (adding /local/lib to /etc/ld.so.conf) but it didn't make a difference. I then looked into winegcc.c and winewrap.c to find out what winwgcc is actually doing. It is creating a shared library (dll) and a little wrapper executable to load the shared library. This should not be necessary with the code in question and I would rather like to build just one executable. So I wrote a Makefile that does this (not using winegcc & co) by calling winebuild explicitly (see below). It seems to work, but when I start the executable by wine phaeaco.exe.so I see the application's windows appearing and immediately disappearing and get the following error messages: err:win:WIN_FindWndPtr window 0x20030 belongs to other process err:win:WIN_FindWndPtr window 0x20030 belongs to other process I wonder whether this error has to do with the way I built the executable. The Makefile is as follows: ------ Makefile ------------------------------------------ INCLUDE_PATH = /local/include/wine LIBRARY_PATH = /local/lib # This should be replaced by wildcard expression as soon as all # sources actually participate in the built. PHAEACO_CSRCS = ../gensrc/Statist.c PHAEACO_CXXSRCS = Experim.cpp Login.cpp Phaeaco.cpp TextWnd.cpp \ Intrface.cpp Mentor.cpp Solver.cpp List.cpp ... (some more) PHAEACO_RCSRCS = phaeaco.rc PHAEACO_DLLS = advapi32 comdlg32 gdi32 kernel32 odbc32 ole32 \ oleaut32 shell32 user32 winspool winmm comctl32 DEFINES = -D__WINE__ INCLUDES = -I. -I../geninc -I../coginc -I$(INCLUDE_PATH) -I$(INCLUDE_PATH)/windows CC = gcc CFLAGS = -g -fpack-struct $(DEFINES) CXX = g++ CXXFLAGS = -g -fpack-struct $(DEFINES) CPPFLAGS = $(INCLUDES) OBJS = $(PHAEACO_CSRCS:.c=.o) $(PHAEACO_CXXSRCS:.cpp=.o) RESS = $(PHAEACO_RCSRCS:.rc=.res) LDFLAGS = -L$(LIBRARY_PATH) -L$(LIBRARY_PATH)/wine LIBS = -lwine -lm WBLIBS = $(patsubst %,-l%,$(PHAEACO_DLLS)) phaeaco.exe.so : $(OBJS) winebuild -o phaeaco.spec.c --exe $(@) -mgui $(OBJS) $(RES) $(LDFLAGS) $(WBLIBS) gcc -o phaeaco.spec.o -c phaeaco.spec.c $(CXX) -shared -Wl,-Bsymbolic,-z,defs -o $@ phaeaco.spec.o $(OBJS) $(LDFLAGS) $(LIBS) strip --strip-all $(@) %.o : %.cpp $(CXX) -c $(CXXFLAGS) $(CPPFLAGS) -o $@ $< %.res : %.rc wrc $(DEFINES) $(INCLUDES) -o $@ $< clean: rm -f ./*.o ../gensrc/*.o ../cogsrc/*.o -- Ralf Juengling <juenglin(a)cse.ogi.edu>

2 2

Re: install default config files to $PREFIX/share/wine
by Alexandre Julliard 05 Jan '04

05 Jan '04

Chris Morgan <cmorgan(a)alum.wpi.edu> writes: > * configure.ac, Makefile.in, documentation/Makefile.in, documentation/samples/ > Makefile.in > Chris Morgan <cmorgan(a)alum.wpi.edu> > Install default wine configuration files to $PREFIX/share/wine for use by > packages and by future changes to create a default configuration if none is > present. I don't think we want that. Future changes are supposed to get rid of the need for a config file, so we don't want to give the impression that external apps can depend on finding a sample config file. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: How can I run a program compiled with winelib when wine has b een uninstalled.
by Brian Vincent (C) 05 Jan '04

05 Jan '04

>> I'm making efforts to let a program which is compiled with winelib run with >> wine uninstalled. This program was for windows initially, I managed to >> compile it under Linux(Redhat) with winelib. Now I have got the files >> "program" and "program.exe.so" and they run well on a PC with wine >> installed, but I want it to run with wine uninstalled. > >This will not work. Why would you try to do that anyhow? I'm guessing it's because he wants to distribute the Winelib app. The folks installing probably won't have Wine on the system. Which brings up a good point, is there an easy way to distribute one? What comes to mind would be some way to adapt the Wine binary distributions (RPM's, .tgz's) to also install an application at the same time. --------------- Brian Vincent Copper Mountain Telecom vincentb(a)coppercolorado.com

4 3

How can I run a program compiled with winelib when wine has been uninstalled.
by Bruce Zhang (HangZhou) 05 Jan '04

05 Jan '04

Dear all, I'm making efforts to let a program which is compiled with winelib run with wine uninstalled. This program was for windows initially, I managed to compile it under Linux(Redhat) with winelib. Now I have got the files "program" and "program.exe.so" and they run well on a PC with wine installed, but I want it to run with wine uninstalled. I think I can realize that by copying the .so files located in /usr/local/lib/wine to a new place and use them, but there are still problems, I got a "Segmentation fault" by now. Who can tell me how can I do with it or if the idea is feasible? I am a newbie of winelib, I've browsed the articles of the last three months in the mailist but couldn't find the answer I want. Any help will be sincerely appreciated. Bruce Zhang

2 1

Make the winehq.org domain the official one.
by Sylvain Petreolle 04 Jan '04

04 Jan '04

winehq.org has been stated as the official one on last month. Today, it doesnt apply to the bugzilla site, since we still receive bugzilla notifications with the .com domain. Shouldnt this part be changed too ? =============================================== De: "Wine Bugs" <wine-bugs _at_ winehq.com> http://bugs.winehq.com/show_bug.cgi?id=1434 Bug 1434 depends on bug 1587, which changed state. Bug 1587 Summary: Several games don't work anymore http://bugs.winehq.com/show_bug.cgi?id=1587 What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED -- Configure bugmail: http://bugs.winehq.com/userprefs.cgi?tab=email ===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 Say NO to software patents Dites NON aux brevets logiciels "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". _________________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

1 0

Re: DMUSIC: my latest work
by Alexandre Julliard 04 Jan '04

04 Jan '04

Rok Mandeljc <rok.mandeljc(a)email.si> writes: > Hey everyone, > > I finally found some time to organise my dmusic work of last two months > in useful patch. Dmusic is now DX9 compatible, we have almost fully > implemented (but not working :( ) The dmusic_common.c thing is wrong, you can't use the same source file in multiple dlls, this won't build properly. Also you should not include private header files from other dlls, if definitions really have to be shared they should be in a common header somewhere in include/ or include/wine, though in most cases you should be able to avoid that. -- Alexandre Julliard julliard(a)winehq.com

3 5

Re: PATCH: Fix DLL constructors on OpenBSD
by wiml＠underhill.hhhh.org 04 Jan '04

04 Jan '04

Alexandre Julliard <julliard(a)winehq.org> writes: > The way it normally works is that the _init() function is built from > the contents of the .init section, so if you add code in .init it's > supposed to show up in _init(). Ah, right. This doesn't work on OBSD because __init() is fully defined in crtbeginS.c, instead of being split between crtbegin and crtend as in most gcc targets, so code added to .init is not executed. > [....] So there are two separate mechanisms, and > the constructors are built on top of the .init stuff. In our case we > need to be in .init because the constructors are normally called after > the rest of the .init code. It doesn't appear that the .init code on OpenBSD does anything before calling the functions listed in .ctors. (Well, that's not quite true: it sets a flag before calling the ctors.) As long as the foo.spec.o file is listed early on the linker's command line, its constructor(s) should be called before any others. The .so's destructors are called in the reverse order. What is it that _init() does on Linux, that the DLL init code needs to run first? I'd be interested in trying to write an autoconf test or something, if possible. Wim.

5 5

Warning: .stabs: description field ...
by Uwe Bonnes 04 Jan '04

04 Jan '04

Hallo, since some days, make in wine/programs/winetest produces: gcc -c -I. -I. -I../../include -I../../include -D_REENTRANT -fPIC -Wall -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o winetest.exe.spec.o winetest.exe.spec.c /tmp/ccOKsOhH.s: Assembler messages: /tmp/ccOKsOhH.s:852680: Warning: .stabs: description field '1a1be' too big, try a different debug format /tmp/ccOKsOhH.s:852683: Warning: .stabs: description field '1a1c7' too big, try a different debug format /tmp/ccOKsOhH.s:852686: Warning: .stabn: description field '1a1c7' too big, try a different debug format This is on a Suse 9.0 system. Is this a problem with my setup or do others observe it too? Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

3 2

winecfg to configure directsound options?
by Chris Morgan 04 Jan '04

04 Jan '04

I was planning to add the audio driver as a configuration option in winecfg but had a few questions. Does anyone use the directsound options? If so it probably makes sense to have an "Audio" tab in winecfg with the audio driver and the dsound options. If not then it might make sense to put the audio driver alone on another page, maybe the general config page? Should we have a multimedia page? What other multimedia options would go there? Thanks, Chris

3 2

Status ToDo's #2
by Tom 04 Jan '04

04 Jan '04

Comments, Suggestions? Tom

5 6

Re: Congradulations - windef.h
by Ivan Leo Murray-Smith 04 Jan '04

04 Jan '04

>You cannot use KDevelop 2.1 release with wine. Too many files to deep. >It will crash trying to import that project. (After 10 minuets of a >progress bar) Sucessfully imported, configured, currently building in KDevelop 2.1 shipped with Mandrake Linux 9.2 Ivan.

2 1

Congradulations :-}
by Boaz Harrosh 04 Jan '04

04 Jan '04

Just wanted to let people know. And share this happy moment with my fellow workman I have successfully Beta released a WinLib port of a, 1 million lines of code, windows program. QA will Install a first Linux Machine and will start to bang on it tomorrow. (Well more like an advanced Alfa I guess) Technologies successfully compiled and running in the Project: - Windows GUI & API (wrapped in an Old C++ lib, ZAFF). - ODBC under CRecordSet from MFC - I use the MSSQL drivers, SQLing data from a neighboring WinXP-SQL Server. I used an mdac.exe installation application from Microsoft. With ODBC32 native DLL. - General MFC contains, Strings, OleDispatch OleVariant OleBSTR... and even some GUI. - Actually to manage that I had an MSVC++ wizard generated MFC MDI Application with ODBC access and forms. Which helped me debug the MFC library. So MFC is pretty much covered. - ATL/WTL OCX hosting and General ATL use for anything COM. - Here too a WTL app-wizard generated MDI application with IE and other OCXes on Forms help me verify the ATL subsystem. Including support for "uuidof", "#pragma property" and more. Hosting and Events work fine. ( actually ActiveX controls compile too, but TLB problem must be resolved.) - A solution for Linking with C++ shared libraries that in-turn also use windows API. (I call them C++ fake DLLs.) - C++ STL from STLPort ported to Wine to compile using msvcrt (and MFC) And more stuff I cannot remember now. By far the biggest problem was the msvcrt vs STL. and other native C++. This caused a big Linking problem where STL would bypass msvcrt but other application code would not. This proved to be fatal. From circular linking to allocators not matching to Libraries not able to load. Since MFC and ATL would not even think to compile with out msvcrt Headers and lib the issue had to be resolved. The only way I managed to solve it all is by directly linking msvcrt GCC style into STLPort and into every module there of. Now that would make some conflicts with OCX's like IE6 that can only run with native msvcrt.dll, so I also had to change it's name. One of the thing I would like to eventually do is Make a static msvcrt library using same source code but having different make files to be used in such situations where it has to be directly linked. Tomorrow I will start synchronization with wine current tree. Once I have it synced (2 days max). I will need someone to help me and guide me on how to send it all in. Dimi, will that be you? So I guess the scores are: Wine vs Windows 1:1 World vs Microsoft 3:10 (we are making progress, wait for the last round) Boaz vs GCC 7:4 Good vs Evil (I better not say) Happy new Year to all Free Life Boaz

5 16

Re: netapi32: implement NetServerEnum and NetShareEnum
by Juan Lang 04 Jan '04

04 Jan '04

--- Dan Kegel <dank(a)gmane.kegel.com> wrote: > My goodness. I didn't know that document existed. > Thanks for > the link! Is there a complete list anywhere of > Win32 APIs > that have been documented by opengroup.org? My pleasure. Don't know of one, but check out the references section of Chris Hertel's (beyond sufficient praise) Implementing CIFS book, http://ubiqx.org/cifs/References.html That's where I found the link. --Juan __________________________________ Do you Yahoo!? Find out what made the Top Yahoo! Searches of 2003 http://search.yahoo.com/top2003

1 0

Re: commctrl.c
by Dmitry Timoshkov 04 Jan '04

04 Jan '04

"Ge van Geldorp" <ge(a)gse.nl> wrote: > Changelog: > Don't destroy heap during unload, as other DLLs which haven't unloaded > yet may still depend on it (DPA* callers) The patch is wrong. A more correct way to fix this is to simply use process heap in DPA (and MRU) APIs. Perhaps even go further and completely remove any use of the private comctl32 heap. -- Dmitry.

1 0

Jump to page:

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