May 2004 - Wine-Devel - list.winehq.org

Re: Exporting symbols
by Dan Timis May 13, 2004

May 13, 2004

> From: Mike Hearn <mh(a)codeweavers.com> > Subject: Re: Exporting symbols > Date: Thu, 13 May 2004 10:39:42 +0100 > Organization: CodeWeavers, Inc > > On Wed, 12 May 2004 19:45:42 -0700, Dan Timis wrote: >> After running strip on the .exe.so if we do nm -D all the symbols are >> still there. Is there any way to get rid of the ones that are not >> needed for dynamic linking? > > Dmitry is right, ask on the binutils list. However if you hide symbols > using the --retain-symbols-file trick or versioning scripts, you may be > able to mangle the symbol table without breaking anything. Why not try > it > - write a program to scan .symtab for the symbols you want to hide and > scramble the strings. I'd be interested to hear the results. > > ELF was not really designed for code obfuscation like this though. I > think > nvidia use a preprocessor to mangle symbols in the final binary, if you > ask them they may be willing to tell you how it's done (maybe even give > you the code). > > thanks -mike Thanks Mike and Dmitry, I'll try the binutils list. I might do code obfuscation. But, it may be safer for me to do something like: #define MyClass F18Rsjkfgwe6 #define MyMethod aYSm48dYo49H class MyClass { void MyMethod(cha *, bool); etc. rather than mess with the binaries. Dan

1 0

Alsa compilation error
by Francois Gouget May 13, 2004

May 13, 2004

revision 1.42 date: 2004/05/05 22:03:48; author: julliard; state: Exp; lines: +143 -67 James Courtier-Dutton <James(a)superbug.demon.co.uk> Updated to the new alsa api. This patch causes a compilation error on my build machine: alsa-headers 0.9+0beta12-3 gcc -c -I. -I. -I../../../include -I../../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o audio.o audio.c audio.c: In function `ALSA_TraceParameters': audio.c:398: too many arguments to function `snd_pcm_hw_params_get_access' audio.c:399: too many arguments to function `snd_pcm_hw_params_get_format' audio.c:448: too many arguments to function `snd_pcm_hw_params_get_channels' audio.c:452: too many arguments to function `snd_pcm_hw_params_get_channels_min' audio.c:453: too many arguments to function `snd_pcm_hw_params_get_channels_max' audio.c:462: too many arguments to function `snd_pcm_hw_params_get_buffer_size' audio.c:466: too many arguments to function `snd_pcm_hw_params_get_buffer_size_min' .... It looks like it removed compatibility macros. Why? -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Computers are like airconditioners They stop working properly if you open WINDOWS

3 4

Winelib and MFC and mixing native Windows DLLs
by Raghavan Gurumurthy May 13, 2004

May 13, 2004

I am trying to build my MFC-based Windows application on Linux. First question - I read in the Winelib user guide that I have to build MFC completely on Winelib as well. Is this really a must? Is there no other alternative? Second question - If my Windows application uses 10 DLLs, do I have to build all these 10 DLLs in addition to the executable on Winelib? Or can I leave the 10 DLLs run in 'native' mode and only convert the executable to be built with Winelib? Thanks in advance, Raghavan

3 2

Winelib Native Linux App
by Simon Craythorn May 13, 2004

May 13, 2004

I'm a little confused on two points. I wrote a simple windows application just to open a window. It has a file menu with exit on it, and that's about it. All the documentation I read for Winelib suggests that re-compiling the application is the best option as this will give a native linux app that can be run directly. But when I compile this app with winelib it generates "winer.exe.so" which needs to be started with the command "wine winer.exe.so". This isn't my idea of being able to be run directly. Secondly, all my windows apps and DLL's are in Borland Builder (just native Win32 C, no VCL/MFC or other third party products). I have Kylix3 installed. I've managed to re-compile my test app with Kylix and link it to the Wine libraries. When I try and run the resulting executable it complains that it can't fine kernel32.dll.so. Just to test I tried copying kernel32.dll.so to the same place as my test app, same result. I added /usr/lib/wine to ld.so.conf and ran ldconfig, but this doesn't help either. Anyone any ideas on either of these issues. Searching the lists it seems I'm the only one to attempt compiling with Kylix at all. -- Simon Craythorn using MailCopa V6.01 InterVations, Inc http://www.intervations.com http://www.mailcopa.com

1 0

[patch] Listview drag-and-drop fix
by Paul Rupe May 13, 2004

May 13, 2004

Xnews was treating all mouseclicks as drag-and-drop operations in the newsgroup listview. The problem was that LISTVIEW_TrackMouse was losing the WM_LBUTTONUP message. This patch adds the missing call to DispatchMessage. License: X11, LGPL Changelog: <prupe(a)myrealbox.com> Dispatch the last message when exiting LISTVIEW_TrackMouse -- Paul Rupe <prupe(a)myrealbox.com> "She smiled, in the end."

2 3

Re: winmm test patch
by Andreas Mohr May 13, 2004

May 13, 2004

Hi, On Thu, May 13, 2004 at 07:30:27AM -0400, Robert Reif wrote: > Adds better error messages. Would probably be more useful to use an often-used construct like: #define DEVTYPE_TO_STR(dev) case dev: return #dev Andreas Mohr

1 0

Load a .so from a Windows binary using Wine
by Raghavan Gurumurthy May 13, 2004

May 13, 2004

I have a Windows GUI application that runs on Wine (not Winelib). Now i want to use that code to load a native Linux .so - how can i do this? Thanks in advance, Raghavan

4 3

Exporting symbols
by Dan Timis May 13, 2004

May 13, 2004

Hi, We need to have a library that links statically to a wine application. The wine application is an .exe.so, so everything becomes in the end an exe.so. The problem we have is that all the symbols are exposed. I have very little experience with Windows, but I understand that with a Windows DLL you can export certain functions, while hiding the others. I know that's also true for the Mac. Is there any way to export only the functions that are called by the code we link to, without exposing the internal workings? Ideally we would like to be able to provide a static library created with ar or ranlib, link that library with other object files to create a .exe.so for wine, but when you do "nm" on the resulting .exe.so you would not see all the inner workings of our library. Is that possible? Thanks, Dan Timis Muse Research, Inc.

3 4

Clipboard functionality across processes
by Santosh Siddheshwar May 12, 2004

May 12, 2004

Hi, Does WINE support access to clipboard data across WINE processes. For e.g. one app opens the clipboard and sets data into it using SetClipboardData, closes it and then exits. The other app tries to retrieve this data. It works in windows but doesnt seem to do so in WINE. Regards Santosh Siddheshwar ********************************************************************* Disclaimer: The information in this e-mail and any attachments is confidential / privileged. It is intended solely for the addressee or addressees. If you are not the addressee indicated in this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. *********************************************************************

3 2

probs w/ make and make install
by eternal＠antelecom.net May 12, 2004

May 12, 2004

cd `dirname dlls/__install-lib__` && make install-lib rm -f libdxerr8.a && ln -s dxerr8/libdxerr8.a libdxerr8.a rm -f libdxerr9.a && ln -s dxerr9/libdxerr9.a libdxerr9.a rm -f libdxguid.a && ln -s dxguid/libdxguid.a libdxguid.a rm -f libuuid.a && ln -s uuid/libuuid.a libuuid.a cd `dirname advapi32/__install__` && make install ../../tools/mkinstalldirs -m 755 /usr/local/lib/wine /usr/bin/install -c advapi32.dll.so /usr/local/lib/wine/advapi32.dll.so cd `dirname amstream/__install__` && make install ../../tools/mkinstalldirs -m 755 /usr/local/lib/wine /usr/bin/install -c amstream.dll.so /usr/local/lib/wine/amstream.dll.so cd `dirname avicap32/__install__` && make install ../../tools/mkinstalldirs -m 755 /usr/local/lib/wine /usr/bin/install -c avicap32.dll.so /usr/local/lib/wine/avicap32.dll.so cd `dirname avifil32/__install__` && make install ../../tools/mkinstalldirs -m 755 /usr/local/lib/wine /usr/bin/install -c avifil32.dll.so /usr/local/lib/wine/avifil32.dll.so make: don't know how to make _install_/avifile.dll.so. Stop *** Error code 2 Stop in /usr/home/vertigo/wine-20040505/dlls. *** Error code 1 Stop in /usr/home/vertigo/wine-20040505. ----------------------------- this is the 2nd stop that occured... during make, towards the end, it couldn't open /home/vertigo/wine-20040505/programs/winetest/advapi32_test.exe... i checked in that dir, and the files were still *_test.exe.so. seemingly, the previous step that copied these files here also stripped them, but did not change their names (remove the .so). i did this manually, and retried make, which finished. the above stop happens almost immediatly from make install. this is on freebsd4.9, and this is basically the same that has always happened for me with all versions of wine i've tried. can someone either help me get this to work, or atleast stop the spreading of the lie that wine works on bsd (have never heard someone say that they had it running on bsd). i've been kicking this horse for months, is it dead? -shaun

2 1