Ken Larson wrote:
Thanks for the info.
Ultimately, my app is a Java app. I am spawning my EXE wrapper around
my DLL and talking to it from Java with sockets. So unless I'm
missing something, my entire (Java) app can't be a winelib linux app
(barring something like gcj which I'm not sure
Boaz Harrosh wrote:
Ken Larson wrote:
This assumes that I'm using winelib, correct? (I currently am not, I'm
compiling on windows, but considering using winelib instead)
Yes!! Winelib can be both your DLL calling code, and you complete Linux
application. No need for .EXE compiled or
Dmitry Timoshkov wrote:
Mike McCormack [EMAIL PROTECTED] wrote:
It looks like the only dependency is from the PostMessageA in
dlls/winsock/async.c #514.
The windows version of ws2_32.dll does not link to user32.dll however,
it appears to load it on demand. I can see the following strings
Ken Larson [EMAIL PROTECTED] wrote:
depends.exe shows that ws2_32 has a delay load dependency on user32.
We have to move user32 to a delay loaded section as well in our version.
So do I interpret this to mean there is a plan to change this in wine?
That would be great.
I sent a patch
Ken Larson wrote:
Thanks for the info.
Ultimately, my app is a Java app.
If I recall correctly someone has reported Installation of Sun's Java
for windows under wine. Or was it A failure to install? I can't recall.
How would you call a DLL on Windows?
Free Life
Boaz
Boaz Harrosh wrote:
Ken Larson wrote:
Thanks for the info.
Ultimately, my app is a Java app.
If I recall correctly someone has reported Installation of Sun's Java
for windows under wine. Or was it A failure to install? I can't recall.
How would you call a DLL on Windows?
Free Life
Boaz
On Mon, 3 Oct 2005, Boaz Harrosh wrote:
Ken Larson wrote:
Thanks for the info.
Ultimately, my app is a Java app.
If I recall correctly someone has reported Installation of Sun's Java
for windows under wine. Or was it A failure to install? I can't recall.
How would you call a DLL on
Remove the call to WSAStartup, and the program requires no X display.
As I said, I know winsock uses hidden windows handles to do some things,
which is pretty ugly architecturally. However, it seems like it should
be possible to not have a display in this case. any ideas?
It looks like
Ken Larson wrote:
Well I am actually using a command-line with CL to compile it, but it
was true that I had a WinMain instead of main.
I've changed the WinMain to main, but this doesn't seem to be the issue.
The issue appears to be initializing winsock. The following simple main
program,
Mike McCormack [EMAIL PROTECTED] wrote:
It looks like the only dependency is from the PostMessageA in
dlls/winsock/async.c #514.
The windows version of ws2_32.dll does not link to user32.dll however,
it appears to load it on demand. I can see the following strings in it:
USER32.dll
cool, can you point me to where i can find the info on how to easily set
up this cross-compiler on linux?
thanks,
Ken
Richard Cohen wrote:
Ken Larson wrote:
Well I am actually using a command-line with CL to compile it, but it
was true that I had a WinMain instead of main.
I've changed
On Sunday 25 September 2005 05:37, Ken Larson wrote:
I'm using wine to access a particular proprietary DLL (I don't have the
source for it) on Linux. The way I'm doing this is to write an EXE that
wraps the DLL, and makes all of the functions available via socket
request and response
Hi Ken,
On Sunday 25 Sep 2005 10:37, Ken Larson wrote:
2. The sockets trick was the simplest way I could figure out how to
do IPC between a linux process and a wine process. However, is
there are any better or faster way to do this? As far as I know I
can't use winelib because I don't have
Alex Villacís Lasso wrote:
You can try installing and configuring this X server. It will not
output anything or use a console, but will behave otherwise like a
valid X server. Then you should point the DISPLAY environment variable
to this X server, and this will keep your app happy.
Kuba Ober wrote:
On Sunday 25 September 2005 05:37, Ken Larson wrote:
I'm using wine to access a particular proprietary DLL (I don't have the
source for it) on Linux. The way I'm doing this is to write an EXE that
wraps the DLL, and makes all of the functions available via socket
request and
On Fri, 30 Sep 2005, Jakob Eriksson wrote:
Alex Villacís Lasso wrote:
You can try installing and configuring this X server. It will not
output anything or use a console, but will behave otherwise like a
valid X server. Then you should point the DISPLAY environment variable
to
2. The sockets trick was the simplest way I could figure out how to do
IPC between a linux process and a wine process.
However, is there are
any better or faster way to do this? As far as I know I can't use
Your .exe can make regular linux syscalls as it's really running on
linux. So
I'm using wine to access a particular proprietary DLL (I don't have the
source for it) on Linux. The way I'm doing this is to write an EXE that
wraps the DLL, and makes all of the functions available via socket
request and response messages. My linux program has access to the
functions of
Ken Larson wrote:
I'm using wine to access a particular proprietary DLL (I don't have
the source for it) on Linux. The way I'm doing this is to write an
EXE that wraps the DLL, and makes all of the functions available via
socket request and response messages. My linux program has access to
Alex -
Thanks for the good info. As far as not needing an X server, when I try
to run my exe under wine without one, I get:
wine: Could not load graphics driver 'x11drv'.
Make sure that your X server is running and that $DISPLAY is set correctly.
but yes, the regedit /? trick works fine.
I
Ken Larson wrote:
Alex -
Thanks for the good info. As far as not needing an X server, when I
try to run my exe under wine without one, I get:
wine: Could not load graphics driver 'x11drv'.
Make sure that your X server is running and that $DISPLAY is set
correctly.
but yes, the regedit
21 matches
Mail list logo
