Qt Jambi 4.5.0 will soon be released (after Qt 4.5.0 has been released), a preview is already available under [1]. [1] http://www.qtsoftware.com/about/news/preview-of-final-qt-jambi-release-available Reproducible: Always
Created attachment 183594 [details] An initial ebuild for the preview of Qt Jambi 4.5.0
Created attachment 183595 [details] The generator-patch for Qt Jambi 4.5.0 Preview
Created attachment 183596 [details, diff] The generator-patch for Qt Jambi 4.5.0 Preview
Created attachment 183598 [details] The configuration-patch for Qt Jambi 4.5.0 Preview
Thanks for the submission. Maybe you can try getting that configuration patch upstream before the final release.
OK, i will try that. Unfortunately I just discovered that the +phonon use-flag leads to a compilation error. Will try to fix this issue first.
Examined the problem and it only occurs if the 'examples' and 'phonon' use-flag are enabled at the same time. File a separate bug for this: #260803.
Why do you skip the 'library.native.bundle' ant target?
Created attachment 188928 [details] updated to install jambi-designer ebuild now creates the designer library, and installs the designer plugins correctly. Also made changes to compile with distcc. Requires updated configuration patch
Created attachment 188929 [details, diff] updated configuration patch
(In reply to comment #9) > Created an attachment (id=188928) [edit] > updated to install jambi-designer > > ebuild now creates the designer library, and installs the designer plugins > correctly. Also made changes to compile with distcc. Requires updated > configuration patch > Kyle, could you please attach a diff against the current ebuild in portage instead of the whole updated ebuild? It makes reviewing easier. Thanks.
Created attachment 188940 [details, diff] diff against 4.4.3 in tree
(In reply to comment #8) > Why do you skip the 'library.native.bundle' ant target? > I think this is fine for most cases, because the /usr/lib qt files will be resolved instead of unpacked from a bundle. It may be nice to make an option for this, but it seems to make sense only if you intend to distribute the bundle (to the same arch). Otherwise, it just seems like a waste of space. In order to run your application with the native files, use the following: java -jar -Djava.library.path=/usr/lib/qtjambi-4:/usr/lib/qt4 yourjar.jar
Just a quick note: shouldn't get_libdir() used when generating the start script too? And "generator" is a little too generic for a binary IMHO, it may easily cause collisions... maybe we should install it as "jambi-generator"?
Created attachment 188947 [details, diff] updated per comment #14
How is jambi-designer supposed to be different from the regular Qt designer? I suspect the designer plugins installed by qtjambi fail to load on my box...
Created attachment 189574 [details] improved ebuild for qtjambi-4.5.0_pre1 Much-reworked (EAPI-2) ebuild. Due to the extensive changes, the diff was unreadable, so I'm attaching the whole ebuild. Works fine here except that the native libraries are built for every Qt library present on the system when emerging, thus the ebuild doesn't respect USE flags. I know where the problem is (java.pro uses QT_CONFIG to determine what must be compiled), I just need to find the best/simplest way to fix it. 'examples' and 'doc' USE flags *not* tested.
Created attachment 189576 [details, diff] configuration-4.5.0_pre1.patch
Created attachment 189577 [details, diff] generator-4.5.0_pre1.patch
(In reply to comment #16) > How is jambi-designer supposed to be different from the regular Qt designer? > I suspect the designer plugins installed by qtjambi fail to load on my box... > jambi-designer outputs a different type of file than regular designer (*.jui). That is pretty much the only indicator that it is working correctly.
(In reply to comment #20) > (In reply to comment #16) > > How is jambi-designer supposed to be different from the regular Qt designer? > > I suspect the designer plugins installed by qtjambi fail to load on my box... > > > > jambi-designer outputs a different type of file than regular designer (*.jui). > That is pretty much the only indicator that it is working correctly. > Ok, then it's working correctly :)
Created attachment 190031 [details, diff] configuration-4.5.0_pre1.patch
Created attachment 190038 [details] qtjambi-4.5.0_pre1.ebuild So, I've chosen to use eqmake4 to fix the problem mentioned in comment #17. This ebuild should be in a pretty good shape now :-) P.S.: I removed the sqlite USE flag because the dependency on x11-libs/qt-sql is _not_ considered optional by upstream, qtjambi won't compile without it!
Looks pretty good. One thing I caught a couple days ago: the examples get installed with 755 permissions! I'll post a fix if you don't beat me to it.
(In reply to comment #24) > Looks pretty good. One thing I caught a couple days ago: the examples get > installed with 755 permissions! I'll post a fix if you don't beat me to it. > Mmmm... it seems that java-pkg_doexamples (from java-utils-2.eclass) doesn't reset the permissions before calling doins... I wonder if it's a feature or a bug...
Native libraries in /usr/$(get_libdir)/qtjambi-4 are also installed with wrong permissions (because of bug #225729).
Created attachment 190214 [details, diff] updated to clean up the examples
Created attachment 190215 [details, diff] cleans up examples, and installs ant tasks for qtjambi. This patch installs the ant-qtjambi.jar file that trolltech thinks developers should have. It also gets rid of class files in the examples directory, since they get bundled already. The latest portage fixes the permissions issue for java-pkg_doexamples.
QtJambi 4.5.0_01 (final) is out. Kyle, have you tried building qtjambi (final or _pre1, it shouldn't matter) with USE="examples phonon" (using x11-libs/qt-phonon)?
(In reply to comment #29) > QtJambi 4.5.0_01 (final) is out. > > Kyle, have you tried building qtjambi (final or _pre1, it shouldn't matter) > with USE="examples phonon" (using x11-libs/qt-phonon)? > Just tried and failed. I'll work on it.
It failed for me too, but I'm using media-sound/phonon, not x11-libs/qt-phonon. With media-sound/phonon, the generator doesn't generate anything for the phonon module and the libcom_trolltech_qt_phonon.so.1.0.0 native library is just bogus... I think bug #260805 is invalid, or at least it doesn't apply to 4.5.0.
(In reply to comment #30) > (In reply to comment #29) > > QtJambi 4.5.0_01 (final) is out. > > > > Kyle, have you tried building qtjambi (final or _pre1, it shouldn't matter) > > with USE="examples phonon" (using x11-libs/qt-phonon)? > > > > Just tried and failed. I'll work on it. > Interestingly, phonon is not packaged in 4.5.0_01. Only the demos are present. 4.4.3 seems to lack the libraries as well. It looks like 4.4.0_01 is the only version with phonon.
Weird. What's missing exactly?
(In reply to comment #33) > Weird. What's missing exactly? > I think I spoke too soon. I think the generator is responsible for creating the sources. I'll have to look deeper...
(In reply to comment #34) > I think I spoke too soon. I think the generator is responsible for creating the > sources. I'll have to look deeper... > Indeed. Could you please check that the sources are generated and the native library is not bogus? (e.g. run scanelf -qn on lib/libcom_trolltech_qt_phonon.so.1.0.0) Thanks.
Created attachment 191328 [details, diff] configuration-4.5.0_p1.patch
Created attachment 191329 [details, diff] generator-4.5.0_p1.patch
Created attachment 191330 [details] qtjambi-4.5.0_p1.ebuild
I added qtjambi-4.5.0_p1 to the qting-edge overlay.
qtjambi-4.5.0_p1 is in tree now.
