Tim, Darrell,
Tweaking out k3b, I probably wasted time looking for resmgr.h. I take it
it's dead. However, I have another configure failure with hal-dbus that I need
to know if it should be fixed or if that code is somewhere else now.
Specifically, I have gotten k3b fully built except for the following:
K3b - Include libdvdread (Video DVD ripping) support:
K3b - yes
K3b - Resmgr support: no
K3b - Compile HAL support no
K3b - You are missing the HAL >= 0.5 headers and libraries
K3b - or the DBus Qt bindings.
<snip, all others 'yes'>
Good - your configure finished. Start make now
What's with the HAL support failing? Should I just ignore the Resmgr failure?
--
David C. Rankin, J.D.,P.E.
When building kmplayer I receive the following build warning:
configure: WARNING: unrecognized options: --enable-npplayer
I can build kmplayer from the original sources in KDE3 with that option and do not receive the warning.
Anybody else receive that warning and ideas about the cause?
Darrell
Tim,
Do you care about updating the old version info in the GIT tree? I was going
through tqtinterface files looking to enable qtransform.h header generation and
I keep running across old version info such as:
tqtinterface.lsm:
Begin4
Title: tqtinterface
Version: Trinity 3.5.12
README:
About tqtinterface
-------------
This is version 3.5.12 of the Trinity Qt Interface
I know this is low priority, but do you want us to collect the information of
where this old stuff is when we find it?
--
David C. Rankin, J.D.,P.E.
Archers,
k3b builds! Issues remain with digikam and gwenview. It was sure good to see:
Finished making: tde-k3b 3.5.14_dev-1 (Tue Mar 27 16:50:40 UTC 2012)
--
David C. Rankin, J.D.,P.E.
I converted the original qca package to TQt and renamed to tqca.
To anybody interested, the converted sources are here:
http://humanreadable.nfshost.com/trinity/patches/tqt-fixes/
The converted tqca sources build without failures. The final package looks reasonable. Others more qualified than me should validate that the final package is good. I don't know the relationship of the original qca and qca-tls or how the original qca-tls depended upon qca for building. That relationship will have to be validated too. I have no idea how to test either.
I compared the original qca-tls sources to a copy of tqca-tls stripped of the TQt layer. The two source sets are practically identical. Therefore I don't think anything has been done to the converted tqca-tls sources that eliminates the need for a converted qca package. (Francois mentioned he has a patch that does something like that.)
I don't know whether I wasted my time converting the package. If not, then pushing the converted sources to GIT would resolve bug report 817.
Darrell
Tim, Darrell,
I'm working on crystal window decorations and I've run into a snag. Looks like
there are missing parts of tqtinterface. The build fails quickly when qimage.h
attempts to include QtGui/qtransform.h:
In file included from embedtool.cpp:26:0:
/usr/include/tqt/Qt/qimage.h:45:30: fatal error: QtGui/qtransform.h: No such
file or directory
compilation terminated.
make[2]: *** [embedtool.o] Error 1
make[2]: Leaving directory `/home/david/Documents/bld/twcs5/src/crystal-1.0.7/pics'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/david/Documents/bld/twcs5/src/crystal-1.0.7'
make: *** [all] Error 2
Checking file ownership, qimage.h is owned by tqtinterface:
18:32 valkyrie:~/Documents/bld/twcs5> pmqo /usr/include/tqt/Qt/qimage.h
/usr/include/tqt/Qt/qimage.h is owned by tde-tqtinterface 3513_tqt-19
Why would the tqtinterface qimage.h header be attempting to include a
non-existent file? Is there a Qt plugin of some kind missing?
--
David C. Rankin, J.D.,P.E.
Guys,
One thing that I have found very useful in KDE3 was the ability to view and
use medical image file formats (MRI,CT,etc..). The functionality is provided
through libksquirrel. However, the xmedcon library must be present on the system
for libksquirrel to provide this capability. I have tested and built xmedcon
with current (bleeding edge) libraries and it works fine. For TDE to be able to
handle medical image formats -> that's a pretty good feather in it's cap :)
source=('http://downloads.sourceforge.net/project/xmedcon/XMedCon-Source/0.11.0/xmed…')
md5sums=('99646261a5cfa4898956de876e99abeb')
_prefix=/usr
./configure \
--prefix=${_prefix} \
--sysconfdir=/etc \
--localstatedir=/var \
--libdir=/usr/lib
make
Simple build. I'll test later today or tomorrow. I'll have to pull CTs from
closed files to test with the medical images, but I don't anticipate problems.
There are a few other file formats that I have to work on (CAD DXF, etc..),
but I would like to see TDE ship with all capabilities working (or at least be
able to have all of them working)
--
David C. Rankin, J.D.,P.E.
In an effort to resolve bug report 817 I converted qca to tqca. That small package never got converted to Trinity TQt.
One stumbling block. I am unable to figure out how to force the configure script to add /usr/include/tqt to the -I include list. If I could get past that then I suspect any remaining build problems will be superficial. The build log output is clear that the problem is not finding the tqt headers.
To anybody with those skills, here is the link to the converted files:
http://humanreadable.nfshost.com/trinity/patches/tqt-fixes/tqca/
The entire gzipped source tree is here:
http://humanreadable.nfshost.com/trinity/patches/tqt-fixes/tqca.tar.gz
Thanks!
Darrell
All,
Here is a new one, I built tdesdk using autoconf (builds fine) but on install,
it fails due to conflicting files from tdesvn. The error on install is:
loading packages...
resolving dependencies...
looking for inter-conflicts...
Targets (1): tde-tdesdk-3513_tqt-1
Total Installed Size: 141.97 MiB
Proceed with installation? [Y/n]
(1/1) checking package integrity
[#######################################] 100%
(1/1) loading package files
[#######################################] 100%
(1/1) checking for file conflicts
[#######################################] 100%
error: failed to commit transaction (conflicting files)
tde-tdesdk: /opt/trinity/share/services/svn+file.protocol exists in filesystem
tde-tdesdk: /opt/trinity/share/services/svn+http.protocol exists in filesystem
tde-tdesdk: /opt/trinity/share/services/svn+https.protocol exists in filesystem
tde-tdesdk: /opt/trinity/share/services/svn+ssh.protocol exists in filesystem
tde-tdesdk: /opt/trinity/share/services/svn.protocol exists in filesystem
Errors occurred, no packages were upgraded.
Checking ownership of the existing files, it is tdesvn that provides the
conflicting files. How should we handle this? Only one package should provide
the files. I'll check for existing bug reports and if I can't find one I'll file it.
I would welcome suggestions for how we handle this. Obviously tdesvn needs to
provide the files if tdesdk isn't installed and vice-versa, but they both can't
provide them...
--
David C. Rankin, J.D.,P.E.