On Tuesday 04 August 2009 20:27:01 Eskil Abrahamsen Blomfeldt wrote: > Erwin Mueller wrote: > > How should I then deploy the finished application on the end user system? > > Should I compile Qt Jambi with all possible Qt-styles (Oxygen, Phase, > > Plastic, Cleanlooks, etc) and deploy it the Qt Jambi way? I can't ask the > > user to compile Qt Jambi against his Qt4 system libraries, can I? > > Hi, Erwin. > > As I see it, there are three ways of doing this. You either have to > bundle the binaries that you plan to use, or the Linux distribution will > have to distribute Qt Jambi as a prebuilt package which is guaranteed to > work with the other libraries on the system. The third way is to check > how the Qt versions are configured on the different Linux distributions. > You might get away with building Qt Jambi against a Qt version which has > a typical build configuration, and then distributing this with your > application. That would probably give you compatibility on at least a > great part of the Linux distributions out there. > > > If I ask the user to compile Qt Jambi against his Qt4 system libraries, > > then the user need first to install all necessary -dev packages? > > Yes, anything required to build Qt Jambi will have to be installed on > the platform where you plan to build the package. > > -- Eskil
I see, thank you very much. So I think the 'Linux-way' would be to build the deb and the rpm packages for Qt Jambi for each distribution I like to support. For that I need to compile Qt Jambi against each version of Qt. For example, one for Ubuntu against Qt-Libs-Ubuntu, one for Debian against Qt-Libs-Debian, one for Fedora against Qt-Libs-Fedora, and so on. Of course it would be much easier if there were packages for the distributions in it's repositories already, but I guess Qt Jambi is not so widely used. Thank you again, Erwin. _______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
