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
On Fri, Sep 30, 2005 at 08:41:17AM +0200, Jakob Eriksson wrote:
Luke Kenneth Casson Leighton wrote:
i am making the amateur version of progress: i just had
echo_server.exe run for the first time on win32: echo_client.exe
has been running successfully since this morning.
That's
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
Folks,
I just released 20050930, this should be considered the pre-0.9
release, so please give it some good testing. In particular, please
test the things that new users will encounter first, like the
automatic .wine creation and winecfg.
Even if you normally build from source, please for once
I think we need some more clean up of bugzilla, we need to close bugs
till 2003/04 which have not updates since 6 months. And also those
which cannot be replicatable.
bye,
Vijay
On 9/30/05, Alexandre Julliard [EMAIL PROTECTED] wrote:
Folks,
I just released 20050930, this should be considered
Mike McCormack [EMAIL PROTECTED] wrote:
--- dlls/msi/action.c 30 Sep 2005 10:32:41 - 1.211
+++ dlls/msi/action.c 30 Sep 2005 11:33:20 -
@@ -46,6 +46,8 @@ http://msdn.microsoft.com/library/defaul
#define REG_PROGRESS_VALUE 13200
#define COMPONENT_PROGRESS_VALUE 24000
+#define
Dmitry Timoshkov wrote:
Do you really need this define? It looks like it's unused (not mentioning
that it breaks Wine rules on using unicode APIs).
I thought that too before I sent the patch, so I removed it and
recompiled just to make sure. It's used by the following definition in
On 9/30/05, Alexandre Julliard [EMAIL PROTECTED] wrote:
We also still need many documentation updates, so please consider
helping with that.
Is anyone actually working on this? I might have some time this
weekend, but I don't want to step on any toes.
-Brian
Brian Vincent schreef:
On 9/30/05, Alexandre Julliard [EMAIL PROTECTED] wrote:
We also still need many documentation updates, so please consider
helping with that.
Is anyone actually working on this? I might have some time this
weekend, but I don't want to step on any toes.
-Brian
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
Hi people,
I read in the today's Wine Weekly News something about rpms for Fedora
Core 4.
In august I begann building some for FC 4. I built rpm's for the july
and the august version.
The rpm's were based on Vincent Beron's. They were downloaded about 700
times from my server.
There is also a
For information on debugging, these official docs may help
http://www.winehq.org/site/docs/wine-devel/debugging
http://www.winehq.org/site/docs/wine-devel/index
http://wiki.winehq.org/DebuggingTutorials
there is an unofficial list of examples from the mailing lists, here.
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.
Luke Kenneth Casson Leighton wrote:
i am making the amateur version of progress: i just had
echo_server.exe run for the first time on win32: echo_client.exe
has been running successfully since this morning.
That's really great!
//Jakob
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
From: Dieter Komendera [EMAIL PROTECTED]
Any comments, improvements, suggestions are very welcome!
FC4 is a popular distro, we _need_ an official binary
build for it for the upcoming beta. If Vincent is not
going to do it, we need to get these official build
uploaded to SF together with all the
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
On 9/30/05, Alex Villacís Lasso [EMAIL PROTECTED] wrote:
This patch is required in order to run any application that embeds
DBGRID32.OCX from MS VisualBasic 5 or 6
Changelog:
* Add additional condition for creation of interface
A patch would be nice =)
Thanks
Steven
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
Alexandre Julliard wrote:
Folks,
I just released 20050930, this should be considered the pre-0.9
release, so please give it some good testing. In particular, please
test the things that new users will encounter first, like the
automatic .wine creation and winecfg.
This is fantastic.
I have
Could somebody please point me to an online documentation on the
functions exported by DIBENG.DLL and how an userspace application could
use them? I want to evaluate whether a possible DIB engine for Wine
could use the DIBENG.DLL API. I googled and all I find are reports of
GPFs involving
On 9/30/05, Dan Kegel [EMAIL PROTECTED] wrote:
I'll be updating the page
http://kegel.com/wine/qa/
with bugzilla statistics
State2005.09.29
Unconfirmed 836
New 403
Assigned68
Resolved421
Closed 1476
(Sorry 'bout that. I'm not used to gmail's interface yet.)
Alexandre wrote:
Bugzilla has had a good cleanup lately (thanks guys!) and most of the
irrelevant bugs have been closed, so please have a look at the
remaining ones to see if there's anything you know how to fix.
I'll be updating the page
http://kegel.com/wine/qa/
with bugzilla statistics
26 matches
Mail list logo
