> Eskil Abrahamsen Blomfeldt wrote: > > Helge Fredriksen wrote: > >> 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.
This is true, I absolutely agree with you. But when you want to use your jambi application on different operating systems, some of them has primitive package and dependency management ( for example windows with no application dependency tracking at all ), you've a trouble. How you should guarantee, that your .jar will work on debian, fedora, winxp? This is a big failure of Java world, I think, because I can't find satisfactory solution how to track jar dependencies. > > maintainers of the Linux distributions would make Qt Jambi packages on > > their systems, as they have done with Qt, which would have made > > deployment on Linux a lot easier. I see that ubuntu for example has some jambi packages. But as I said, I think that they have modified compile flags of qtc++ too in deb-srcs to successfully build jambi on ubuntu. Maybe I should help with this, creating a deb package is not a hard work. Much harder work is to make that package 'official'. I think that debian should try to backoport ubuntu's packages. I don't know the current status of rpm distros. > > For us, this is made more difficult by the fact that a fair share of > > Linux distributions have Qt 4 pre-installed to support KDE 4, and by > > the fact that Qt Jambi requires certain build flags to be set to work > > around bugs in the JVM, which makes it binary incompatible with the > > standard installation of Qt. Could you explain it shortly, please? What kind of jvm bugs? BR -- Dusan _______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
