![]() Registered Member ![]()
|
I'm trying to compile and install QtJambi on Arch Linux + KDEMod, but it keeps failing when it attempts to find Qt's Phonon plugin; since KDE is my desktop environment of choice, my version of Qt was compiled without the phonon plugin so I may use KDE's.
Has anybody successfully gotten QtJambi to compile? I need it for several projects of mine (many of which are KDE related). Edit: Here is the specific error message it is giving me:
Last edited by deltaecho on Sat Oct 18, 2008 7:46 am, edited 1 time in total.
"Many of life's failures are people who did not realize how close they were to success when they gave up."
Thomas Edison |
![]() Registered Member ![]()
|
OK, so I've hacked on it a little and learned a bit, however, now receive this error:
I will keep playing with it, but in the meantime, can anybody help me with these?
"Many of life's failures are people who did not realize how close they were to success when they gave up."
Thomas Edison |
![]() Registered Member ![]()
|
For now, I've given up on compiling my own version of QtJambi :P
What I've decided to do is unpack its binary to /opt/qtjambi, and symlink its various libraries to the locations I would have placed them had I compiled it. This seems to be the best solution for now, because Eclipse's QtJambi plugin will not work with system-compiled libraries, only the binaries supplied by Qt. If you're running Arch Linux, here is my PKGBUILD and here is the link to its AUR page. If you have any suggestions on how I can improve it, let me know (the build() method is written in BASH). For those interested in helping me figure out how to get the bugger to compile, here are the steps I've already taken:
I hope that helps somebody ... NOTE: For 64-bit users, QtJambi's Eclipse plugin will not work, but you can work around this by including QtJambi's *.jar's in your project's build path ("Project -> Properties -> Java Build Path -> Libraries tab -> Add External Jars"). You won't have access to the nice QtDesigner interface from Eclipse, but you can have it opened separately and work on the UI while dealing with the coding part in Eclipse.
"Many of life's failures are people who did not realize how close they were to success when they gave up."
Thomas Edison |
Registered users: Bing [Bot], Evergrowing, Google [Bot], rblackwell