[X2go-dev] X2GO and SSH

--[ UxBoD ]-- uxbod at splatnix.net
Wed Dec 15 11:20:29 CET 2010


----- Original Message -----
> --[ UxBoD ]-- schrieb:
> > ----- Original Message -----
> >> --[ UxBoD ]-- schrieb:
> >>> ----- Original Message -----
> >>> Hi Alex,
> >>>
> >>> Thank you for the detailed steps. May I ask if you rebuilt Qt,
> >>> statically, under Windows or has all your work been performed
> >>> under
> >>> Linux ? I have tried both of those Qt versions and ran
> >>> configure.exe
> >>> -static -openssl -I<path_to_openssl_include>
> >>> -L<path_to_openssl_libs> and it failed to compile when running
> >>> mingw32-make sub-src.
> >>>
> >>> I must be doing something crazily wrong in the way I am rebuilding
> >>> Qt :(
> >> I'm configure and build Qt always under windows. My configuration
> >> options are:
> >>
> >> -release
> >> -static
> >> -openssl
> >> -qt-style-windowsxp
> >> -qt-style-windowsvista
> >>
> >> openssl installed under c:\Program Files\openssl
> >>
> >> regards,
> >
> > Hi Alex,
> >
> > I finally managed to build Qt! Now onto libssh in the latest
> > x2go-client. I am guess that I need to apply the diff and then build
> > it ? Do you perform the compile under Cygwin or use MinGW32 ?
> 
> 
> Hello,
> 
> As I wrote in my last e-mail, the changes you need for x2goclient are
> already in master branch of libssh. You can build it on your system
> using mingw shipped with Qt SDK (need cmake, libssl and zlib) or get
> ready for use build from us:
> 
> http://x2go.obviously-nice.de/deb/libssh/libssh-x2go.zip
> 
Good morning, Alex

I downloaded the zip file and expanded it into the directory where the x2go client source is.  I then ran qmake followed by mingw32-make release and it failed to find the lib ssh include files. It would appear they are actually in libssh/include/libssh so I copied them all upto the top directory. It got a bit further with compilation but now fails trying to find the ssh library. What am I doing so wrong Alex. This appears to be such a complicated compiled task; and I guess it is due to not having certain paths defined somewhere.
-- 
Thanks, Phil



More information about the x2go-dev mailing list