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.
I would be grateful for somebody helping me locate an image in the sources. The image is seen in this About dialog:
http://humanreadable.nfshost.com/trinity/build_logs/about-dialog.png
I'm unsure why this dialog shows a default image when the desktop file specifies Icon=fifteenpieces.
I'd like to update the image. I think the image is a default image for About dialogs.
Thanks!
Darrell
Tim, anyone,
It would be nice to have a troubleshooting 'cheat sheet' to use to solve
TQwhatever not declared failures when they are encountered. I can read c++, I
know what constructors are, what destructors are, what public and private
members are, etc.., but with a project the size of TDE, with the multiple levels
of submodule inclusion through the git tree, my eyes glaze over trying to chase
down where the declaration problems are when they are encountered.
Case-in-point, tdeadmin. I ran into a build failure cause by 'TQListViewItem'
has not been declared:
In file included from knetworkconfdlg.cpp:11:0:
knetworkconfdlg.h:142:40: error: 'TQListViewItem' has not been declared
In file included from knetworkconfdlg.cpp:31:0:
./knetworkconfdlg.ui.h:153:6: error: prototype for 'void
KNetworkConfDlg::updateProfileNameSlot(TQListViewItem*)' does not match any in
class 'KNetworkConfDlg'
knetworkconfdlg.h:142:18: error: candidates are: virtual void
KNetworkConfDlg::updateProfileNameSlot(int*)
./knetworkconfdlg.ui.h:147:6: error: virtual void
KNetworkConfDlg::updateProfileNameSlot()
In file included from knetworkconfdlg.cpp:688:0:
knetworkconfdlg.moc: In member function 'virtual bool
KNetworkConfDlg::tqt_invoke(int, TQUObject*)':
knetworkconfdlg.moc:171:80: error: no matching function for call to
'KNetworkConfDlg::updateProfileNameSlot(TQListViewItem*)'
knetworkconfdlg.moc:171:80: note: candidates are:
./knetworkconfdlg.ui.h:147:6: note: virtual void
KNetworkConfDlg::updateProfileNameSlot()
./knetworkconfdlg.ui.h:147:6: note: candidate expects 0 arguments, 1 provided
knetworkconfdlg.h:142:18: note: virtual void
KNetworkConfDlg::updateProfileNameSlot(int*)
knetworkconfdlg.h:142:18: note: no known conversion for argument 1 from
'TQListViewItem*' to 'int*'
If I knew where to start, then I wouldn't mind trying to figure out where to
fix the declaration error. But not knowing whether I just start grepping within
tdeadmin for TQListViewItem or whether I need to start in tqtinterface or what,
I'm somewhat left chasing my tail. I don't know if it is possible, but I know it
would help me and others if there was something like:
TQString objects are type ......
TQListViewItem objects are type .....
To fix TQxzy declaration issues:
(1) grep for '___________' in ___________;
(2) if declare ___________ found then
(3) ___________; else
(4) then grep in ______________;
(5) if declare ____________ found then
...........
Just some simple decision tree would go a long way to get everyone involved in
helping with these issues and also provide a valuable tool that would help cut
down bug squashing time even if the person can't solve it by being able to say
'I got to step 8 in troubleshooting and 1-7 are fine, but I can't figure out
what to do next...'
Worth a thought. If somebody else can help here, please jump in.
--
David C. Rankin, J.D.,P.E.
When using the Standard splash theme, the respective icons jump in the left corner of the screen.
Would somebody help me learn the name of each of those icons and where they are located in the sources?
The last jumping icon is a plain text document icon. I doubt that is the intended icon. That icon often is used when another icon is not found or not specified. I want to change the icon to the default Trinity logo icon, like the other splash themes.
Thanks!
Darrell