----- Original Message -----
On Wed, 2010-12-15 at 11:32 +0100, Oleksandr Shneyder wrote:
--[ UxBoD ]-- schrieb:
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.
Hello,
It is not complicate at all. Please read careful my Howto and you'll see, that it's very simple:
From Re: [X2go-dev] X2GO and SSH 09.12.2010 17:44 by Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de>
==============================
unpack this file and install libssh in mingw directory which shipped with Qt SDK.
include/libssh/* -> mingw/include/libssh/ lib/libssh.dll.a -> mingw/lib/
you must provide libssh.dll and zlib1.dll with your build of x2goclient
<snip> Thanks, Oleksandr but I'm a little confused by the above statement. If we are doing static linking, why do we need to distribute libssh.dll and zlib1.dll?
By the way, we have it working now but are just trying to tweak it, e.g., to statically link all libraries so we have a single executable. For example, just as you describe, despite specifying static linking, we seem to need dlls for not only ssh but also openssl. Thanks - John
Really ? Once I had compiled Qt with the static option it did not list any other DLLs when running through DependancyWalker ?
Thanks, Phil