Kurt Pfeifle wrote:my own idea about klik is to use it primarily as a very efficient tool to help experienced users to testdrive development versions of KDE packages without them needing to compile themselvs, and without the distro packages needing to provide weekly snapshot RPMs and .debs (which they don't do, anyways).
Can I autopackage KDE/Qt apps?
It's possible but hard, because the C++ ABI is not stable. It was supposd to be, but then gcc 3.4 broke it yet again. Until we have a stable C++ ABI on Linux distributing binaries that link against anything other than the standard library is a bad idea. GTKmm apps are OK because you can statically link GTKmm and not suffer too badly, but Qt/KDE cannot be statically linked in a sensible fashion. We want better support for KDE apps in autopackage and know how to do it, but need somebody to step up and do the necessary legwork.
Rhakios wrote:So, does this mean we'll be seeing autopackage files on the cover discs in future Mike?
Nigel wrote:Given the amount of memory and the processor speed on modern machines, what's so wrong with statically linked binaries ? At least that way you don't end up in dependancy hell...
Users browsing this forum: Google [Bot] and 1 guest