>Right-click on Kicker -> Add New Panel -> KSim. (No, I wouldn't
>have thought of looking there either--I didn't even know I had it
>installed until I asked my package mangler about it.)
Ah! Mystery solved. :)
Makes sense now that I know. I have long, long not paid attention
to that menu option.
Long story is I'm updating help handbooks. I wanted to discover
whether the KSim handbook is accessible through the app. The
handbook is a useless template shell anyway, but I wanted to
confirm the handbook is accessible somehow, somewhere. Test: no,
the popup Help option does nothing, the preferences dialog Help
button opens the kicker handbook rather than the ksim handbook.
This latter result seems to affect all applets too.
These panel extensions do not appear anywhere in the help handbook
table of contents (TOC). There is a TOC entry for Konqueror
Plugins. Perhaps there should be one for Panel Extensions?
Darrell
>The still-extant homepage, http://ksim.sourceforge.net/ , provides
>screenshots.
>From the looks of it, it's very similar to gkrellm.
Yes, I saw that web site too. I haven't found information about
starting the app. Not in the applets list, not in the launcher
menu, no executable, no help useful handbook.
Darrell
> Good question. Looks like a superkaramba type app where you
>start the
>executable and it shows up in the systray and lets you configure
>the skin ans
>sensors needed. I'll give it a try when I install tde.
There is no executable. This is a panel extension.
Darrell
>Oh - and k3b is broken right now for me. I'll see if I can't
>figure out the
>'scope' issue - I was good at that a year ago, but I seem to have
>CRS syndrome.
>(can't remember shi...)
>
>How do I include preprocessor checks for libcdio > 0.83?? What is
>the syntax?
Take a gander at some of the libpng patches from a year ago.
I'm guessing you want to test the location of cdda.h in the
configure scripts, not in the C++. Perhaps something like this:
http://www.trinitydesktop.org/patches/1380496303:5077373c0cc9e90f1bd
1d4231fb44686a3c4aa19.diff
Should the libcdio pkgconfig file reveal the location?
Darrell
Slavek, All,
Working with tqscintilla/tqscintilla-plugin, I was quite pleased and surprise
to find tqscintilla builds just fine (first time). However, tqscintilla-plugin
build fails due to the autogenerated Makefile including -lqt for libqt in the
g++ command. The major part of the build is done in:
tqscintilla/qt
Building with:
cd tqscintilla/qt
qmake qscintilla.pro
make
works fine. But the Makefile "install" is broken. While the make produces the
libraries it FAILS to install anything:
1577860 Jan 23 15:38 libqscintilla.so.7.0.1
libqscintilla.so -> libqscintilla.so.7.0.1
libqscintilla.so.7 -> libqscintilla.so.7.0.1
libqscintilla.so.7.0 -> libqscintilla.so.7.0.1
The plugin is built in tqscintilla/designer with:
cd tqscintilla/designer
qmake designer.pro
make
fails with the error:
g++ -luuid -Wl,-rpath,../ -Wl,-rpath,../qt -Wl,-rpath,/opt/tqt3/lib -shared -o
libqscintillaplugin.so qscintillaplugin.o -L../ -L../qt -L/opt/tqt3/lib -luuid
-lqscintilla -lqt
/usr/bin/ld: cannot find -lqt
collect2: error: ld returned 1 exit status
Looking at the string, it looks for -lqt (that doesn't exists - and is NOT
needed) Changing into the build directory and issuing the command without the
-lqt completes fine:
g++ -luuid -Wl,-rpath,../ -Wl,-rpath,../qt -Wl,-rpath,/opt/tqt3/lib -shared -o
libqscintillaplugin.so qscintillaplugin.o -L../ -L../qt -L/opt/tqt3/lib -luuid
-lqscintilla -lqt
$ ls -al
-rwxr-xr-x 1 nobody root 22174 Jan 23 14:41 libqscintillaplugin.so
The problem is that qmake autogenerates the Makefile and the Makefile
automatically includes the -lqt for some reason.
Checking both the tqscintilla/qt/qscintilla.pro and the resulting
tqscintilla/qt/Makefile there is no -lqt added to the g++ command for that app.
Why is it being added to the tqscintilla/designer/Makefile? More importantly -
how do we fix it?
To get around the install & lib issues, I simply modified my build/package
script to get around the errors:
build() {
cd ${srcdir}
## CMAKE config
msg "Setting PATH, CMAKE and Trinity Environment variables"
# Source the QT and TDE profile
[ "$QTDIR" = "" ] && . /etc/profile.d/tqt3.sh # or tqt3.sh
[ "$TDEDIR" = "" ] && . /etc/profile.d/trinity.sh # or tde.sh
## build tqscintilla
msg "Building - ${pkgname}..."
cd ${srcdir}/${pkgname#*-}/qt
qmake qscintilla.pro
make
## build plugin files
msg "Building - ${pkgname}-plugin..."
cd ${srcdir}/${pkgname#*-}/designer
# patch designer/designer.pro; LIBPATH += ../tmplib ../qt
msg "patching designer/designer.pro; LIBPATH += ../tmplib ../qt"
sed -i 's/tmplib/\ ..\/qt/' designer.pro
qmake designer.pro
# patch the resulting Makefile to remove -lqt
msg "patching Makefile to remove -lqt"
sed -i 's/-lqscintilla -lqt/-lqscintilla/' Makefile
make
}
package() {
pkgdesc="A port to Qt3 of Neil Hodgson's Scintilla C++ editor class"
provides=('qscintilla-qt3')
options=('staticlibs' 'libtool' '!emptydirs' '!strip')
msg "Packaging - $pkgbase"
cd ${srcdir}/${pkgname#*-}/qt # use for non-out-of-source
make INSTALL_ROOT="${pkgdir}" install # other form - older package
# install missing library files
install -m 755 -Dd "${pkgdir}${QTDIR}/lib"
install -m 644 -D libqscintilla.so.7.0.1 "${pkgdir}${QTDIR}/lib"
ln -s ${pkgdir}${QTDIR}/lib/libqscintilla.so.7.0.1
${pkgdir}${QTDIR}/lib/libqscintilla.so
ln -s ${pkgdir}${QTDIR}/lib/libqscintilla.so.7.0.1
${pkgdir}${QTDIR}/lib/libqscintilla.so.7
ln -s ${pkgdir}${QTDIR}/lib/libqscintilla.so.7.0.1
${pkgdir}${QTDIR}/lib/libqscintilla.so.7.0
# installing includes
for i in qextscintilla*.h; do
install -m 644 -D $i "${pkgdir}${QTDIR}/include/$i"
done
cd ${srcdir}/${pkgname#*-}/designer # use for non-out-of-source
install -m 644 -D libqscintillaplugin.so "${pkgdir}${QTDIR}/lib"
}
I need to confirm that my package contents are the total contents for the
package. Since you build in the ../qt directory and the ../src is not touched
(except by the magic Makefiles) I'm skeptical. My package consists of:
opt/tqt3/include/qextscintillaprinter.h
opt/tqt3/include/qextscintillacommand.h
opt/tqt3/include/qextscintillalexerbatch.h
opt/tqt3/include/qextscintillalexerpython.h
opt/tqt3/include/qextscintillalexerbash.h
opt/tqt3/include/qextscintillalexerjava.h
opt/tqt3/include/qextscintillalexerdiff.h
opt/tqt3/include/qextscintilla.h
opt/tqt3/include/qextscintillabase.h
opt/tqt3/include/qextscintillalexersql.h
opt/tqt3/include/qextscintillalexercpp.h
opt/tqt3/include/qextscintillacommandset.h
opt/tqt3/include/qextscintillalexer.h
opt/tqt3/include/qextscintillaglobal.h
opt/tqt3/include/qextscintillalexeridl.h
opt/tqt3/include/qextscintillalexermakefile.h
opt/tqt3/include/qextscintillalexerjavascript.h
opt/tqt3/include/qextscintillalexerruby.h
opt/tqt3/include/qextscintillalexercss.h
opt/tqt3/include/qextscintillalexerlua.h
opt/tqt3/include/qextscintillamacro.h
opt/tqt3/include/qextscintillalexerperl.h
opt/tqt3/include/qextscintillaapis.h
opt/tqt3/include/qextscintillalexerproperties.h
opt/tqt3/include/qextscintillalexercsharp.h
opt/tqt3/include/qextscintillalexerhtml.h
opt/tqt3/include/qextscintillalexerpov.h
opt/tqt3/include/qextscintillalexertex.h
opt/tqt3/include/qextscintilladocument.h
opt/tqt3/translations/qscintilla_pt_br.qm
opt/tqt3/translations/qscintilla_fr.qm
opt/tqt3/translations/qscintilla_ru.qm
opt/tqt3/translations/qscintilla_de.qm
opt/tqt3/lib/libqscintilla.so
opt/tqt3/lib/libqscintilla.so.7
opt/tqt3/lib/libqscintillaplugin.so
opt/tqt3/lib/libqscintilla.so.7.0.1
opt/tqt3/lib/libqscintilla.so.7.0
What do you say Slavek?
--
David C. Rankin, J.D.,P.E.
Darrell, All,
Anyone building qscintilla-qt3 and qscintilla-qt3-plugin on R14? Looks like we
will need to name-change update the code with qblah... to tqblah...
What uses the editor? Is it worth fixing?
--
David C. Rankin, J.D.,P.E.
> Anyone building qscintilla-qt3 and qscintilla-qt3-plugin on R14?
>Looks like we
>will need to name-change update the code with qblah... to
>tqblah...
>
> What uses the editor? Is it worth fixing?
I don't use and don't compile. Worth fixing? I have no idea.
We have cruft in the sources I wish we'd delete. Such as the
duplicate kuickshow, which is in tdegraphics, mlt, which nothing in
Trinity uses....
Darrell
> How do you build k9copy without hal?
k9copy needs k3b installed to compile.
To build k3b without hal:
k3b: --without-hal
To build k9copy without hal:
k9copy: Use --enable-k3bdevices to build without HAL support.
Darrell