* The packages should now build with Qt 3.1.x and above, and KDE 3.1.x and
above for Korundum.
* Added a qui extension for loading a Qt Designer .ui file at runtime via
QWidgetFactory
* For example:
require 'Qt'
require 'qui'
a = Qt::Application.new ARGV
if ARGV.length == 0
exit
end
if ARGV.length == 2
QUI::WidgetFactory.loadImages ARGV[0]
w = QUI::WidgetFactory.create ARGV[1]
if w.nil?
exit
end
w.show
a.connect( a, SIGNAL('lastWindowClosed()'), a, SLOT('quit()') )
a.exec
end
I just tried to compile korundum, but unfortunately make fails (log
attached).
Hmm, it couldn't find the libkmdi library. One of the changes I made to the
latest version of korundum was to look for that library as part of the
package configuration. It was only added in KDE 3.2, and so to build on KDE
3.1 there needs to be a check for whether the library is there and not add
a '-lkmdi' link option if it's missing.
As a work round you can edit korundum-cvs/smoke/kde/Makefile.am, and change
$(LIB_KMDI) to -lkmdi. I wonder why the test doesn't work. Towards the end
of the configure you should see a line like this, and in your case I assume
the result was 'no':
checking whether to use kmdi lib from kdelibs... yes
As a work round you can edit korundum-cvs/smoke/kde/Makefile.am, and
change $(LIB_KMDI) to -lkmdi. I wonder why the test doesn't work. Towards
the end of the configure you should see a line like this, and in your case
I assume the result was 'no':
checking whether to use kmdi lib from kdelibs... yes
I guess I found something in config.log (attached), maybe this is what
you're looking for.
It seems to work fine. Unfortunately, the second chapter of the tutorial
contains a broken link to Signals and Slots documentation.
OK - I've fixed that and a few other broken links. The Signals and Slots
documentation isn't ruby specific, it's just the standard C++ on
Trolltech's site.
My fault. Somehow /usr/kde/3.2/bin was in my PATH and /usr/kde/3.3/bin not,
so the older version of kde-config was used. I fixed it but now there's a
new problem (log attached).
My fault. Somehow /usr/kde/3.2/bin was in my PATH and /usr/kde/3.3/bin
not, so the older version of kde-config was used. I fixed it but now
there's a new problem (log attached).
I'll keep my fingers crossed that the new libkmdi check is working ok then..
Thunfisch
I think what's happened is that the Smoke library has been generated from
the KDE 3.2 headers, but you're compiling it against KDE 3.3. I had a look
on my KDE 3.1 machine, and KCatalogue::setFileName() did used to be public,
but on 3.3 it's private. So you need to remove the generated .cpp files
from korundum-cvs/smoke/kde (ie smokedata.cpp, x_1.cpp to x_20.cpp), and
then make again to regenerate Smoke. A 'make clean' command doesn't remove
those sources, but it should do.
I think what's happened is that the Smoke library has been generated from
the KDE 3.2 headers, but you're compiling it against KDE 3.3. I had a look
on my KDE 3.1 machine, and KCatalogue::setFileName() did used to be
public, but on 3.3 it's private. So you need to remove the generated .cpp
files from korundum-cvs/smoke/kde (ie smokedata.cpp, x_1.cpp to x_20.cpp),
and then make again to regenerate Smoke. A 'make clean' command doesn't
remove those sources, but it should do.
You're absolutely right, now it compiles without any problems.
Thanks for you help and time.
I think what's happened is that the Smoke library has been generated from
the KDE 3.2 headers, but you're compiling it against KDE 3.3. I had a
look on my KDE 3.1 machine, and KCatalogue::setFileName() did used to be
public, but on 3.3 it's private. So you need to remove the generated .cpp
files from korundum-cvs/smoke/kde (ie smokedata.cpp, x_1.cpp to
x_20.cpp), and then make again to regenerate Smoke. A 'make clean'
command doesn't remove those sources, but it should do.
You're absolutely right, now it compiles without any problems.
Thanks for you help and time.
No problem. I think the KDE version check for the libkmdi library was wrong
though because it was actually introduced in 3.2.0. Your 3.2 lib had it
because the Smoke library generated those classes from the 3.2 headers, and
then the link failed. So I've just changed it in
kdebindings/configure.in.in :
