[X2go-dev] Compiling x2go Windows client

----- Original Message -----

Post by --[ UxBoD ]--
Hi,
I am attempting to compile the win client and have installed the QT
SDK, MinGw and the x2goclient sources. They have been added to the
environment path to allow the compilation binaries to be found. The
readme says that one should rename x2goclient.pro with
x2goclient.pro.windows yet the latter file does not exist?
I decided to press on and ran qmake followed by make which completed
without any errors. I found the x2goclient.exe within the debug
directory and once I ran it the normal client screen popped up but was
immediately followed by the error "Runtime Error!" from the Microsoft
Visual C++ Runtime Library.
Would very much appreciate some help in resolving the problem please.

Okay I have now got it to start vcxsrv, sshd and pulse by copying the x2goclient.exe binary to c:\program files\x2goclient\ though when I try and connect to a session it just hangs on connecting :( The code I changed was in onmainwindow.cpp to the following:

/* xorg-> setWorkingDirectory ( appDir+"\\xming" ); */
/* xorg->start ( appDir+"\\xming\\xming.exe",args ); */
xorg-> setWorkingDirectory ( "C:\\program files\\vcxsrv" );
xorg->setEnvironment ( env );
xorg->start ( "C:\\program files\\vcxsrv\\vcxsrv.exe",args );

What I have noticed though it that the binary I compile is huge compared to the one that is shipped. Is that due to it being in some sort of debug mode or has the binary been stripped ?

--
Thanks, Phil

John A. Sullivan III

2010-11-09 16:17:45 UTC

Post by --[ UxBoD ]--
----- Original Message -----

/* xorg-> setWorkingDirectory ( appDir+"\\xming" ); */
/* xorg->start ( appDir+"\\xming\\xming.exe",args ); */
xorg-> setWorkingDirectory ( "C:\\program files\\vcxsrv" );
xorg->setEnvironment ( env );
xorg->start ( "C:\\program files\\vcxsrv\\vcxsrv.exe",args );
What I have noticed though it that the binary I compile is huge compared to the one that is shipped. Is that due to it being in some sort of debug mode or has the binary been stripped ?

What args are being passed? I would guess that the arguments (or at
least the syntax) are different between Xming and vcxsrv.

Regarding size, I wonder if your binary is statically linked instead of
dynamically linked (not that I understand linking very well!) - John

Gerry Reno

2010-11-09 16:27:12 UTC

Post by John A. Sullivan III

Post by --[ UxBoD ]--
----- Original Message -----

What args are being passed? I would guess that the arguments (or at
least the syntax) are different between Xming and vcxsrv.
Regarding size, I wonder if your binary is statically linked instead of
dynamically linked (not that I understand linking very well!) - John
_______________________________________________

Phil,
Sounds like you're making good progress. As John says you may need to
adjust the args.

Sometimes statically linked can actually be better because you're not
dependent on people having specific DLL's installed or the
correct/compatible versions of DLL's.

How much bigger is your binary?

Regards,
Gerry

Heinz-M. Graesing

2010-11-09 16:40:50 UTC

Hello,

Post by --[ UxBoD ]--
----- Original Message -----
What I have noticed though it that the binary I compile is huge compared to the one that is shipped. Is that due to it being in some sort of debug mode or has the binary been stripped ?

please configure Qt for building "release" binaries (it looks like
you're building the client in debug mode).

best regards,

Heinz

--[ UxBoD ]--

2010-11-09 17:02:05 UTC

----- Original Message -----

Post by --[ UxBoD ]--
----- Original Message -----
What I have noticed though it that the binary I compile is huge
compared to the one that is shipped. Is that due to it being in some
sort of debug mode or has the binary been stripped ?

please configure Qt for building "release" binaries (it looks like
you're building the client in debug mode).
best regards,
Heinz

Thanks Heinz.

I have now compiled it as a release binary and it is a lot smaller now :) Still having the same problem though that when I launch x2goclient it starts up vcxsrv, sshd and pulse okay; the x2go status screen changes to say Connecting and then it hangs :( What I think is happening is that vcxsrv is ignoring the display parameter that is passed to it. If I run xcalc -display localhost:0 that works; though if I try xcalc -display:6000 it fails. I am guessing the next step should be the NX libraries etc starting. Any ideas ?

--
Thanks, Phil

Oleksandr Shneyder

2010-11-10 06:54:02 UTC

Post by --[ UxBoD ]--
----- Original Message -----

Post by --[ UxBoD ]--
----- Original Message -----
What I have noticed though it that the binary I compile is huge
compared to the one that is shipped. Is that due to it being in some
sort of debug mode or has the binary been stripped ?

please configure Qt for building "release" binaries (it looks like
you're building the client in debug mode).
best regards,
Heinz

Thanks Heinz.
I have now compiled it as a release binary and it is a lot smaller now :) Still having the same problem though that when I launch x2goclient it starts up vcxsrv, sshd and pulse okay; the x2go status screen changes to say Connecting and then it hangs :( What I think is happening is that vcxsrv is ignoring the display parameter that is passed to it. If I run xcalc -display localhost:0 that works; though if I try xcalc -display:6000 it fails. I am guessing the next step should be the NX libraries etc starting. Any ideas ?

Hello,

0 - Display number
6000 - TCP port

TCP port = Display number + 6000

regards

--
Oleksandr Shneyder
Dipl. Informatik
X2go Core Developer Team

email: ***@obviously-nice.de
web: www.obviously-nice.de

--> X2go - ***@home

--[ UxBoD ]--

2010-11-10 09:20:27 UTC

----- Original Message -----

Post by --[ UxBoD ]--
----- Original Message -----

Post by --[ UxBoD ]--
----- Original Message -----
What I have noticed though it that the binary I compile is huge
compared to the one that is shipped. Is that due to it being in
some
sort of debug mode or has the binary been stripped ?

please configure Qt for building "release" binaries (it looks like
you're building the client in debug mode).
best regards,
Heinz

Thanks Heinz.
I have now compiled it as a release binary and it is a lot smaller
now :) Still having the same problem though that when I launch
x2goclient it starts up vcxsrv, sshd and pulse okay; the x2go status
screen changes to say Connecting and then it hangs :( What I think
is happening is that vcxsrv is ignoring the display parameter that
is passed to it. If I run xcalc -display localhost:0 that works;
though if I try xcalc -display:6000 it fails. I am guessing the next
step should be the NX libraries etc starting. Any ideas ?

Hello,
0 - Display number
6000 - TCP port
TCP port = Display number + 6000
regards

Yep, but still not dice. It gets to the point of connecting and then just hangs. I can see all the necessary processes running and obviously X is working okay. Will check from the server side and see if it is even attempting to start the session.

--
Thanks, Phil

--[ UxBoD ]--

2010-11-10 09:52:08 UTC

----- Original Message -----

Post by --[ UxBoD ]--
----- Original Message -----

Post by --[ UxBoD ]--
----- Original Message -----

Post by --[ UxBoD ]--
----- Original Message -----
What I have noticed though it that the binary I compile is huge
compared to the one that is shipped. Is that due to it being in
some
sort of debug mode or has the binary been stripped ?

please configure Qt for building "release" binaries (it looks
like
you're building the client in debug mode).
best regards,
Heinz

Thanks Heinz.
I have now compiled it as a release binary and it is a lot smaller
now :) Still having the same problem though that when I launch
x2goclient it starts up vcxsrv, sshd and pulse okay; the x2go
status
screen changes to say Connecting and then it hangs :( What I think
is happening is that vcxsrv is ignoring the display parameter that
is passed to it. If I run xcalc -display localhost:0 that works;
though if I try xcalc -display:6000 it fails. I am guessing the
next
step should be the NX libraries etc starting. Any ideas ?

Hello,
0 - Display number
6000 - TCP port
TCP port = Display number + 6000
regards

Yep, but still not dice. It gets to the point of connecting and then
just hangs. I can see all the necessary processes running and
obviously X is working okay. Will check from the server side and see
if it is even attempting to start the session.

After watching the remote server the SSH session is not even being attempted to be established :( I have even tried setting the working directory back to being xming once vcxsrv has been started incase I was corrupting a path further down the chain; though still no joy. Any ideas please ?

--
Thanks, Phil

--[ UxBoD ]--

2010-11-10 10:02:21 UTC

----- Original Message -----

Post by --[ UxBoD ]--
----- Original Message -----

Post by --[ UxBoD ]--
----- Original Message -----

Post by --[ UxBoD ]--
----- Original Message -----
What I have noticed though it that the binary I compile is
huge
compared to the one that is shipped. Is that due to it being
in
some
sort of debug mode or has the binary been stripped ?

please configure Qt for building "release" binaries (it looks
like
you're building the client in debug mode).
best regards,
Heinz

Thanks Heinz.
I have now compiled it as a release binary and it is a lot
smaller
now :) Still having the same problem though that when I launch
x2goclient it starts up vcxsrv, sshd and pulse okay; the x2go
status
screen changes to say Connecting and then it hangs :( What I
think
is happening is that vcxsrv is ignoring the display parameter
that
is passed to it. If I run xcalc -display localhost:0 that works;
though if I try xcalc -display:6000 it fails. I am guessing the
next
step should be the NX libraries etc starting. Any ideas ?

Hello,
0 - Display number
6000 - TCP port
TCP port = Display number + 6000
regards

Yep, but still not dice. It gets to the point of connecting and then
just hangs. I can see all the necessary processes running and
obviously X is working okay. Will check from the server side and see
if it is even attempting to start the session.

After watching the remote server the SSH session is not even being
attempted to be established :( I have even tried setting the working
directory back to being xming once vcxsrv has been started incase I
was corrupting a path further down the chain; though still no joy. Any
ideas please ?

I am now compiling the x2goclient as a release version but look at the difference in size to the one that is distributed:

C:\Program Files\x2goclient>dir x2goclient.exe
26/11/2009 10:11 4,915,200 x2goclient.exe

C:\Program Files\x2goclient>dir c:\x2goclient-3.01\release\x2goclient.exe
10/11/2010 09:32 1,699,840 x2goclient.exe

The one I have compiled is half the size! Where is the x2goclient.pro.windows file that is mentioned in README.WINDOWS as I cannot find it ??

--
Thanks, Phil

John A. Sullivan III

2010-11-10 12:23:31 UTC

On Wed, 2010-11-10 at 10:02 +0000, --[ UxBoD ]-- wrote:
<snip>

Post by --[ UxBoD ]--
C:\Program Files\x2goclient>dir x2goclient.exe
26/11/2009 10:11 4,915,200 x2goclient.exe
C:\Program Files\x2goclient>dir c:\x2goclient-3.01\release\x2goclient.exe
10/11/2010 09:32 1,699,840 x2goclient.exe
The one I have compiled is half the size! Where is the x2goclient.pro.windows file that is mentioned in README.WINDOWS as I cannot find it ??

I do not know the answer but I do remember there was a lengthy
discussion on the list about this that can probably be dug out of the
archives - John

--[ UxBoD ]--

2010-11-10 11:28:24 UTC

----- Original Message -----

Post by --[ UxBoD ]--
----- Original Message -----

Post by --[ UxBoD ]--
----- Original Message -----

Post by --[ UxBoD ]--
----- Original Message -----
What I have noticed though it that the binary I compile is
huge
compared to the one that is shipped. Is that due to it being
in
some
sort of debug mode or has the binary been stripped ?

please configure Qt for building "release" binaries (it looks
like
you're building the client in debug mode).
best regards,
Heinz

Thanks Heinz.
I have now compiled it as a release binary and it is a lot
smaller
now :) Still having the same problem though that when I launch
x2goclient it starts up vcxsrv, sshd and pulse okay; the x2go
status
screen changes to say Connecting and then it hangs :( What I
think
is happening is that vcxsrv is ignoring the display parameter
that
is passed to it. If I run xcalc -display localhost:0 that
works;
though if I try xcalc -display:6000 it fails. I am guessing
the
next
step should be the NX libraries etc starting. Any ideas ?

Hello,
0 - Display number
6000 - TCP port
TCP port = Display number + 6000
regards

Yep, but still not dice. It gets to the point of connecting and
then
just hangs. I can see all the necessary processes running and
obviously X is working okay. Will check from the server side and
see
if it is even attempting to start the session.

After watching the remote server the SSH session is not even being
attempted to be established :( I have even tried setting the working
directory back to being xming once vcxsrv has been started incase I
was corrupting a path further down the chain; though still no joy.
Any
ideas please ?

I am now compiling the x2goclient as a release version but look at the
C:\Program Files\x2goclient>dir x2goclient.exe
26/11/2009 10:11 4,915,200 x2goclient.exe
C:\Program Files\x2goclient>dir
c:\x2goclient-3.01\release\x2goclient.exe
10/11/2010 09:32 1,699,840 x2goclient.exe
The one I have compiled is half the size! Where is the
x2goclient.pro.windows file that is mentioned in README.WINDOWS as I
cannot find it ??

Would it be better for me to build the Windows client under Linux ? and if that is the case would somebody be able to provide a brief how-to ?

--
Thanks, Phil

--[ UxBoD ]--

2010-11-10 14:07:47 UTC

----- Original Message -----

Post by --[ UxBoD ]--
I am now compiling the x2goclient as a release version but look at
C:\Program Files\x2goclient>dir x2goclient.exe
26/11/2009 10:11 4,915,200 x2goclient.exe
C:\Program Files\x2goclient>dir
c:\x2goclient-3.01\release\x2goclient.exe
10/11/2010 09:32 1,699,840 x2goclient.exe
The one I have compiled is half the size! Where is the
x2goclient.pro.windows file that is mentioned in README.WINDOWS as I
cannot find it ??

I do not know the answer but I do remember there was a lengthy
discussion on the list about this that can probably be dug out of the
archives - John

I believe it is a red herring.

--[ UxBoD ]--

2010-11-11 13:12:17 UTC

----- Original Message -----

Post by --[ UxBoD ]--
----- Original Message -----

I do not know the answer but I do remember there was a lengthy
discussion on the list about this that can probably be dug out of
the
archives - John

I believe it is a red herring.

--[ UxBoD ]--

2010-11-12 09:10:21 UTC

----- Original Message -----

Post by --[ UxBoD ]--
----- Original Message -----

Post by --[ UxBoD ]--
I am now compiling the x2goclient as a release version but look
at
C:\Program Files\x2goclient>dir x2goclient.exe
26/11/2009 10:11 4,915,200 x2goclient.exe
C:\Program Files\x2goclient>dir
c:\x2goclient-3.01\release\x2goclient.exe
10/11/2010 09:32 1,699,840 x2goclient.exe
The one I have compiled is half the size! Where is the
x2goclient.pro.windows file that is mentioned in README.WINDOWS
as
I
cannot find it ??

I do not know the answer but I do remember there was a lengthy
discussion on the list about this that can probably be dug out of
the
archives - John

I believe it is a red herring.

--[ UxBoD ]--

2010-11-12 09:59:40 UTC

----- Original Message -----

Post by --[ UxBoD ]--
----- Original Message -----

Post by --[ UxBoD ]--
I am now compiling the x2goclient as a release version but
look
at
C:\Program Files\x2goclient>dir x2goclient.exe
26/11/2009 10:11 4,915,200 x2goclient.exe
C:\Program Files\x2goclient>dir
c:\x2goclient-3.01\release\x2goclient.exe
10/11/2010 09:32 1,699,840 x2goclient.exe
The one I have compiled is half the size! Where is the
x2goclient.pro.windows file that is mentioned in
README.WINDOWS
as
I
cannot find it ??

I do not know the answer but I do remember there was a lengthy
discussion on the list about this that can probably be dug out
of
the
archives - John

I believe it is a red herring.

--[ UxBoD ]--

2010-11-12 10:39:54 UTC

Yippee have built a cross compiled version of x2goclient by copying
libQtSvg4.a to libQtSvg.a on the Windows VM plus doing the same for
QtGui, QtNetwork and QtCore. Not sure why Windows and Linux are
different with their filenames.
I copied the resulting binary across to the Windows VM and fired it
up. That worked fine though once I entered my username and password
the client crashed and was intercepted by Qt debugger.
This is so so frustrating as every step forward that is taken is
countered by two back steps. Hopefully one of the developers will be
able to help as we are really running out of time to get a functional
X2Go client working. Mouse issues etc with Xming is causing us major
issues and we need to test with VCXSRV ASAP.

Have tried with 3.01-13 and the unstable branch each one crashes as soon as the username and password is entered :(

--
Thanks, Phil

Oleksandr Shneyder

2010-11-12 12:30:12 UTC

Post by --[ UxBoD ]--

Have tried with 3.01-13 and the unstable branch each one crashes as soon as the username and password is entered :(

Hallo Phil,
since version 3.01-4 there is no project file for windows. Linux,mac and
windows parts are merged in one "x2goclient.pro" file. We using Qt 4.5.3
configured to make static release binaries on lenny to perform
cross-platform builds of x2goclient. But with newer versions of qt on
windows x2goclient although is working without a problem, no matter what
you use to build x2goclient mingw or msvc. I think you have a problem,
that some binaries are missing in your installation. Please try to
install original x2goclient and try if it work. After that, replace
x2goclient with your binary. Please be sure that your binary works in
this installation before you make any changes in x2goclient code.

Happy hacking,
alex

--
Oleksandr Shneyder
Dipl. Informatik
X2go Core Developer Team

email: ***@obviously-nice.de
web: www.obviously-nice.de

--> X2go - ***@home

--[ UxBoD ]--

2010-11-12 12:46:33 UTC

----- Original Message -----

Post by Oleksandr Shneyder

Post by --[ UxBoD ]--

Yippee have built a cross compiled version of x2goclient by copying
libQtSvg4.a to libQtSvg.a on the Windows VM plus doing the same for
QtGui, QtNetwork and QtCore. Not sure why Windows and Linux are
different with their filenames.
I copied the resulting binary across to the Windows VM and fired it
up. That worked fine though once I entered my username and password
the client crashed and was intercepted by Qt debugger.
This is so so frustrating as every step forward that is taken is
countered by two back steps. Hopefully one of the developers will
be
able to help as we are really running out of time to get a
functional
X2Go client working. Mouse issues etc with Xming is causing us
major
issues and we need to test with VCXSRV ASAP.

Have tried with 3.01-13 and the unstable branch each one crashes as
soon as the username and password is entered :(

Hallo Phil,
since version 3.01-4 there is no project file for windows. Linux,mac
and
windows parts are merged in one "x2goclient.pro" file. We using Qt
4.5.3
configured to make static release binaries on lenny to perform
cross-platform builds of x2goclient. But with newer versions of qt on
windows x2goclient although is working without a problem, no matter
what
you use to build x2goclient mingw or msvc. I think you have a problem,
that some binaries are missing in your installation. Please try to
install original x2goclient and try if it work. After that, replace
x2goclient with your binary. Please be sure that your binary works in
this installation before you make any changes in x2goclient code.
Happy hacking,
alex

Hello Alex, really appreciate your response :) I have taken the Windows X2GO 3.01-11 and installed that on Windows XP 32 bit. I backed up x2goclient.exe and the proceeded to compile the same version of x2goclient using MinGW and Qt 4.7.1 (this could be where the problem is arising!) using the steps; qmake followed by mingw32-make release and that created the binary. I copied that to c:\program files\x2goclient and ran it. It started fine and I connected to my existing session, once I entered my username and password it then crashed. This happens the same with both build under Linux and Windows. Using QtCreator I did manage to get some kind of debug information which said:

Creating desktop: x2go_Administrator

ASSERT failure in QWidget: "Widgets must be created in the GUI thread.", file kernel\qwidget.cpp, line 1231
QObject::killTimers: timers cannot be stopped from another thread
C:\x2goclient-3.01\debug\x2goclient.exe exited with code 3

I will try downloading the same release of Qt that you are using. Just to be clear I am assuming that you export your Windows Qt install to your Linux box and then compile using those libraries ?

--
Thanks, Phil

Oleksandr Shneyder

2010-11-12 13:49:31 UTC

--[ UxBoD ]-- schrieb:

Hello Phil,

Post by --[ UxBoD ]--
Creating desktop: x2go_Administrator
ASSERT failure in QWidget: "Widgets must be created in the GUI thread.", file kernel\qwidget.cpp, line 1231
QObject::killTimers: timers cannot be stopped from another thread
C:\x2goclient-3.01\debug\x2goclient.exe exited with code 3

I think, a newest version of qt that I tried was a 4.6.x.

Post by --[ UxBoD ]--
I will try downloading the same release of Qt that you are using.

Just to be clear I am assuming that you export your Windows Qt install
to your Linux box and then compile using those libraries ?

Yes, I have compiled Qt libs on windows and then exported libraries as
SMB share. But building in windows environment is no problem although. I
make cross platform build only because it is simple and comfortable.

regards

--
Oleksandr Shneyder
Dipl. Informatik
X2go Core Developer Team

email: ***@obviously-nice.de
web: www.obviously-nice.de

--> X2go - ***@home

--[ UxBoD ]--

2010-11-12 16:19:56 UTC

----- Original Message -----

Post by Oleksandr Shneyder
Hello Phil,

Post by --[ UxBoD ]--
Hello Alex, really appreciate your response :) I have taken the
Windows X2GO 3.01-11 and installed that on Windows XP 32 bit. I
backed up x2goclient.exe and the proceeded to compile the same
version of x2goclient using MinGW and Qt 4.7.1 (this could be where
the problem is arising!) using the steps; qmake followed by
mingw32-make release and that created the binary. I copied that to
c:\program files\x2goclient and ran it. It started fine and I
connected to my existing session, once I entered my username and
password it then crashed. This happens the same with both build
under Linux and Windows. Using QtCreator I did manage to get some
Creating desktop: x2go_Administrator
ASSERT failure in QWidget: "Widgets must be created in the GUI
thread.", file kernel\qwidget.cpp, line 1231
QObject::killTimers: timers cannot be stopped from another thread
C:\x2goclient-3.01\debug\x2goclient.exe exited with code 3

I think, a newest version of qt that I tried was a 4.6.x.

Post by --[ UxBoD ]--
I will try downloading the same release of Qt that you are using.

Just to be clear I am assuming that you export your Windows Qt install
to your Linux box and then compile using those libraries ?
Yes, I have compiled Qt libs on windows and then exported libraries as
SMB share. But building in windows environment is no problem although.
I
make cross platform build only because it is simple and comfortable.
regards

Using Qt 4.5.3 was the magic formula and we now have a client built using VcxSrv.

Mike Gabriel

2010-11-21 17:59:09 UTC