wine-devel November 2002

wine-devel@winehq.org

152 participants
501 discussions

winewrapper
by Dimitrie O. Paun 22 Nov '02

22 Nov '02

Folks, Another problem developing Winelibs app while using your Wine tree. Say you have the following: -- a Winelib app you're working on -- a Wine tree you're working on -- you compile wine out-of-tree Now, say you build your myapp.exe.so OK, and you now want to create a symlink myapp -> winewrapper so you can start your Winelib app. Problem is that winewrapper resides in the source tree, and there is no way for it to figure out where the build tree is, and it needs that. Possible solution: -- have winewrapper somehow in the Wine build tree. One way to do that is to rename winewrapper to winewrapper.in, and generate winewrapper at build time -- link to the winewrapper in the build tree -- modify winewrapper slightly so that it looks where is resides, and if it's in the wine tree, is should try to use that to run the app. Alexandre, what do you say? -- Dimi.

4 13

Re: wine/tools wineinstall
by Dustin Navea 22 Nov '02

22 Nov '02

On Thu, 2002-11-21 at 17:46, Alexandre Julliard wrote: > ChangeSet ID: 6362 > CVSROOT: /opt/cvs-commit > Module name: wine > Changes by: julliard(a)wine.codeweavers.com 2002/11/21 17:46:06 > > Modified files: > tools : wineinstall > > Log message: > Matthew Davison <m.davison(a)virgin.net> > Remove obsolete --enable-opengl. > > Patch: http://cvs.winehq.com/patch.py?id=6362 > > Old revision New revision Changes Path > 1.47 1.48 +1 -1 wine/tools/wineinstall > > > I'm not totally sure that this should be done as my wine install comes with opengl disabled due to relying on libpthread for thread safety. If we remove the --enable-opengl from wineinstall FLC's will not know how to enable it... -Dustin

2 1

__int64
by Dimitrie O. Paun 22 Nov '02

22 Nov '02

Hmm, Another header problem. When compiling Putty with Wine's headers, I get this errors: In file included from /home/dimi/dev/wine/wine.src/include/msvcrt/wchar.h:12, from wcwidth.c:9: /home/dimi/dev/wine/wine.src/include/msvcrt/io.h:42: parse error before "__int64" /home/dimi/dev/wine/wine.src/include/msvcrt/io.h:42: warning: no semicolon at end of struct or union /home/dimi/dev/wine/wine.src/include/msvcrt/io.h:44: parse error before '}' token /home/dimi/dev/wine/wine.src/include/msvcrt/io.h:60: parse error before "__int64" ... Reason is that __int64 is not defined. Now, this happens when I compile a file that has only one include: #include <wchar.h> As a quick hack, I've added this: typedef long long __int64; to include/msvcrt/sys/types.h, but it doesn't look like the right fix. We define __int64 in here: include/basetsd.h:#define __int64 long long but why a define and not a typedef? Should we include this file from one of the msvcrt header files? I really don't like doing that, but than again, I don't know much about the organization of our headers, or most importantly, the way MS does it... -- Dimi.

4 7

PuTTY update
by Dimitrie O. Paun 21 Nov '02

21 Nov '02

Folks, Here's a quick status update on PuTTY as a Winelib app: 1. It compiles, links, and runs perfectly (Yay!) 2. I've talked to the PuTTY folks, and they agreed to add Winelib as one of their targets in their build process (provided I do the patch :)) 3. I've modified they Makefile-generation Perl scrip to do just that. What is missing: 1. The winspool issue I've sent earlier is bugging me. They link against -lwinspool, we require -lwinspool.drv This is very awkward to implement, and my patch would become a lot more intrusive (and maybe unacceptable). We need to fix this on our end, so we're compatible. 2. The winewrapper thing I've just sent out. I can't send them a bunch (they generate like 7 apps) of silly wrapper scrips, that'd be ridiculous. Help in resolving these issues would be greatly appreciated. I'd like to send them the patch sooner rather than later, so that (1) they don't change their mind, and (2) I don't forget what I was doing! :) -- Dimi.

2 2

Seperating winelibs from main wine ( was "Winelib support" )
by Mark Hannessen 21 Nov '02

21 Nov '02

Mmmm.. Doesn't sound like a basic windows app. I do not know any windows program that uses putty and there are plenty linux/unix alternatives. but it might be usefull to some people. ( i don't know anyone ) perhaps it is time to seperate all the winelib progs from the main wine package and create a winelib package. just how knows what people in the future might write. paint / control panel / media player / calculator / etc... comments please Mark Hannessen On Thursday 21 November 2002 10:50, wine-devel-request(a)winehq.com wrote: > Hi folks, > > I'm one of the Wine (http://www.winehq.org) developers, > and I just managed to build Putty under Winelib. That > is, Putty now runs as a native Linux application. > > The interesting part is that I've managed to do so with > virtually no changes to the source code, just a few > changes to the makefile.cyg file. > > Now, my question to you: are you interested in supporting > Putty under Wine, as a Winelib app? If so, I can clean up > my changes, and send you a patch for the build system to > incorporate in your tree.

7 13

[Fwd: Re: Wine developers want Pegasus Mail as a 'Gold' app]
by Rick Romero 21 Nov '02

21 Nov '02

I contacted David Harris, author of Pegasus Mail, and here's what he had to say. I am totally lost when it comes to the windowing stuff, I'm not sure what's X and what's Windows. Hopefully that can help a little.. I know the patches thread was really self-explanatory, but was centered on the app being iconified. I don't know that this is really any different, but it just seems more of a 'hiding the taskbar' and not iconifying the app. Or am I just stubborn/thick-headed? (well, I am :) The "Setup Wizard" was something I thought would be good to have, but at this point, I think David would have to remove the actual file open code from Pegasus for it to work. HTH. Rick -----Forwarded Message----- From: David Harris <David.Harris(a)pmail.gen.nz> To: Rick Romero <rick(a)valeoinc.com> Subject: Re: Wine developers want Pegasus Mail as a 'Gold' app Date: 22 Nov 2002 10:52:12 +1300 On 21 Nov 2002 at 11:59, Rick Romero wrote: > I apologize for the direct email, I had hoped that a Win-PM list posting > would be sufficient, but it unfortunately hasn't been. Alas, I don't read any of the public lists any more - with more than 300 messages a day to deal with just on the local accounts, I simply don't have time. > But let me get right down the the issues. I was hoping you could give > me some insight into the workings of Pegasus Mail so that the Wine guys > could easily implement any Windows API's that you might be using, that > are missing from Wine. Please consider my mailbox open at any time of the day for this - both yourself and any Wine developer who would like to contact me directly. Given that I simply don't have the resources to produce my own Linux version of Pegasus Mail at this stage, Wine assumes considerable importance for me, so any collaboration offers clear mutual benefits. > The first, critical issue, has to do with hiding the taskbar entry. > The option: "Hide the Pegasus Mail taskbar entry when minimized" which > is on by default, causes Wine to not refresh the window after > minimizing, or changing virtual desktops. A one-line fix for Wine DOES > exist, (Essentially, the flag WS_VISIBLE is not checked within Wine) but > I was hoping you could give us a little more info on what flag you may > set on that checkbox, or if it's just a flag at all, or a quick couple > lines of code.. It's not as clean or tidy as a couple of lines of code - there are some messages involved, but overall it's pretty simple. When Pegasus Mail gets a WM_SIZE message with wParam set to SIZE_MINIMIZED, it simply calls ShowWindow (hWndFrame, SW_HIDE); where "hWndFrame" is the main WinPMail frame window. There's a little other cruft in there as well, but nothing that would affect this. Under Windows, the effect of this is to remove the application from the taskbar. That's really all there is to it. The preferences checkbox merely sets a preference field which is queried later when the application is actually minimized - it has no other immediate function when it is checked. > The second issue is just for user convienance. We've found that Pmail > checks for a physical winsock.dll (wsock32.dll for Wine), and if that > exists, it enables TCP/IP. What still doesn't occur though, is the > Internet Setup Wizard. A fresh install, with wsock32.dll existing, (We > assume) should start the Wizard upon startup. That doesn't happen, > Pegasus works just fine, but doesn't start the wizard for the new user. > Are there any other checks you make to start that wizard up? Looking through the code, it appears to me that the following conditions need to be true before the Internet Setup Wizard will run: 1: It must be the first time the program has ever run for this user (i.e, there needs to have been no PMAIL.INI file present in the mailbox when the program started). 2: The commandline -Z (flags) switch must not have bit 0 set (i.e, it cannot have "1" as one of its bit members) - this disables TCP/IP altogether. 3: The User's POP3 server, POP3 username and POP3 password must all be zero-length (i.e, not yet defined) internally. 4: The bit member 0x20000 must not be set in the -Z (flags) commandline switch (this bit simply disables the setup wizard). 5: The program must be able to locate WSOCK32.DLL in any of the usual places where LoadLibrary would look (the Windows System directory, the Windows directory, the path, the current directory). Note that the check in step 5 is unintentionally quite extensive - the file not only has to be present, but Pegasus Mail actually has to be able to open it for reading (this is because I have a general-purpose file existence checking routine that attempts to make sure that the file not only exists, but can be opened, and I use that as part of the process of searching for a DLL). Aside from (all) that, I can't see anything else in there that might cause the setup wizard not to run. -- If there were some reliable way that I could determine that I was running under Wine, I would be *happy* to add code to the program that gave it specific behaviours in that environment - all you need to do is tell me what behaviours you need modified, and how I can detect Wine. Cheers! -- David -- ------------------ David Harris -+- Pegasus Mail ---------------------- Box 5451, Dunedin, New Zealand | e-mail: David.Harris(a)pmail.gen.nz Phone: +64 3 453-6880 | Fax: +64 3 453-6612 Real newspaper headlines from U.S. papers: MAN HELD OVER GIANT L.A. BRUSH FIRE -- -- Rick Romero IT Manager Valeo, Inc. ph: 262.695.4841 Sussex, WI. fax: 262.695.4850 Rick(a)valeoinc.com

1 0

Minor AIM bug
by Dustin Navea 21 Nov '02

21 Nov '02

Hey now that I got AIM running, (have to copy from a windows install and force wine to use that winver) I noticed 2 small bugs.. Both are related to comctl32 AFAICT... 1) When going to sign on, the controls think that the left mouse button is pushed always, and so when you move the mouse over the screen name it selects it, that is more of a feature IMO, as it makes it easier to switch screen names 2) When resizing the chat windows, there is a significant amount of lag moving the controls, like you resize the window, but the controls all move a lot slower than the window does, hard to describe but if anyone wants a screenshot I can post one somewhere... -Dustin

1 0

PostMessage and NULL HWND's
by steve.lustbader＠philips.com 21 Nov '02

21 Nov '02

PostMessage fails if you pass in NULL as the HWND argument. According to the MSDN, a NULL HWND means "The function behaves like a call to PostThreadMessage with the dwThreadId parameter set to the identifier of the current thread." Currently, PostMessage tries to get the thread id of the hwnd, which of course fails since it's NULL in this case, and of course the error is Invalid Window Handle. It seems like a simple fix is a test if hwnd is NULL and calling PostThreadMessage with the right thread ID, but I don't know how to get the current thread's ID. Any ideas/suggestions? -Steve

2 1

RE: Adding -lc when linking?
by Patrik Stridvall 21 Nov '02

21 Nov '02

> Gerald Pfeifer <pfeifer(a)dbai.tuwien.ac.at> writes: > > > How should this be solved (in a portable way)? > > Adding -lc seems the right way. In fact I committed that fix last > night ;-) Yes I noticed. :-) However, it doesn't seem to be the 100% correct fix. DLLs using pthreads like the ones depending on OpenGL needs to link with -lc_r instead of -lc on FreeBSD. ---8<--- gcc -shared -Wl,-Bsymbolic,-z,defs d3d8.spec.o basetexture.o cubetexture.o d3d8_main.o device.o directx.o indexbuffer.o resource.o surface.o swapchain.o texture.o vertexbuffer.o volume.o volumetexture.o d3d8.dll.dbg.o -o d3d8.dll.so -L../../dlls -L../../library -lwine -L../../ole -lwine_uuid -L/usr/X11R6/lib -lSM -lICE -lXxf86dga -lXxf86vm -lXv -lXext -lX11 -lGL -lGLU -lm -lc /usr/lib/libgcc.a(_eh.o): In function `__empty': _eh.o(.text+0x9e): undefined reference to `pthread_setspecific' /usr/lib/libgcc.a(_eh.o): In function `__get_eh_info': _eh.o(.text+0xec): undefined reference to `pthread_key_create' _eh.o(.text+0x1b9): undefined reference to `pthread_getspecific' _eh.o(.text+0x1d8): undefined reference to `pthread_setspecific' /usr/lib/libgcc.a(frame.o)(.text+0x44b): undefined reference to `pthread_mutex_lock' /usr/lib/libgcc.a(frame.o)(.text+0x492): undefined reference to `pthread_mutex_unlock' /usr/lib/libgcc.a(frame.o): In function `__register_frame_info': frame.o(.text+0x8d9): undefined reference to `pthread_mutex_lock' frame.o(.text+0x900): undefined reference to `pthread_mutex_unlock' /usr/lib/libgcc.a(frame.o): In function `__register_frame_info_table': frame.o(.text+0x969): undefined reference to `pthread_mutex_lock' frame.o(.text+0x990): undefined reference to `pthread_mutex_unlock' /usr/lib/libgcc.a(frame.o): In function `__deregister_frame_info': frame.o(.text+0x9dc): undefined reference to `pthread_mutex_lock' frame.o(.text+0xa27): undefined reference to `pthread_mutex_unlock' frame.o(.text+0xa4d): undefined reference to `pthread_mutex_unlock' *** Error code 1

3 2

Re: COM Enhancement patch
by John K. Hohm 21 Nov '02

21 Nov '02

> Well, I was hoping some of the COM experts would comment on that. If > I understand it right you are avoiding writing some thunking routines > for older interfaces, at the cost of an extra pointer access in every > function. I'm not convinced it's a good trade-off, but I'd like to > hear other opinions. I might not exactly be an expert, but I don't like the extra work being done everywhere with the extra pointer. If writing the thunk functions is really so cumbersome, perhaps a macro for generating the thunk functions is in order.

3 2

← Newer
1
...
13
14
15
16
17
18
19
...
51
Older →

Jump to page:

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 November 2002