Shachar wrote:
It used to not be possible to write a plugin, to be loaded from a standard Linux ELF program, that will be itself a winelib shared object. All sorts of issues regarding running wineserver and memory layout initializations were problematic.
I'm wondering whether there is any news on that front. Is it still not practically possible to do this?
Last time I asked about this, I got the impression that there was some hope but nobody was working on it. And I think it would require linking something statically into the program, too, so if you're trying to foist winelib shared objects onto an unsuspecting Big App, you're probably going to be out of luck even if this gets worked on.
What application did you have in mind?
Dan Kegel wrote:
What application did you have in mind?
I honestly don't know, yet. I'm meeting a prospective client on Sunday that is currently doing some browser plugin via ActiveX, and wants to support Linux and Mac OSX, as well as Firefox. They were thinking about using Wine for some of the stuff, and converting code for other.
Obviously, I've heard the usual "we'll use winelib as we don't want to bundle the whole of Wine", and had to break it to them that that is not how things work.
At worst, I believe we can run the actual plugin code in a separate process (started by Wine), and have a stub as the actual plugin, and have the two communicate via some IPC. I was just asking in case the problem was miraculously solved by someone while I was away from Wine. What you describe sounds awfully similar to what I remembered, however.
Shachar
On Friday 09 March 2007 14:21 +0100, Shachar Shemesh wrote:
Dan Kegel wrote:
What application did you have in mind?
I honestly don't know, yet. I'm meeting a prospective client on Sunday that is currently doing some browser plugin via ActiveX, and wants to support Linux and Mac OSX, as well as Firefox. They were thinking about using Wine for some of the stuff, and converting code for other.
A couple of years ago two KDE developers were working on something like this as a fun project: http://dot.kde.org/994747675/
At worst, I believe we can run the actual plugin code in a separate process (started by Wine), and have a stub as the actual plugin, and have the two communicate via some IPC. I was just asking in case the problem was miraculously solved by someone while I was away from Wine. What you describe sounds awfully similar to what I remembered, however.
That shouldn't be a problem, Konqueror is doing this for all "Netscape" plugins and I think there is a Firefox plugin which does this with MPlayer
Cheers, Kevin