| Trolltech Home | Qt-jambi-interest Home | Recent Threads | All Threads | Author | Date | |
| All threads index page 1 | |
Hi, I was wondering if Trolltech could make a QtJambi package that includes all the OS dependent libraries into each OS package or something to that effect. In this way, deployment for each supported OS can be made without having to download all the different OS packages just for to get at the required libs. How about it? Thanks. Raymond Martin
Raymond Martin wrote: > Hi, > > I was wondering if Trolltech could make a QtJambi package that includes all the OS > dependent libraries into each OS package or something to that effect. In this way, > deployment for each supported OS can be made without having to download all > the different OS packages just for to get at the required libs. > > How about it? Hi Raymond, Our thought currently was to have a set of libs: the qtjambi.jar containing the .class files and a qtjambi_[platform].jar containing the native libraries. You see this pattern in the webstart where we have qtjambi_linux.jar and qtjambi_win32.jar. The problem with providing one complete jar is the size... We'll have to have win32/64, linux32/64, freebsd, solaris, mac os x, etc... It'll easy be 500Mb. We're open for discussion on this topic thouch so please share your ideas. best regards, Gunnar
On Monday 05 March 2007 09:24, Gunnar Sletta wrote: > Raymond Martin wrote: > > I was wondering if Trolltech could make a QtJambi package that includes > > all the OS dependent libraries into each OS package or something to that > > effect. In this way, deployment for each supported OS can be made without > > having to download all the different OS packages just for to get at the > > required libs. > Our thought currently was to have a set of libs: the qtjambi.jar > containing the .class files and a qtjambi_[platform].jar containing the > native libraries. You see this pattern in the webstart where we have > qtjambi_linux.jar and qtjambi_win32.jar. The problem with providing one > complete jar is the size... We'll have to have win32/64, linux32/64, > freebsd, solaris, mac os x, etc... It'll easy be 500Mb. > > We're open for discussion on this topic thouch so please share your ideas. For installing via the web, it would be great if there is an option to split up the jars even more. Having separate XML, openGL, SVG and SQL jars from the main stuff means most apps have to download even less. All the webstart user has to do is write which modules his app will require. Though we might want to make a little nice app to generate such a file; IMOHO no user should ever have to write XML by hand, especially not if it means having to have lots of lines for different platforms etc. -- [ signature omitted ]
Attachment:
pgpFI6jiwmIEA.pgp
Description: PGP signature
Hi Gunnar, > Our thought currently was to have a set of libs: the qtjambi.jar > containing the .class files and a qtjambi_[platform].jar containing the > native libraries. You see this pattern in the webstart where we have > qtjambi_linux.jar and qtjambi_win32.jar. The problem with providing one > complete jar is the size... We'll have to have win32/64, linux32/64, > freebsd, solaris, mac os x, etc... It'll easy be 500Mb. > > We're open for discussion on this topic thouch so please share your ideas. Actually, I was just talking about the download packages for developers (.tar.gz, etc.), on each platform, but you are right to put the OS specifics into separate jars. As some else mentioned, this could all be broken up even more into jars/packages for XML, SQL, and so forth when deploying for each OS. This is already done on certain Linux distributions (e.g. Mandriva) with Qt. Perhaps it is better left to whatever third party is distributing it. Thanks, sounds good. Raymond