similar to: My first winelib app - where am I going wrong?

Hi All I'm trying to compile the following program int main() { return 0; } I generated a makefile using winemaker running make I get wineg++ -c -mno-cygwin -o test.o test.cpp wineg++ -mwindows -mno-cygwin -o test.exe.so test.o -lodbc32 -lole32 -loleaut32 -lwinspool -luuid ld: Relocatable linking with relocations from format elf32-i386

Hi all, I am trying to build wine-20040309, and i am facing a gcc crash while compiling winetest. The log is below (sorry : it's localized in french). make[2]: Entre dans le r?pertoire `/home/root/build/wine-20040309/programs/winetest'../../tools/winegcc/winegcc -B../../tools/winebuild -mwindows gui.o main.o send.o util.o winetest.exe.dbg.o gui.res winetest.res -o winetest.exe.so

Hi, I am currently having trouble building the DLLs of an application ported from Win32 to Winelib - compiling, thanks to some hints from Dimi O. Paun, now works fine, only(?) the final linking step fails. Since Winelib-documentation is unfortunately pretty outdated, I tried to orientate myself on the makefiles of the Winelib dlls in the cvs /wine/dlls/ directory. I tried the following

I have a little program coded for windows, and I want to compile it using winegcc. Unfortunately, some functions are not implemented in winelib, and I have to tweak some files. So, How do I submit those changes ? I found nothing on the WineHQ site. SO, if someone knows where to redirect me, I can do it alone! ___________________________________________________________________________

Hello, Would a wine developer please revisit this page http://www.winehq.org/site/docs/winelib-guide/winelib-getting-started and modify it to have a step by step guide to take a Linux box without wine nor winelib to a running notepad exe built by the newbie (and not downloaded)? Or if you are a wine-user, please provide such steps to this list. As a newbie, the statement "It can be found

Hi, I have the following problem - when I compile a DLL using winegcc and call GetModuleFileName on it I get a name in "c:\windows\system", regardless of the DLLs actual location. I have googled for it, and found this thread http://www.winehq.org/pipermail/wine-devel/2003-December/023224.html which says that this behavior is needed for built-in DLLs. My problem is that I'm

Suppose that I have Windows application using Code: LoadLibrary followed by Code: GetProcAddress It should be possible to load a library implemented in terms of POSIX function but I do not understand how. Should I load the dll.so file generated by winegcc or do i need a plain .dll file?[/code]

Hello! I'm trying to port zCPU emulator (http://www.wiremod.com/forum/cpu-tutorials-programs/2956-zcpu-emulator.html) to Linux with winelib. This app is mainly console, but can draw some stuff using SDL. The problem is: compiles fine but when linking I get Code: /usr/lib/wine/libwinecrt0.a(exe_main.o): In function `main': exe_main.c:(.text+0x9d): undefined reference to `WinMain'

Hi, I have Mandriva 2006 x86_64. I tried to install wine, but the binaries are for 32 bits and the result is very instable (win programs close suddenly, no internet available for those programs, etc...) So I tried to compile wine 0.9.14 from source, but I have an error during make when "searching for -lXext" : LD_LIBRARY_PATH="../../libs/unicode:$LD_LIBRARY_PATH"

Hi All, I have implemented a JNI library on window that call the C++ dll APIs. Now I want my JAVA program is run on the UNIX system. I have used WineLib to wrapper Window Dlls to the Share Object Lib (so lib) (Using Winedump and Winegcc to build). The functions in the so lib can work normally with my C main test function. BUT when I call it from Java. The function can linked BUT it is crashed at

Hello, I'm currently trying to use Winelib to port a fairly big windows application to Linux. The application consists of quite a lot of DLLs, some of which don't depend on the Win32 API (they can be compiled with gcc). I think I read all available documentation, but I still have a few questions: - is it possible to link a linux binary with "linux" shared libs and

Hello! Problem with winegcc. Could you please write me where is my mistake? t:~$ LANG=C make pc winegcc -o inkdemo.pc src/*.c -linkview -lfreetype -ljpeg -lz /usr/local/lib/libinkview.a(hw_emulator.o): In function `eink_waveform': hw_emulator.c:(.text+0xa22): undefined reference to `SetBitmapBits' hw_emulator.c:(.text+0xa73): undefined reference to `BitBlt'

What are the advantages of using winegcc over the mingw cross compiler? Also, what are the differences in the header files / libs supplied with each ? I have an app (http://www.autohotkey.com/forum/viewtopic.php?t=46546) cross compiling with mingw using codeblocks, and I have it working under winelib side by side native linux code. I wanted to translate it so it would compile with winegcc so

Hi all, I'm trying to build the Windows version of ZDoom 2.1.7 under Linux with Winelib. Of course, I know that ZDoom can be compiled natively under Linux, but I'm aiming to port Skulltag (which is based on ZDoom) to Linux and if ZDoom can't be build with Winelib, Skulltag can't be either. With little modifications I was able to compile ZDoom with winegcc, but during linking the

I am trying to follow the instructions here (http://www.winehq.org/docs/winelib-guide/bindlls-wrapper) to build a dll with wine that i can load dynamically in a windows wine application. this is what i am doing: MyWinDll.spec Code: 2 stdcall MyWinFunc (int) MyProxyWinFunc MyWin.c Code: #include <windef.h> short MyProxyWinFunc(int *i) { return 5; } shell Code: winemaker --nosource-fix

I installed 1.1.6 and it was working fine except for one application. I installed 0.9.32 after changing my .wine directory to .wine_bak. (someone mentioned that they had got my application to work on the older version). The application still didn't work, so I changed my .wine directory to .wine932, and changed my .wine_bak to .wine. At that point I expected everything to be back to where I had

I tested also with a clean git source. Something wrong with ole32. Code: -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body -Wstrict-prototypes -Wtype-limits -Wwrite-strings -fno-omit-frame-pointer -Wpointer-arith -Wlogical-op -I/usr/include/freetype2 -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0 -o tmarshal_i.o tmarshal_i.c

hi, i'm trying to compile the wine 1.1.9 version, but i get this error. gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wtype-limits -Wpointer-arith -g -O2 -o ntdsapi.o ntdsapi.c ../../tools/winegcc/winegcc -B../../tools/winebuild -shared ./ntdsapi.spec ntdsapi.o -o

Dear all, While trying to port ff-activex-host to Linux with winelib, I got an error as below: $ make wineg++ -c -O0 -W -mno-cygwin -I/home/fracting/wine-git/dlls/atl -DWIN32 -D_WINDOWS -DXP_WIN32 -DMOZILLA_STRICT_API -DXPCOM_GLUE -DXP_WIN -D_X86_ -DNPSIMPLE_EXPORTS -o GenericNPObject.o GenericNPObject.cpp In file included from GenericNPObject.cpp:36: GenericNPObject.h:39: fatal error:

Unfortunately not all our documentation is up to date. We try to move more to our wiki and update it there but I'm not sure if there is winegcc stuff there already. You have roughly two options. The easiest one is to dynamically load the dll using LoadLibrary and load the functions you need using GetProcAddress. Another way is to create a dummy dll against which you can link. You need