All,
Upon k3b start, the only error received during startup check was:
<quote>
System locale charset is ANSI_X3.4-1968
Your system's locale charset (i.e. the charset used to encode filenames) is set
to ANSI_X3.4-1968. It is highly unlikely that this has been done intentionally.
Most likely the locale is not set at all. An invalid setting will result in
problems when creating data projects.
Solution: To properly set the locale charset make sure the LC_* environment
variables are set. Normally the distribution setup tools take care of this.
</quote>
I know about a year ago, there was considerable discussion about where these
variables should be set. Looking, it seems that some distros take care of this
with XDG config which can be set separately between gnome XDG and kde XDG. Does
TDE need to look at setting these? I don't know the answer. I do know SuSE sets
them and Arch doesn't. So there is a variation between the way this is handled
distro to distro. May not be a bad thing to do in the TDE config if these
setting matter.
--
David C. Rankin, J.D.,P.E.
All,
For those not familiar with applications/basket (Basket Notepads), it is
probably the finest 2nd brain invented for TDE. You can simply squirrel away all
types of information and notes in a simple manner. (text, graphics, audio,
colors, etc..) Think of it as an integrated sticky notes suite on steroids
providing full search of all the information you have in it. I have built up
hundreds of notes over the years and this is a must have app for me.
Builds and works fine:
http://www.3111skyline.com/dl/dt/trinity/ss/basket-1.0.3.jpg
Tip: set the following settings for improved ease of use:
(Basket tab)
[x] insert note when clicking to the right of the insertion line.
(General tab)
Show main windows when mouse hovers over system try icon for 7 tenths second
Crystal window decorations and basket notepads were the last 2 'must-haves'
before I could ditch 3.5.12 and move to 3.5.14 as my daily driver :)
--
David C. Rankin, J.D.,P.E.
All,
I have twin-style-crystal building on TDE. The version of crystal in GIT is
1.0.5. I want to get 1.0.7 building. I have both build directories and I will
work though them to see if I can figure out why. What I would like to get is
advise on what to start with to see if I can isolate the issue. Do I start with
the 'configure' files and go from there, or is it better to diff the raw sources
before trying to sort it out. Basically, the error with 1.0.7 is:
g++ -DHAVE_CONFIG_H -I. -I.. -I/opt/trinity/include -I/opt/tqt3/include -I.
-include tqt.h -I/usr/include/tqt -I/usr/include/tqt/Qt -DQT_THREAD_SUPPORT
-D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE
-Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -O2 -march=x86-64
-mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4
-D_FORTIFY_SOURCE=2 -Wformat-security -Wmissing-format-attribute
-Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common
-I/usr/include/tqt -MT embedtool.o -MD -MP -MF .deps/embedtool.Tpo -c -o
embedtool.o embedtool.cpp
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.
There is no QtGui/qtransform.h on my system even though it is included from
tqt/Qt/qimage.h. Should I look for a missing package or option not-enabled on
one of the packages that is already built? From searching, it looks like QtGui
is a plugin to Qt (or in this case TQt). Is there such a thing in TDE?
--
David C. Rankin, J.D.,P.E.
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.