> This comes up from time to time, the solution is always compile a
> winelib app with winegcc then use sockets or something to communicate.
> In your server app you can use windows and linux code mixed together.
If you don't need to use linux APIs in your windows application
you can also make a n
On Mon, 5 Nov 2007, Josh Scholar wrote:
[...]
> OK. I need to access COM to do this, and I notice that in "What it WINELIB"
> it says "Also missing are some of the more exotic features of Microsoft's
> compiler like native COM support".
What won't work is if you're using statements such as '#impo
Hi Josh,
(please bottom-post on this list.)
> OK. I need to access COM to do this...
I don't know why you need COM to do this. If you're writing the app
yourself, why not just use a socket?
> Unfortunately, I've never really understood COM very well. Is there an IDL
> compiler for WINE? I
OK. I need to access COM to do this, and I notice that in "What it WINELIB"
it says "Also missing are some of the more exotic features of Microsoft's
compiler like native COM support".
I'm hoping that "native COM support" just means some new fancy add-on that
wasn't in Visual Studio 6.0, and that
Hello Joshua,
Joshua Scholar schreef:
> I really want to have some way to communicate between a Linux program and
> a Windows program running under WINE. The connection doesn't need to be
> high speed, a stream is fine - I'm just sending some unicode text. I'm
> writing both programs myself,
I really want to have some way to communicate between a Linux program and
a Windows program running under WINE. The connection doesn't need to be
high speed, a stream is fine - I'm just sending some unicode text. I'm
writing both programs myself, so I can implement this in the easiest way,
th
