Am Donnerstag 12 April 2007 15:57 schrieb Phil Lodwick:
> > What is the problem with running the whole app as a winelib app?
> > You don't save any resources by having the application outside
> > since you still have wine running, and you have the IPC overhead.
>
> I want to provide a library other
> What is the problem with running the whole app as a winelib app?
> You don't save any resources by having the application outside
> since you still have wine running, and you have the IPC overhead.
I want to provide a library other developers can use without having them
worry about the intric
Am Donnerstag 12 April 2007 00:28 schrieb Phil Lodwick:
> > or to write some proxy winelib app and
> > talk to the DLL using ipc like sockets,
> > pipes, shared memory, etc.
>
> Thanks Stefan. I thought I was missing something.
>
> This was the approach that I was planning on as a backup. Looks l
> or to write some proxy winelib app and
> talk to the DLL using ipc like sockets,
> pipes, shared memory, etc.
Thanks Stefan. I thought I was missing something.
This was the approach that I was planning on as a backup. Looks like I bring
the backup plan to the front burner. Basically Linux
I'm not the DLL expert, but I think you're missing something here.
The problem is that your windows dll will most likely use the windows
api(otherwise, don't use wine at all). The windows API depends on some other
things, like a few memory management constraints, the windows registry, and
most
Greetings,
My googling skills are letting me down today. I believe I have seen several
people requesting to do the same and answers indicating it is possible.
However, after several hours of reading email archives from 2000-2007 are am
officially confused :-(
I have successfully ported an appli
