I agree totally on this. Why isn't it possible to use the excellent
dependency systems found in apt/rpm to make sure that the system
has the right version of the Qt libs installed when attempting to
install Jambi libs to ensure that one do not run into linking problems?
Really, such strange deployment issues really makes it tough to
tease open source developers into using Jambi. Having to compile and
distribute the whole Qt system each time you want do develop something
in Jambi makes it look really obscure to most developers.
Regards,
Helge Fredriksen
Erwin Mueller wrote:
On Tuesday 04 August 2009 20:54:16 Dusan Zatkovsky wrote:
But - original binary qtjambi distribution has a big benefit - you should
run your application on any computer if you bundle qt jars together with
your app, because that jars contains native c++ qt libs too. I know that it
is 'breaking' the package managment idea on most linux distros and using
much more disk/ram space, but sometimes it should be very useful ( mostly
when you want to run your apps on mixed environment [windows/linux] ).
It's not only breaking that, it's breaks also the used style of the desktop in
the system. For example my pre-compiled Qt Jambi use the very ugly Clearlooks
style but everything else on my desktop is using Oxygen. The designer can only
use Phase, Windows, Motif, CDE, Plastic and Clearlooks style, no Oxygen. On my
other laptop with Debian Sid, the pre-compiled Qt Jambi use CDE or Motif style
(don't sure with one).
Erwin.
_______________________________________________
Qt-jambi-interest mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
|
_______________________________________________
Qt-jambi-interest mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
