RE: wine/ tools/wineinstall loader/Makefile.in loa ...
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Alexandre Julliard Sent: 12 November 2003 03:28 To: [EMAIL PROTECTED] Subject: wine/ tools/wineinstall loader/Makefile.in loa ... Log message: Added a wine-glibc binary that detects the glibc threading in use and execs the corresponding wine binary. Removed the --with-nptl configure option. Cool! Well done. Rob
(no subject)
_ Charla con tus amigos en línea mediante MSN Messenger: http://messenger.microsoft.com/es
Re: asm help
BOOL WINAPI
_InitCommonControlsEx(WINGS_INITCOMMONCONTROLSEX* lpInitCtrls)
{
if(!dwLPA_InitCommonControlsEx)
{
return FALSE;
} else {
return dwLPA_InitCommonControlsEx(lpInitCtrls);
}
}
The jmp is an optimization step, where the new function is called with
the same parameters as the old one.
I do agree with you about not using direct ASM-C conversions like this.
--
Shachar Shemesh
Open Source integration consultant
Home page resume - http://www.shemesh.biz/
Ok, i understand, i got Access violation in
dwLPA_InitCommonControlsEx(lpInitCtrls);
Re: Netmeeting under Wine
This is an off topic question. You may ask it to the [EMAIL PROTECTED] list. Le mer 12/11/2003 à 10:06, David Martinez Prado a écrit : Hi! it's my firts time runing wine. I want to execute Netmeeting under Wine but i can. Can anybody help me please? Regards, DAVID _ Localiza y ponte en contacto con tus antiguos compañeros de clase en MSN Compañeros. http://mipasado.msn.es/
Re: Wintab32 - Tablet support
Hi, This is more a question for the developers Should have posted to wine-devel then :) Doing so now. A couple of months ago there was a patch from Aric Stewart that added support for graphics tablets in wine. However I have not heard anything about it since. Is anybody still working on this? Graphics tablet support is the only thing stopping us from using Photoshop under Linux at the present time. Moving all our graphics artists off dual booting windows machines would be extremely benificial! I tried the original patch but found it affected the stability of wine... I noticed that in the original patch a lot of functions were called from DllMain that shouldn't be called from there. Did the backtrace include wintab32.DllMain? The initialisation should probably be moved to either each function with a line like if (!initialised) Initialise(); Alexandre, how come this patch hasn't been included in Wine yet? Was it the problem stated here or something else? Daire Rob
how to search several PE files to see if any of them import a particular function?
Is there a way to do this? I want to use it on various PE files (DLLs, EXEs etc) to see if any of them import some of the functions for which I dont yet have a prototype :)
Re: how to search several PE files to see if any of them import a particular function?
Le mer 12/11/2003 à 08:00, Jonathan Wilson a écrit : Is there a way to do this? I want to use it on various PE files (DLLs, EXEs etc) to see if any of them import some of the functions for which I dont yet have a prototype :) winedump can tell you which APIs a file imports and exports. Script around it. Vincent
listview advice needed.
Hi,
Agent 2.0 beta crashes on listview related code, and requires native
comctl32 to run.
Here is a cut from a +relay,+message,+listview trace:
| trace:message:SPY_ExitMessage (0x1004b) L{SysListView32} message [1004]
LVM_GETITEMCOUNT returned
| 0009:Ret user32.SendMessageA() retval= ret=005cad80
At this point the listview is newly created, headers column inserted
etc. No items yet.
| 0009:Call user32.SendMessageA(0001004b,1007,,406cf6f8) ret=005cc1b4
| trace:message:SPY_EnterMessage (0x1004b) L{SysListView32} message [1007]
LVM_INSERTITEMA sent from self wp= lp=406cf6f8
| trace:message:SPY_DumpMem LVITEM [] 0003
| trace:message:SPY_DumpMem LVITEM [0010] 42103914 0018
| trace:message:SPY_DumpMem LVITEM [0020] 61737365 005cc11f 406cf770 006b30b6
| trace:message:SPY_DumpMem LVITEM [0030]
The program inserts the first item. Valid fields are Text and Image.
| trace:listview:LISTVIEW_WindowProc (uMsg=1007 wParam=0 lParam=406cf6f8)
| trace:listview:LISTVIEW_InsertItemT (lpLVItem={iItem=0, iSubItem=0,
pszText=application/octet-stream, cchTextMax=24, iImage=-1}, isW=0)
| trace:listview:LISTVIEW_InsertItemT inserting at 0, sorted=1, count=0, iItem=0
| trace:listview:LISTVIEW_ShiftIndices Shifting 0u, 1 steps
| trace:listview:set_main_item ()
| trace:listview:set_main_item oldState=0, newState=0
| trace:listview:set_main_item uChanged=0x3
| trace:listview:notify_listview (code=-102, plvnm=iItem=0, iSubItem=0, uNewState=0x0,
uOldState=0x0, uChanged=0x0, ptAction=(0, 0), lParam=0 )
| trace:listview:notify_hdr (code=-102)
| trace:message:SPY_EnterMessage (0x10049) L{wxWindowClass} message [004e]
WM_NOTIFY sent from self wp=1e68 lp=406cf148
| trace:message:SPY_DumpStructure NMHDR hwndFrom=0x1004b idFrom=0x1e68
code=LVN_INSERTITEM0xff9a, extra=0x20
| trace:message:SPY_DumpMem NM extra []
| trace:message:SPY_DumpMem NM extra [0010]
Still inside the LVM_ISERTITEMA message a WM_NOTIFY is sent. The
programs message handler queries number of items:
| 0009:Call user32.SendMessageA(0001004b,1004,,) ret=005cad80
| trace:message:SPY_EnterMessage (0x1004b) L{SysListView32} message
[1004] LVM_GETITEMCOUNT sent from self wp= lp=
| trace:listview:LISTVIEW_WindowProc (uMsg=1004 wParam=0 lParam=0)
| trace:message:SPY_ExitMessage (0x1004b) L{SysListView32} message
[1004] LVM_GETITEMCOUNT returned 0001
| 0009:Ret user32.SendMessageA() retval=0001 ret=005cad80
there is one item.
| 0009:Call user32.SendMessageA(0001004b,1005,,406cebe0) ret=005ca4cb
| trace:message:SPY_EnterMessage (0x1004b) L{SysListView32} message
[1005] LVM_GETITEMA sent from self wp= lp=406cebe0
| trace:message:SPY_DumpMem LVITEM [] 0004 42100a50 406cf148
| trace:message:SPY_DumpMem LVITEM [0010] 406cf154 406ced10 407c1c09 005cad80
| trace:message:SPY_DumpMem LVITEM [0020] 0001004b 1004 406ced10 005ccb9a
| trace:message:SPY_DumpMem LVITEM [0030] 0001004b
and request that lParam of that item. Note that iItem is zero but
iSubItem is 0x42100a50, like all other fields it is filled with rubbish.
(confirmed with dissassembly that only the mask and iItem fields are
filled in)
| trace:listview:LISTVIEW_WindowProc (uMsg=1005 wParam=0 lParam=406cebe0)
| trace:listview:LISTVIEW_GetItemT (lpLVItem={iItem=0, iSubItem=1108347472,
lParam=1004b}, isW=0)
| trace:message:SPY_ExitMessage (0x1004b) L{SysListView32} message
[1005] LVM_GETITEMA returned 0001
| trace:message:SPY_DumpMem LVITEM [] 0004 42100a50 406cf148
| trace:message:SPY_DumpMem LVITEM [0010] 406cf154 406ced10 407c1c09 005cad80
| trace:message:SPY_DumpMem LVITEM [0020] 0001004b 1004 406ced10 005ccb9a
| trace:message:SPY_DumpMem LVITEM [0030] 0001004b
At return, the requested value of lParam is still rubbish, which is
causing a crash somewhat later.
| trace:message:SPY_ExitMessage (0x10049) L{wxWindowClass} message [004e]
WM_NOTIFY returned
| trace:message:SPY_DumpStructure NMHDR hwndFrom=0x1004b idFrom=0x1e68
code=LVN_INSERTITEM0xff9a, extra=0x20
| trace:message:SPY_DumpMem NM extra []
| trace:message:SPY_DumpMem NM extra [0010]
| 0009:Ret user32.SendMessageW() retval= ret=40b49738
If I hack LISTVIEW_GetItemT() with a hack like:
|
| if (lpSubItem)
| {
| SUBITEM_INFO *lpSubItem = LISTVIEW_GetSubItemPtr(hdpaSubItems,
lpLVItem-iSubItem);
| pItemHdr = lpSubItem ? lpSubItem-hdr : callbackHdr;
|+ if(!lpSubItem) lpLVItem-iSubItem = 0;
| }
the program proceeds (crashes much much later) . But this is probably
not the correct way to check that an invalid subitem has been passed
(for
Re: fcvt
flyker == flyker [EMAIL PROTECTED] writes: flyker Function fcvt incorrect. example: int dec, sign; printf(%s\n, flyker fcvt(1.12, 2, dec, sign)); flyker result: 1.12e+00 flyker but need: 112 In what way does that behaviour hurt you(r application)? Bye -- Uwe Bonnes[EMAIL PROTECTED] Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt - Tel. 06151 162516 Fax. 06151 164321 --
Re: Make failed, something about D3D8 D3Dcore...
Hi Raphael, glx.h is mesa 3.2 glext.h is SGI 1.2.1 Hmm... It seems I'm using very old headers... I'm using the newest NVIDIA driver. I will try to find some newer headers. Greetings, --Thomas _ My worst enemy gave me a copy of Windows...
Re: fcvt
Uwe Bonnes wrote: flyker == flyker [EMAIL PROTECTED] writes: flyker Function fcvt incorrect. example: int dec, sign; printf(%s\n, flyker fcvt(1.12, 2, dec, sign)); flyker result: 1.12e+00 flyker but need: 112 In what way does that behaviour hurt you(r application)? Bye Link with -lmsvcrt option
Re: Make failed, something about D3D8 D3Dcore...
Le mer 12/11/2003 à 09:19, Thomas Brix Larsen a écrit : Hi Raphael, glx.h is mesa 3.2 glext.h is SGI 1.2.1 Hmm... It seems I'm using very old headers... I'm using the newest NVIDIA driver. When you install the NVIDIA driver, there's an option to install development headers at the same time. Vincent
Re: Make failed, something about D3D8 D3Dcore...
ons, 2003-11-12 kl. 15:30 skrev Vincent Béron: Le mer 12/11/2003 à 09:19, Thomas Brix Larsen a écrit : Hi Raphael, glx.h is mesa 3.2 glext.h is SGI 1.2.1 Hmm... It seems I'm using very old headers... I'm using the newest NVIDIA driver. When you install the NVIDIA driver, there's an option to install development headers at the same time. Vincent No, not with my Lunar Linux (lunar-linux.org) it extracts and compiles the driver, not using NVIDIAs system. I should probaly contact the Lunar development team, and tell them about the missing headers. But I've found the headers in /usr/share/doc/NVIDIA_GLX-1.0/ And it is compiling now. Greetings, --Thomas _ My worst enemy gave me a copy of Windows...
Re: suggestion: Get native uxtheme and native common controlls working on WINE and ReactOS
Hello Kevin, --- Kevin Koltzau [EMAIL PROTECTED] wrote: It is not possible to get native uxtheme from an XP installation working under wine. However I am currently working on a uxtheme.dll implementation for wine that will support loading native WinXP themes, which when finished I'm sure could be used by ROS. We have a uxtheme.dll that is being developed in ReactOS cvs also that supports loading native WinXP themes and we have a theme dumping program. You are welcome to look at the code and discuss the work with our developer KJK:Hyperion. I cannot help with sharing this code with ReactOS and Winehq as this developer wishes to remain under a Pseudonym. I would much rather get a working implementation going in Winehq and use your uxtheme. Thanks Steven __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree
Re: PATCH: handle non aligned mmaps of sections
--- Alexandre Julliard [EMAIL PROTECTED] wrote: I don't think it makes sense to use the normal mapping code for such files, we should really have a separate loader for the NT kernel stuff (which can of course re-use some lower level functions of the current loader). Do we also create a stub implementation of ntoskrnl for the driver support? SecDev.sys is reported to load under ReactOS and I would like to help get it to load under WINE. Thanks Steven __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree
Re: PATCH: handle non aligned mmaps of sections
Steven == Steven Edwards [EMAIL PROTECTED] writes: Steven --- Alexandre Julliard [EMAIL PROTECTED] wrote: I don't think it makes sense to use the normal mapping code for such files, we should really have a separate loader for the NT kernel stuff (which can of course re-use some lower level functions of the current loader). Steven Do we also create a stub implementation of ntoskrnl for the Steven driver support? SecDev.sys is reported to load under ReactOS and Steven I would like to help get it to load under WINE. More question: How does a user program call into SecDev.sys? Via DeviceIOControl()? I looked at some .sys files, and they don't export anything. How is DeviceIOControl reached? Bye -- Uwe Bonnes[EMAIL PROTECTED] Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt - Tel. 06151 162516 Fax. 06151 164321 --
Native Dll x Built-in Dll - why everything doesn't work with native dlls
Hello all!! My name is Leonardo, and i'm working in a project that will migrate thousands of windows NT4 machines to Linux. In this project we will do some wine impplementations, if needed. The apps that we are testing is some VB6/5 apps and DataBase client apps. None of the apps executed correctly. So we will impplement wine. I need to know why when we use Native DLL these apps doesn't work. How does wine open the native dll files? Where are the doc about that? thanks. -- _ ,^. _ Leonardo Luiz Padovani da Mata ,'/ -' '- \`.Ciencia da Computacao - UFMG / | \ / | \ [EMAIL PROTECTED] | | | | | | ICQ:61226375 | \_,' `._/ | | | \ / ... `. .'May the force be with you, always `--._.--' Nerd Pride... eu tenho. Voce tem? Alianca Rebelde
Re: Native Dll x Built-in Dll - why everything doesn't work with native dlls
Leonardo == Leonardo Luiz Padovani da Mata [EMAIL PROTECTED] writes: Leonardo Hello all!! My name is Leonardo, and i'm working in a project Leonardo that will migrate thousands of windows NT4 machines to Linux. Leonardo In this project we will do some wine impplementations, if Leonardo needed. Leonardo The apps that we are testing is some VB6/5 apps and DataBase Leonardo client apps. None of the apps executed correctly. So we will Leonardo impplement wine. Leonardo I need to know why when we use Native DLL these apps doesn't Leonardo work. How does wine open the native dll files? Where are the Leonardo doc about that? High level DLLs (like the visual basic dlls) call into low level dlls, like kernel32.dll. If there are bugs in the wine implementation of these dlls, errors will happen, even when a native high level dll is uses. With VB6/5, most errors happen around Ole/Com, as wine still needs a long way in that area. Running with the appropriate native DLLs may circumvent the problem. For migrating, using the native dlls is not a (legal) option however. Native dlls are opened by loading the dll, when the PE header request the dll, just like windows does. Learn the basics from reading low level windows books, and then understand what wine does in what way by reading the wine source and asking good questions on the list. Asking Where are the doc about that? is normally not considered a good question, as you don't show what effort you did yourself to solve that problem. Bye -- Uwe Bonnes[EMAIL PROTECTED] Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt - Tel. 06151 162516 Fax. 06151 164321 --
Re: PATCH: handle non aligned mmaps of sections
On Wed, Nov 12, 2003 at 05:59:31PM +0100, Uwe Bonnes wrote: Steven == Steven Edwards [EMAIL PROTECTED] writes: Steven --- Alexandre Julliard [EMAIL PROTECTED] wrote: I don't think it makes sense to use the normal mapping code for such files, we should really have a separate loader for the NT kernel stuff (which can of course re-use some lower level functions of the current loader). Steven Do we also create a stub implementation of ntoskrnl for the Steven driver support? SecDev.sys is reported to load under ReactOS and Steven I would like to help get it to load under WINE. More question: How does a user program call into SecDev.sys? Via DeviceIOControl()? I looked at some .sys files, and they don't export anything. How is DeviceIOControl reached? On load, the loader calls start(DRIVER_OPEN *do, PUNICODE_STRING *name); The DRIVER_OPEN struct is filled out by the called function, including lots of function pointers. One of them is called from DeviceIoControl(). Ciao, Marcus
Re: Zombies (was : Conformance tests...)
From: Sylvain Petreolle [EMAIL PROTECTED] To: Paul Millar [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: Sami Aario [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Saturday, November 08, 2003 3:17 PM Subject: Zombies (was : Conformance tests...) Paul, Sami, (and perhaps others), could you run this script and send me the results ? Results attached. ./controls ./controls : 0 zombies ./dlls ./dlls : 0 zombies ./documentation ./documentation : 0 zombies ./files ./files : 0 zombies ./graphics ./graphics : 0 zombies ./include ./include : 0 zombies ./libs ./libs : 0 zombies ./loader ./loader : 0 zombies ./memory ./memory : 0 zombies ./misc ./misc : 0 zombies ./miscemu ./miscemu : 0 zombies ./msdos ./msdos : 0 zombies ./objects ./objects : 0 zombies ./programs ./programs : 0 zombies ./scheduler ./scheduler : 0 zombies ./server ./server : 0 zombies ./tools ./tools : 0 zombies ./win32 ./win32 : 0 zombies ./windows ./windows : 0 zombies
Re: Zombies (was : Conformance tests...)
From: Paul Millar [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Sami Aario [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 12:56 PM Subject: Re: Zombies (was : Conformance tests...) Looks suspiciously like the 2.6.0-test8 kernel is to blame. To confirm this, I rebooted quisquiliae using a 2.4.20-kernel. Guess what? No zombies. My kernel is the Debian sarge default kernel, 2.2.20. I get zero zombies.
Re: Zombies (was : Conformance tests...)
My kernel is the Debian sarge default kernel, 2.2.20. I get zero zombies. Oops, should be Debian woody.
wine 20031016 installed from source: no winebuild
I had earliler experienced some problems with my Mandrake 9.1 installation of wine, when trying to use the wine libraries. I have now done the following: installed wine-20031016-mdk.i586.rpm My binary programs seemed to run fine, (except for a font problem described in a separate post). Since the development tools, winemaker etc were present, I decided to try to build my application. This proceeded well beyond where I could get to earlier (wrc failed), but ended as follows: --- [EMAIL PROTECTED] MyWin]$ make c++ -c -I. -I/usr/local/include/python2.3 -I/usr/include/wine/windows -g -O2 -fpermissive -fno-for-scope-D_REENTRANT -o MyWin.o MyWin.cpp In file included from /usr/local/include/python2.3/Python.h:8, from MyWin.cpp:4: /usr/local/include/python2.3/pyconfig.h:847:1: warning: _POSIX_C_SOURCE redefined In file included from /usr/include/ctype.h:27, from /usr/include/wine/windows/winnt.h:27, from /usr/include/wine/windows/windef.h:203, from /usr/include/wine/windows/windows.h:38, from MyWin.cpp:2: /usr/include/features.h:131:1: warning: this is the location of the previous definition LD_LIBRARY_PATH=/usr/lib:$LD_LIBRARY_PATH /usr/bin/winebuild -fPIC -o mywin.dll.spec.c --spec mywin.dll.spec MyWin.res MyWin.o -L/usr/lib -L/usr/lib/wine -ladvapi32 -lcomdlg32 -lgdi32 -lkernel32 -lodbc32 -lole32 -loleaut32 -lshell32 -luser32 -lwinspool mywin.dll.spec:1: could not open .def file for advapi32 make: *** [mywin.dll.spec.c] Error 1 --- So I assumed that the missing library specs were a part of the wine-devel package, which was not installed. I could not locate any wine-devel rpms for version 20031016 and Mandrake. So, I dowmloaded the 20031016 source tarball and installed it with the tools/install. This seemd to work well, except that at the end of the , the following complaint appears: - mkdir -m 755 -p -- /usr/local/share/aclocal /usr//bin/install -c -m 644 ./aclocal.m4 /usr/local/share/aclocal/wine.m4 /sbin/ldconfig * * The installed Wine libraries will not be found! You can either: Add the line '/usr/local/lib' to /etc/ld.so.conf and run /sbin/ldconfig export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib * * Found existing /home/parz/.wine/config, do you want to overwrite this existing Wine configuration file? (yes/no) no Installation complete for now. Good luck (this is still alpha software). If you have problems with WINE, please read the documentation first, as many kinds of potential problems are explained there. [EMAIL PROTECTED] wine-20031016]$ --- However, inspecting /etc/ld.so.conf shows that the complained-about path *is* actually present: [EMAIL PROTECTED] MyWin]$ cat /etc/ld.so.conf /usr/X11R6/lib /usr/lib/qt3/lib /usr/local/lib [EMAIL PROTECTED] MyWin]$ So, I tried to build my winelib dll anyways: [EMAIL PROTECTED] Emsview]$ echo $LD_LIBRARY_PATH [EMAIL PROTECTED] Emsview]$ /sbin/ldconfig /sbin/ldconfig: Can't create temporary cache file /etc/ld.so.cache~: Permission denied [EMAIL PROTECTED] Emsview]$ su Password: [EMAIL PROTECTED] Emsview]# ldconfig [EMAIL PROTECTED] Emsview]# exit exit [EMAIL PROTECTED] Emsview]$ cd MyWin [EMAIL PROTECTED] MyWin]$ make LD_LIBRARY_PATH=/usr/lib:$LD_LIBRARY_PATH /usr/bin/winebuild -fPIC -o mywin.dll.spec.c --spec mywin.dll.spec MyWin.res MyWin.o -L/usr/lib -L/usr/lib/wine -ladvapi32 -lcomdlg32 -lgdi32 -lkernel32 -lodbc32 -lole32 -loleaut32 -lshell32 -luser32 -lwinspool /bin/sh: line 1: /usr/bin/winebuild: No such file or directory make: *** [mywin.dll.spec.c] Error 127 [EMAIL PROTECTED] MyWin]$ -- So, with the homebuilt wine-20031016, it seems that the development tools are not installed, and I am stuck. How do I get past these problems? -- Parzival Herzog
Re: wrc doesn't seem to accept -r option,even though it is automatically generated by make file
On Tuesday 11 November 2003 01:22 pm, Parzival Herzog wrote: On November 11, 2003 11:39, Ivan Leo Murray-Smith wrote: I don't know how to solve your problem, but it would be a good idea if you just installed the latest CVS version. whine I' just too inexperienced and too isolated to use CVS right now: an 800 page manual, configuring, using SSH, it threatens to take up the rest of the year just to get started, and I'm off to another mailing list when the inevitable why doesn't it work problems occur. I've also discovered that with non-rpm source distributions, there is a make install, but so far, nothing I have seen has a make uninstall that does anything, and that concerns me, when I see 70 MB of stuff flying off to 400 different places. (Maybe wine is not like that, but I just built the insight gdb, and I thought it would use my existing gdb, but it built and installed a new one, installed its own tk, (gee, what about the tk that is a part of Python) and has no way to uninstall. I'm at a place where I'm wrestling with how does the PATH get set, how do you build a static library, how do you build a shared library, how does the loader find a shared library. Wrestling with ten thousand-line makefiles is sheer insanity from my perspective. I just hope that I can get my little program to compile and run with winelib, because if it that works, I won't have to use Windows in my day-to-day work. /whine There, there, no need to whine /, it's going to be OK! Try following the instructions on this page: http://www.winehq.com/site/cvs Just do what it says, step-by-step. You don't need ssh for this, just cvs. That page even tells you how to keep your wine up-to-date via cvs once you get it. And, wine just happens to support make uninstall. Sounds to me like you are letting yourself get overwhelmed by the scope of what you do not know. For example, very few people here (although there are probably one or two) would actually know the full answer to how does the loader find a shared library. You don't need to know that for your experiment. Instead, just read the ld.so manpage and the pages it references. Think of it like your television: you don't care how the ion gun works... just how to change the channel, volume, etc. (As for the make uninstall thing, you hit the nail on the head: where did all those binaries go? Many unixy programs support a --prefix=[path] argument at the configure stage of the build; so all your binaries go under that directory; for example, to install my wine, I use --prefix=/opt/wine, which puts wine in /opt/wine/bin, /opt/wine/lib, etc. But it certainly can get tricky keeping track of this if you are building tons of stuff from source and putting it all in /usr or /usr/local, as is common practice. The best solution I know of, if you are building lots of stuff from source, is to use gentoo, which really does rigorously keep track of what 'make install' did. But I should warn you that gentoo is not always so easy to get up and running as other distributions.) Good luck! You are now in the nasty horizontal part of the learning curve for unix programming and wine. It does get better, just be patient and persistent, and you will prevail. -- gmt It is to be the assent and ratification of the several States, derived from the supreme authority in each State, the authority of the people themselves. The act, therefore, establishing the Constitution, will not be a NATIONAL, but a FEDERAL act. --James Madison, Federalist No. 39
Wine 20031016 Wingdings font encoding problem?
I have wine-20031016 built from source installed on Mandrake 9.1 Programs that had displayed certain characters from the Windows Wingdings font, now display the box that signifies that the character code is not present in the font. With the standard wine (20030315) installed with Mandrake, these characters used to showed up as the astrological zodiac signs, i.e. Aries, Taurus, etc., just as they do when my program is run natively. The font is copied from windows, the Wingdings Truetype font. The character codes are (decimal) 94 - 105 (hex) 0x5E - 0x69 (ascii) ^ - i I have installed these Windows fonts under KDE, and, if I select the Wingdings font in, say KDE Kwrite, and type ^_`abcdefghi, all the expected character glyphs show. is this a bug, or a configuration problem? (I use some other non-Microsoft fonts as well, and some of these work, for the codes used, and some don't, although with earlier versions of wine, they all worked. Since Wingdings is a well-known and used font, I hope that solving the problem for it, will solve it for the others as well.) -- Parzival Herzog
Re: PATCH: dlls/wineps/type42.c
On Tue, 11 Nov 2003, Alexandre Julliard wrote: type42.c: In function `T42_download_header': type42.c:269: warning: int format, DWORD arg (arg 3) type42.c:269: warning: int format, DWORD arg (arg 4) The patch is of course OK, but it makes no difference to the functionality, int and DWORD are the same size. It's only a cosmetic issue. Gosh, I really had my head with some other machines (with larger int); you are right, of course! Gerald -- Gerald Pfeifer (Jerry) [EMAIL PROTECTED] http://www.pfeifer.com/gerald/
Re: [ros-kernel] Re: suggestion: Get native uxtheme and native common controlls working on WINE and ReactOS
At 17.20 12/11/2003, Steven Edwards wrote: We have a uxtheme.dll that is being developed in ReactOS cvs also that supports loading native WinXP themes ha! I wish. Nope, mine is a complementary effort. It's a fake UxTheme API that actually draws in the classic Windows style, to make the future transition to a fully-themed user32 a bit less painful. I happily leave the implementation of the compositing engine to someone else and we have a theme dumping program. most of the code is there, but it requires an elaborate workaround to actually work. I'm not sure why, I think it has to create at least a window before UxTheme stops hiding themes from it
Re: int21 handling
Eric Pouech [EMAIL PROTECTED] writes: I'd suggest changing the oem_files_api to a krnl_file_api_codepage (or something like this) which would be set to either CP_ANSI or CP_OEM and use this variable in most of file related A functions (instead of our current CP_ANSI). Then we would set OEM APIs on int21 entry (and reset to the old mode on exit). I assume we hold a lock while executing the int21 API, so preventing some multi-threading issues on this. I don't think we want to switch the global flag on every int21 call, that's fairly ugly IMO. If int21 needs OEM then it should use OEM explicitly, which is pretty much what it's doing already AFAICS. I see no reason to change that. -- Alexandre Julliard [EMAIL PROTECTED]
Re: Native Dll x Built-in Dll - why everything doesn't work with native dlls
I have notified a recent regression in loading native dlls from database programs like VFP3. I believe that VB work the same way. - Original Message - From: Uwe Bonnes [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, November 12, 2003 3:27 PM Subject: Re: Native Dll x Built-in Dll - why everything doesn't work with native dlls Leonardo == Leonardo Luiz Padovani da Mata [EMAIL PROTECTED] writes: Leonardo Hello all!! My name is Leonardo, and i'm working in a project Leonardo that will migrate thousands of windows NT4 machines to Linux. Leonardo In this project we will do some wine impplementations, if Leonardo needed. Leonardo The apps that we are testing is some VB6/5 apps and DataBase Leonardo client apps. None of the apps executed correctly. So we will Leonardo impplement wine. Leonardo I need to know why when we use Native DLL these apps doesn't Leonardo work. How does wine open the native dll files? Where are the Leonardo doc about that? High level DLLs (like the visual basic dlls) call into low level dlls, like kernel32.dll. If there are bugs in the wine implementation of these dlls, errors will happen, even when a native high level dll is uses. With VB6/5, most errors happen around Ole/Com, as wine still needs a long way in that area. Running with the appropriate native DLLs may circumvent the problem. For migrating, using the native dlls is not a (legal) option however. Native dlls are opened by loading the dll, when the PE header request the dll, just like windows does. Learn the basics from reading low level windows books, and then understand what wine does in what way by reading the wine source and asking good questions on the list. Asking Where are the doc about that? is normally not considered a good question, as you don't show what effort you did yourself to solve that problem. Bye -- Uwe Bonnes[EMAIL PROTECTED] Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt - Tel. 06151 162516 Fax. 06151 164321 --
