----- Original Message -----
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
On Tue, 2010-11-09 at 15:45 +0000, --[ UxBoD ]-- wrote:
----- Original Message -----
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 ?
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
On 11/09/2010 11:17 AM, John A. Sullivan III wrote:
On Tue, 2010-11-09 at 15:45 +0000, --[ UxBoD ]-- wrote:
----- Original Message -----
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 ?
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
Hello,
Am 09.11.2010 16:45, schrieb --[ 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
----- Original Message -----
Hello,
Am 09.11.2010 16:45, schrieb --[ 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
--[ UxBoD ]-- schrieb:
----- Original Message -----
Hello,
----- 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 ?
Am 09.11.2010 16:45, schrieb --[ UxBoD ]--: 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: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
----- Original Message -----
--[ UxBoD ]-- schrieb:
----- Original Message -----
Hello,
----- 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 ?
Am 09.11.2010 16:45, schrieb --[ UxBoD ]--: 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
----- Original Message -----
----- Original Message -----
--[ UxBoD ]-- schrieb:
----- Original Message -----
Hello,
----- 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 ?
Am 09.11.2010 16:45, schrieb --[ UxBoD ]--: 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
----- Original Message -----
----- Original Message -----
----- Original Message -----
--[ UxBoD ]-- schrieb:
----- Original Message -----
Hello,
----- 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 ?
Am 09.11.2010 16:45, schrieb --[ UxBoD ]--: 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
----- Original Message -----
----- Original Message -----
----- Original Message -----
----- Original Message -----
--[ UxBoD ]-- schrieb:
----- Original Message -----
Hello,
Am 09.11.2010 16:45, schrieb --[ 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 ??
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
On Wed, 2010-11-10 at 10:02 +0000, --[ UxBoD ]-- wrote: <snip>
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 ??
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
----- Original Message -----
On Wed, 2010-11-10 at 10:02 +0000, --[ UxBoD ]-- wrote: <snip>
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 ??
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. From a prior conversation it would appear the preferred development environment is Linux; even for the Windows package. A prior post has asked for help on what needs to be done to create that environment. Interestingly I have downloaded every release from version 3.01-4 and none of them work when I compile under Windows. I am wondering now what version of QT the devs are compiling against as I am using the latest SDK from Trolltech.
Thanks, Phil
----- Original Message -----
----- Original Message -----
On Wed, 2010-11-10 at 10:02 +0000, --[ UxBoD ]-- wrote: <snip>
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 ??
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. From a prior conversation it would appear the preferred development environment is Linux; even for the Windows package. A prior post has asked for help on what needs to be done to create that environment. Interestingly I have downloaded every release from version 3.01-4 and none of them work when I compile under Windows. I am wondering now what version of QT the devs are compiling against as I am using the latest SDK from Trolltech.
For reference have given up on trying to get X2goclient working under Windows when compiling from source. Using the Trolltech SDK with the included MinGW the client compiles cleanly but once you run it, enter your username and password, it then crashes and asks to be debugged.
One step forward though is that I know what changes need to be made to use VCXSRV so will now try and build a Linux x-compilation environment.
I am open to offers of help with this :)
Thanks, Phil
----- Original Message -----
----- Original Message -----
----- Original Message -----
On Wed, 2010-11-10 at 10:02 +0000, --[ UxBoD ]-- wrote: <snip>
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 ??
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. From a prior conversation it would appear the preferred development environment is Linux; even for the Windows package. A prior post has asked for help on what needs to be done to create that environment. Interestingly I have downloaded every release from version 3.01-4 and none of them work when I compile under Windows. I am wondering now what version of QT the devs are compiling against as I am using the latest SDK from Trolltech.
For reference have given up on trying to get X2goclient working under Windows when compiling from source. Using the Trolltech SDK with the included MinGW the client compiles cleanly but once you run it, enter your username and password, it then crashes and asks to be debugged.
One step forward though is that I know what changes need to be made to use VCXSRV so will now try and build a Linux x-compilation environment.
I am open to offers of help with this :)
I believe I have setup my Linux cross-compiler environment okay but when I tried and build x2goclient I receive the following error:
make[1]: Entering directory `/home/uxbod/compile/x2goclient-3.01' /home/uxbod/compile/mingw/bin/i586-mingw32-g++ -mthreads -Wl,-enable-stdcall-fixup -Wl,-enable-auto-import -Wl,-enable-runtime-pseudo-reloc -mwindows -Wl,-s -Wl,-subsystem,windows -o release/x2goclient.exe object_script.x2goclient.Release -L'/mnt/windows/C/Qt/qt/lib' -lmingw32 -lqtmain release/x2goclient -lwinspool -lQtSvg -lQtGui -lQtNetwork -lQtCore /home/uxbod/compile/mingw/lib/gcc/i586-mingw32/3.4.5/../../../../i586-mingw32/bin/ld: cannot find -lQtSvg collect2: ld returned 1 exit status
I have mounted the Qt directory from my Windows virtual machine and created a new Qt build spec called win32-x-g++ which contains:
# # qmake configuration for win32-x-g++ # # Written for MinGW #
MAKEFILE_GENERATOR = MINGW TEMPLATE = app CONFIG += qt warn_on release link_prl copy_dir_files debug_and_release debug_and_release_target QT += core gui DEFINES += UNICODE QT_LARGEFILE_SUPPORT QMAKE_COMPILER_DEFINES += __GNUC__ WIN32
QMAKE_CC = gcc QMAKE_LEX = flex QMAKE_LEXFLAGS = QMAKE_YACC = byacc QMAKE_YACCFLAGS = -d QMAKE_CFLAGS = QMAKE_CFLAGS_DEPS = -M QMAKE_CFLAGS_WARN_ON = -Wall QMAKE_CFLAGS_WARN_OFF = -w QMAKE_CFLAGS_RELEASE = -O2 QMAKE_CFLAGS_DEBUG = -g QMAKE_CFLAGS_YACC = -Wno-unused -Wno-parentheses QMAKE_CFLAGS_THREAD = -mthreads
QMAKE_CXX = /home/uxbod/compile/mingw/bin/i586-mingw32-g++ QMAKE_CXXFLAGS = $$QMAKE_CFLAGS QMAKE_CXXFLAGS_DEPS = $$QMAKE_CFLAGS_DEPS QMAKE_CXXFLAGS_WARN_ON = $$QMAKE_CFLAGS_WARN_ON QMAKE_CXXFLAGS_WARN_OFF = $$QMAKE_CFLAGS_WARN_OFF QMAKE_CXXFLAGS_RELEASE = $$QMAKE_CFLAGS_RELEASE QMAKE_CXXFLAGS_DEBUG = $$QMAKE_CFLAGS_DEBUG QMAKE_CXXFLAGS_YACC = $$QMAKE_CFLAGS_YACC QMAKE_CXXFLAGS_THREAD = $$QMAKE_CFLAGS_THREAD QMAKE_CXXFLAGS_RTTI_ON = -frtti QMAKE_CXXFLAGS_RTTI_OFF = -fno-rtti QMAKE_CXXFLAGS_EXCEPTIONS_ON = -fexceptions QMAKE_CXXFLAGS_EXCEPTIONS_OFF = -fno-exceptions
QMAKE_INCDIR = /home/uxbod/compile/mingw/include QMAKE_INCDIR_QT = /mnt/windows/C/Qt/qt/include QMAKE_LIBDIR_QT = /mnt/windows/C/Qt/qt/lib
QMAKE_RUN_CC = $(CC) -c $(CFLAGS) $(INCPATH) -o $obj $src QMAKE_RUN_CC_IMP = $(CC) -c $(CFLAGS) $(INCPATH) -o $@ $< QMAKE_RUN_CXX = $(CXX) -c $(CXXFLAGS) $(INCPATH) -o $obj $src QMAKE_RUN_CXX_IMP = $(CXX) -c $(CXXFLAGS) $(INCPATH) -o $@ $<
QMAKE_LINK = /home/uxbod/compile/mingw/bin/i586-mingw32-g++ QMAKE_LFLAGS = -mthreads -Wl,-enable-stdcall-fixup -Wl,-enable-auto-import -Wl,-enable-runtime-pseudo-reloc -mwindows QMAKE_LFLAGS_RELEASE = -Wl,-s QMAKE_LFLAGS_DEBUG = QMAKE_LFLAGS_CONSOLE = -Wl,-subsystem,console QMAKE_LFLAGS_WINDOWS = -Wl,-subsystem,windows QMAKE_LFLAGS_DLL = -shared QMAKE_LINK_OBJECT_MAX = 10 QMAKE_LINK_OBJECT_SCRIPT= object_script
QMAKE_LIBS = QMAKE_LIBS_CORE = -lkernel32 -luser32 -lshell32 -luuid -lole32 -ladvapi32 -lws2_32 #QMAKE_LIBS_CORE = -lkernel32 -luser32 -luuid -lole32 -ladvapi32 -lws2_32 QMAKE_LIBS_GUI = -lgdi32 -lcomdlg32 -loleaut32 -limm32 -lwinmm -lwinspool -lws2_32 -lole32 -luuid -luser32 QMAKE_LIBS_NETWORK = -lws2_32 QMAKE_LIBS_OPENGL = -lopengl32 -lglu32 -lgdi32 -luser32 QMAKE_LIBS_COMPAT = -ladvapi32 -lshell32 -lcomdlg32 -luser32 -lgdi32 -lws2_32 QMAKE_LIBS_QT_ENTRY = -lmingw32 -lqtmain
MINGW_IN_SHELL = $$(MINGW_IN_SHELL) #isEqual(MINGW_IN_SHELL, 1) { QMAKE_DIR_SEP = / QMAKE_COPY = cp QMAKE_COPY_DIR = cp -r QMAKE_MOVE = mv QMAKE_DEL_FILE = rm -f QMAKE_MKDIR = mkdir -p QMAKE_DEL_DIR = rm -rf #} else { # QMAKE_COPY = copy /y # QMAKE_COPY_DIR = xcopy /s /q /y /i # QMAKE_MOVE = move # QMAKE_DEL_FILE = del # QMAKE_MKDIR = mkdir # QMAKE_DEL_DIR = rmdir #} QMAKE_MOC = $$[QT_INSTALL_BINS]$${DIR_SEPARATOR}moc QMAKE_UIC = $$[QT_INSTALL_BINS]$${DIR_SEPARATOR}uic QMAKE_IDC = $$[QT_INSTALL_BINS]$${DIR_SEPARATOR}idc
QMAKE_IDL = midl QMAKE_LIB = ar -ru QMAKE_RC = /home/uxbod/compile/mingw/bin/i586-mingw32-windres
QMAKE_ZIP = zip -r -9
QMAKE_STRIP = strip QMAKE_STRIPFLAGS_LIB += --strip-unneeded QMAKE_CHK_DIR_EXISTS = if not exist load(qt_config)
All the paths look okay for which I am very puzzled why I am receiving a linker error. Any thoughts ? and perhaps you could post your qmake.conf ?
Thanks, Phil
----- Original Message -----
----- Original Message -----
----- Original Message -----
----- Original Message -----
On Wed, 2010-11-10 at 10:02 +0000, --[ UxBoD ]-- wrote: <snip>
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 ??
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. From a prior conversation it would appear the preferred development environment is Linux; even for the Windows package. A prior post has asked for help on what needs to be done to create that environment. Interestingly I have downloaded every release from version 3.01-4 and none of them work when I compile under Windows. I am wondering now what version of QT the devs are compiling against as I am using the latest SDK from Trolltech.
For reference have given up on trying to get X2goclient working under Windows when compiling from source. Using the Trolltech SDK with the included MinGW the client compiles cleanly but once you run it, enter your username and password, it then crashes and asks to be debugged.
One step forward though is that I know what changes need to be made to use VCXSRV so will now try and build a Linux x-compilation environment.
I am open to offers of help with this :)
I believe I have setup my Linux cross-compiler environment okay but when I tried and build x2goclient I receive the following error:
make[1]: Entering directory `/home/uxbod/compile/x2goclient-3.01' /home/uxbod/compile/mingw/bin/i586-mingw32-g++ -mthreads -Wl,-enable-stdcall-fixup -Wl,-enable-auto-import -Wl,-enable-runtime-pseudo-reloc -mwindows -Wl,-s -Wl,-subsystem,windows -o release/x2goclient.exe object_script.x2goclient.Release -L'/mnt/windows/C/Qt/qt/lib' -lmingw32 -lqtmain release/x2goclient -lwinspool -lQtSvg -lQtGui -lQtNetwork -lQtCore /home/uxbod/compile/mingw/lib/gcc/i586-mingw32/3.4.5/../../../../i586-mingw32/bin/ld: cannot find -lQtSvg collect2: ld returned 1 exit status
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.
Thanks, Phil
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
--[ UxBoD ]-- schrieb:
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
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
----- Original Message -----
--[ UxBoD ]-- schrieb:
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
--[ UxBoD ]-- schrieb:
Hello Phil,
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 think, a newest version of qt that I tried was a 4.6.x.
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: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
----- Original Message -----
--[ UxBoD ]-- schrieb:
Hello Phil,
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 think, a newest version of qt that I tried was a 4.6.x.
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. From my testing performance appears to be pretty comparable with Xming. Does the unstable branch of x2goclient have the code in for windows clipboard ? Then will be the next thing we wish to get working. Oh,have tested full screen mode with vcxsrv though have found it throws it to the foreground and obscures the x2go window. Do you know of a way with QProcess to minimize the forked process ?
Thanks, Phil
-
--[ UxBoD ]-- -
Gerry Reno -
Heinz-M. Graesing -
John A. Sullivan III -
Oleksandr Shneyder