 |
Forums |
Admin  Start New Thread
By: Vincent Fourmond
 RE: Qt4 smoke conflicts with Qt3 [ reply ]
2006-10-16 18:55
|
|
Great. I've worked on a thing of my own for the librairies, but I didn't give a think about the Ruby library. I'll integrate this as soon as possible (but I'd like the current version - 1.4.6 to go into the archive first). Cheers !
|
By: Richard Dale
RE: Qt4 smoke conflicts with Qt3 [ reply ]
2006-10-14 11:52
|
The smoke libs, and qtruby extensions now use different names/versions, and so they can be installed at the same time. After you've installed qt4 qtruby on top of qt3 qtruby, you can do either:
require 'Qt3'
require 'Qt4'
according to which one you want to use.
require 'Qt'
will default to the qt4 version. But if you install the qt3 version of qtruby after the qt4 one, require 'Qt' will default to the qt3 version again.
The qt4 version of the rbuic tool has been renamed 'rbuic4', and the tool to introspect to smoke library is called 'rbqt3api', 'rbqt4api' with the default 'rbqtapi' using qt4 qtruby.
|
By: Vincent Fourmond
RE: Qt4 smoke conflicts with Qt3 [ reply ]
2006-06-14 18:23
|
Actually, I simply did
perl -pi 's/smokeqt/smokeqt4/g' **/*
in my directory tree, and everything went fine. This transforms all the occurences of smokeqt in all the files into smokeqt4.
It then builds, installs and runs fine.
|
By: Vincent Fourmond
RE: Qt4 smoke conflicts with Qt3 [ reply ]
2006-05-04 19:43
|
Well, no: as you can see, both version provide the libsmokeqt.so.1 symlink, and ld and the dynamic linker is linking only to this. The 2.3 subversion information is not used at run-time (at least under linux, as far as I can understand).
To prevent any clash, wouldn't it be safer to rename the library to libsmokeqt4 ? If you're interested, I can try and make a patch to do that. It shouldn't break anything.
(anyway, I'll work on the patch for myself, because I need to have both at the same time)
|
By: Richard Dale
RE: Qt4 smoke conflicts with Qt3 [ reply ]
2006-05-04 09:54
|
I did up the version of the smoke library for Qt4:
baldhead duke 502% ls /opt/kde4/lib/*smoke*
/opt/kde4/lib/libsmokeqt.la /opt/kde4/lib/libsmokeqt.so.1
/opt/kde4/lib/libsmokeqt.so /opt/kde4/lib/libsmokeqt.so.1.2.3
baldhead duke 504% ls /usr/lib/*smokeqt*
/usr/lib/libsmokeqt.la /usr/lib/libsmokeqt.so.1
/usr/lib/libsmokeqt.so /usr/lib/libsmokeqt.so.1.2.2
So it's my understanding that you should be able to link against the 1.2.2 version for Qt3, and the latest 1.2.3 version for Qt4.
But the QtRuby extension needs to be a gem, which does have a versioning system before it will really be possible to run both Qt3 and Qt4 versions at the same time. The project really does need binary gems as it's so hard to build on Windows and Mac OS X at the moment.
|
By: Vincent Fourmond
Qt4 smoke conflicts with Qt3 [ reply ]
2006-04-26 14:14
|
I find that the Qt4 extension is great. However, I find that it is a real pity that it is not easy to have both Qt3 and Qt4 extensions at the same time:
* for one, the binary extension's name is only Qt. No way to select the version wanted;
* but, more important: the smoke library for Qt4 has the same name than the one for Qt3. This is quite nasty, as I can't use Qt4 for Ruby and have my old Perl::Qt(3) programs running.
I could hack my way out of this problem, but I think a decision should be taken to avoid conflicts, as this will make further distribution (Red Hat, Debian, and so on...) really difficult.
What do you think about it ?
|
|
|
