similar to: No subject

Hi. I'm not sure if this is the correct place for this question, or if the wine-devel list is more appropriate; please let me know if I should ask over there. I'm trying to build, using winemaker/winegcc/etc, a DLL for use with a Windows binary. This is a somewhat unusual case, in that this library is actually explicitly being written for a Windows binary that will run in Linux (I'm

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

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, We just started using WineLib, and have very basic question: which -g??? option do you use to do source level debugging with winedbg? I searched the documentation and mailing list for any step-by-step about this, but found nothing. So either the answer is so obvious that I just can't see it - or it doesn't work? By default, winemaker seems configure things for no debug - so

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

Hi, The company I work for, has asked me to use winelib to port some code, however I have a problem compiling the MFC. I run winemaker 0.5.7 with options: 'winemaker --lower-uppercase -nomfc --dll ./ > \ winemaker_output.txt' No errors in file or stderror; further winemaker accesses the correct directories. But when I run ./configure as: './configure --with-wine=/usr/bin \

Hi all, I''ve got a preliminary JRuby version of win32-api checked into CVS at the moment under win32-api/lib/win32/api.rb. I''ve also pasted it below. It doesn''t quite work right in that I can''t get it to modify the arguments in place in the API#call method. Take a look at the sample code at the very bottom to see what I mean. I haven''t even tried

Hi, the following patch is a (hopefully least intrusive) extension when sshd is started so that it daemonizes itself. In that case Windows 9x/Me has a slight problem with sshd as soon as the current user logs off. The sshd daemon will be killed as well. Since installing services is very different between NT and 9x, the way used for NT boxes isn't working well for 9x. For that reason

1) i'm facing problem while compiling MFC code when "winemaker" command is given i get these lines admin at XXX:~/.wine/drive_c/windows/system32/MFC> winemaker --lower-uppercase . Winemaker 0.6.0 Copyright 2000 Francois Gouget <fgouget at codeweavers.com> for CodeWeavers closedir() attempted on invalid dirhandle DIRECTORY at /usr/local/bin/winemaker line 1054. closedir()

Marcus Meissner wrote: > > In article <ax%R6.33895$hV3.53576@newsfeeds.bigpond.com>, > David Rowe <voicet@bigpond.com.au> wrote: > >1) Why does winemaker (after ./configure, make etc) produce a library and > >sym link as the output, e.g. why not an executable. > > This is the usual invokation method of WINE binaries. Do not worry. This is an excellent

Hi. I'm currently starting the process of porting a windows based gaming engine (uses the windows API),to linux. I have winelib (winemaker?) and have read through it's documentation but am still unsure what it's really for. Is it possable to use winelib to assist me in porting this engine from windows to linux,is that what it's for? If so,do I have to provide all nessesary

Hi - I wrapped R.dll up using somebody code online (see below). I am comparing R on .NET IPC with R(D)COM. I got it all working. Except, I realize that in my client code of the IPC remoting, if I call 'plot' function in R via EvaluateNoReturn, I don't seem to see any results on the R plot window (although the window pops up). Is there anything to do with the code of R.dll wrapper

On Mon, Oct 4, 2010 at 3:22 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >>>> Any help will be much appreciated. Thanks! >>> Windows does not support dynamic linking. You will need to resolve >>> externals by hand. >> >> Why would it not support dynamic linking?  What about loadlibrary and >> its kin are not sufficient to handle

I remember seeing a message somewhere about C++ DLLs and wanting to implement them in Winelib. Well here is an idea that I use in Windows that works great: Define your class in a common header (let's call it dll.hpp): class DllClass { public: int somedata; virtual void member(int arg); }; Define the DLL source with two exports: #include <dll.hpp> extern "C"

Sorry for the attachment, but I do not know of another way to communicate the details of my proposed changes to the dev team. While writing RipTrax (a ripper + encoder program), I wanted to make all encoder DLLs dynamically linkable at runtime. I first check for the existence of the dll, open the library with Load Library and then do a GetProcAddress for each routine I plan to use. With the

Any chance of some help please? I have just started trying to get WineLib working on my machine, after playing with wine for several months. I am starting slowly. The BASIC hello, world. (no graphics, no Microsoft etc) I run winemaker and configure (with -L/usr/local/lib) make generates ./hw2.spec:7: could not open .so file for advapi32.dll I am aware of the discussion in January (compiling

I read the following on wine HQ: Linking in .lib Files .... You cannot use .lib files directly with Winelib. The reason is that winebuild does not support reading .lib files. Support for '.lib' files (or possibly even '.dll' files) could be added in but it is not there currently. Exactly how you deal with that depends on what your situation: 1.if you

I am attempting to use winemaker on a relatively straightforward Windows App that we have. Just a little background, we started the effort by first evaluating our application in Wine itself and obtained very good results. Now, we're moving on to try and compile a version for Linux by using Winelib and running into this problem. I ran winemaker with this: winemaker --lower-all which finished

Well, from my recent experience with Winelib, I can tell you this: Winemaker currently sucks, and the makefiles it creates are nonfunctional and you'll have to redo them by hand anyway. Yeah. If I knew anything about how to fix it I just might be tempted to do so :) Thanks, Scott Ritchie On Sat, 2005-01-22 at 13:19 -0800, Dan Dennison wrote: > Building MFC for winelib has been

Full_Name: Venkatesh Mysore Version: R-1.7.0 OS: WindowsXP Submission from: (NULL) (216.165.110.10) While accessing Rproxy.dll repeatedly (using the code from the (D)COM example in the R website) causes a failure in the 24th iteration. R-1.6.2 does NOT give this error. This seems to be a memory management error, that might be linked to the huge leakage difference between R-1.7.0 and R-1.6.2