Building from tqt3 onwards all compiles for me (slackware 13.37)
When compiling twin-style-crystal it stops at the error that qvariant.h was
not found.
Adding --with-extra-includes=/usr/include/tqt/Qt/ during configure finds
the file but then stops with the error:
In file included from configdialog.h:12:0,
from crystalconfig.cc:43:
/usr/include/tqt/Qt/qvariant.h:45:28: fatal error: QtCore/qatomic.h: No
such file or directory
compilation terminated.
make[3]: *** [crystalconfig.lo] Error 1
make[3]: Leaving directory `/tmp/twin-style-crystal/client/config'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/twin-style-crystal/client'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/twin-style-crystal'
make: *** [all] Error 2
This file (QtCore/qatomic.h) does not exists anywhere in the git tree or
the local system.
Jay
In keditcl.h, installed by tdelibs, is the following:
class TDEUI_EXPORT_DEPRECATED KEdit : public TQMultiLineEdit
What does that mean to any code wanting to use that function? That is, how should the code be updated to call that function?
Darrell
Hi,
As was pointed out by Darrell Anderson, a documentation review board is needed. I have started a list on the Etherpad. This list is currently rather incomplete as I have not yet gone through any of the documentation, and I therefor do not have a thorough knowledge of everything that needs updating.
The list on the Etherpad should list known changes that need to be made to the documentation, and should allow anybody interested in maintaining documentation to claim the documentation for specific apps that they use on a regular basis.
The list of apps that is on the Etherpad is currently incomplete. I currently not have time to go through the packages to list all of them as I have some stuff in real life that I need to do, so the first several items on the apps list are just categories copied from the source downloads page. Feel free to expand them if you can.
If you do not trust your technical writing skills, perhaps you can simply check the docs for apps you are interested in and report needed changes that you see.
--
Kris Gamrat
The following messages appear when building gwenview:
/opt/trinity/include/ntqglobal.h:711: error: 'INT32' has a previous declaration as 'typedef int INT32'
Configure output:
checking libmng.h usability... no
checking libmng.h presence... yes
configure: WARNING: libmng.h: present but cannot be compiled
configure: WARNING: libmng.h: check for missing prerequisite headers?
configure: WARNING: libmng.h: see the Autoconf documentation
configure: WARNING: libmng.h: section "Present But Cannot Be Compiled"
configure: WARNING: libmng.h: proceeding with the compiler's result
checking for libmng.h... no
Configure.log:
#include <libmng.h>
configure:25086: result: no
configure:25086: checking libmng.h presence
configure:25086: g++ -E -DQT_THREAD_SUPPORT -D_REENTRANT -I/opt/trinity/include -I. -include tqt.h -I/opt/trinity/include/tde -I/usr/include/tqt conftest.cpp
configure:25086: $? = 0
configure:25086: result: yes
configure:25086: WARNING: libmng.h: present but cannot be compiled
configure:25086: WARNING: libmng.h: check for missing prerequisite headers?
configure:25086: WARNING: libmng.h: see the Autoconf documentation
configure:25086: WARNING: libmng.h: section "Present But Cannot Be Compiled"
configure:25086: WARNING: libmng.h: proceeding with the compiler's result
configure:25086: checking for libmng.h
configure:25086: result: no
configure:25161: WARNING: Can't find libmng.h, Gwenview won't be compiled with MNG support
Darrell
Arch folks,
PyQt3 will build with the git sources for tde, but I get LOTS (1000s) of
deprecation warnings. Eg:
sip: Deprecation warning: sip/qt/copying.sip:50: %OptionalInclude is deprecated,
use %Include and the 'optional' argument instead
sip: Deprecation warning: sip/qt/copying.sip:51: %OptionalInclude is deprecated,
use %Include and the 'optional' argument instead
sip: Deprecation warning: sip/qt/qnamespace.sip:23: %ExportedDoc is deprecated,
use %Extract instead
sip: Deprecation warning: sip/qt/qwindowdefs.sip:23: %ExportedDoc is deprecated,
use %Extract instead
sip: Deprecation warning: sip/qt/qwindowdefs.sip:37: %OptionalInclude is
deprecated, use %Include and the 'optional' argument instead
I'm not that familiar with PyQt3 or sip, so I don't know whether it is needed
or not, but to make sure nothing was lost, I was building it. Do we really need
this package, if so, does it need to be updated to get rid of the deprecations
warnings?
--
David C. Rankin, J.D.,P.E.
Tim, All,
What is the status of renaming from 'k_whatever' to 't_whatever'? Are we at a
point where all that will be done is done? Obviously, this effects building and
packaging. For instance tdebase still contains all the 'k' applications:
kappfinder
kate
kcheckpass
kcminit
kcontrol
kdcop
kdebugdialog
kdeeject
kdepasswd
kdesktop
kdialog
kfind
khelpcenter
khotkeys
kicker
kioslave
klipper
kmenuedit
knetattach
konqueror
konsole
kpager
kpersonalizer
kreadconfig
krootbacking
kscreensaver
ksmserver
ksplashml
kstart
ksysguard
ksystraycmd
While some have move to 't' apps:
tdeinit
tdeprint
tdesu
tdm
tdmlib
Do we expect to see in the future:
tappfinder
tate
tcheckpass
tcminit
...
tonqueror (Sounds like the biggest baddest Tonka truck)
tonsole (Sounds like something you have removed as a kid)
...
Or can we be pretty certain the remaining 'k' names won't change?
--
David C. Rankin, J.D.,P.E.
Guys, gals,
Looking at tdebase build package for arch based on the original 3.5.13
tarball, I show the following patches:
patches/01-kicker-lockout-applet-button-order.patch
patches/dbusfix.patch
patches/07-bigger_title_icons_in_kcontrol.patch
patches/06-nspluginscan-xdgcompliance.patch
patches/08-kip_kdesktop_rounded_icon_text_corners.patch
patches/03-kcontrol_advbg_step.patch
patches/02-doc_location.patch
and
xsession.patch
Does anyone know which are still required for the tdebase build from the git
tree? I looked at http://scm.trinitydesktop.org/scm/git/tdebase, but I can't
figure out which patch may have been applied. Better tool for that?
--
David C. Rankin, J.D.,P.E.
Archers,
In the effort to clean up the daisy-chain of $pkgname, $depends, and $provides
as I go through the build scripts for the git tree, here is my first thoughts on
a name cleanup. I'm not tied to any of the names and the goal is simply to make
the dependency tree as clean as possible without K_this and T_that intermixed.
The $depends simply lists the git tree depends and does not list the other
required depends for building (those are what they are), but I want to remove
depends that don't belong or are unnecessary (referencing a previous trinity
package implicitly includes all the prior depends - so duplication is unnecessary)
Look it over. I've only done it for the packages I have built so far
(avahi-tqt still won't build). Obviously some people won't build the 'davs' or
avahi-tqt, so I've set the $depends accordingly.
# GITsource $pkgname $provides $depends
qt3 tde-qt3 'qt3'
tqtinterface tde-tqtinterface 'tqtinterface' 'qt3'
arts tde-arts 'arts' 'tqtinterface'
dbus-tqt tde-dbus-tqt 'dbus-tqt' 'arts'
dbus-1-tqt tde-dbus-1-tqt 'dbus-1-tqt' 'dbus-tqt'
libcaldav tde-libcaldav 'libcaldav' 'dbus-1-tqt'
libcarddav tde-libcarddav 'libcarddav' 'dbus-1-tqt'
libart-lpgl tde-libart-lpgl 'libart-lpgl' 'dbus-1-tqt'
avahi-tqt tde-avahi-tqt 'avahi-tqt' 'dbus-1-tqt'
tdelibs tde-tdelibs 'tdelibs' 'libart-lpgl'
tdebase tde-tdebase 'tdebase' 'tdelibs'
The $pkgname is just a stab. I actually will probably want something like:
$pkgname
tde-dep-qt3
tde-dep-tqtinterface
tde-dep-arts
tde-dep-dbus-tqt
tde-dep-dbus-1-tqt
tde-dep-libcaldav
tde-dep-libcarddav
tde-dep-libart-lpgl
tde-dep-avahi-tqt
tde-tdelibs
tde-tdebase
...
tde-app-kpilot
...
That way dependencies, applications, etc... all sort together and the tde-xyz
is shorter than including 'dependencies' or 'applications' in the file name.
Just my thoughts...
--
David C. Rankin, J.D.,P.E.
Archers, All,
Currently, Arch installs trinity to /opt/trinity. Personally, I would like to
move the default install to /opt/tde. Two reasons: (1) most important -- less
typing; (2) the tradition of the install being in /opt/kde, why not standardize
around /opt/tde?
For the rest of the community -- Where are you putting tde? It would just make
sense to set a community-wide standard. Yes, I know that the location is
irrelevant and can be obtained by the standard environment files, but we
recently had a rebuild of 3.5.12 that moved from /opt/kde to /opt/kde3. That's
fine, but depending upon the repo you hit to pull files from, your system would
break due to install location differences in the various packages.
I don't have any hard feelings either way for any single location, but if it
is all the same, then if possible, I would like to see a standard that all
packagers could reference. Of course you don't have to use it, but if there is a
standard install, the balance of builds will migrate to it over time.
What says the team?
/opt/trinity
/opt/tde
/opt/tde_ver (ver being a 2 or 3-digit version: eg. 13 or 313)
/opt/other_suggestions?
Personally for me, /opt/tde works :)
(/opt/trinity is probably my fault on arch anyway :)
--
David C. Rankin, J.D.,P.E.
Calvin, Pawel, Baho,
Comparing my old tdelibs build with the current, I have -DWITH_PAM=ON. That
isn't set in the current build scripts. Is it already set by default or was
there another reason for not keeping that option?
--
David C. Rankin, J.D.,P.E.