I notice the developer's wiki has been updated and mentions that qt3 should be build with Trinity sources rather than built from distro sources.
I am building qt3 from the original 3.3.8b sources and applying my own patches. That approach worked okay last spring.
I presume any patches applied in the past no longer are needed because they are included in the Trinity sources.
Problem is I don't see a tarball for the Trinity sources. I don't know how to use git.
I would appreciate somebody updating the wiki to provide some guidance. :) Or provide sufficient details here, which later can be added to the wiki.
Thanks.
Darrell
The Trinity code repository is officially in a hard freeze as of 6:30PM
CDT 10/25/2011, pending release of TDE 3.5.13. The only updates that will
be accepted at this point are critical bug fixes that require only minor
changes to the TDE source.
Distribution packagers, start building your official packages for release
at this time. We are on schedule for an official 3.5.13 release on
November 1, 2011.
Timothy Pearson
Trinity Desktop Project
Building on Slackware 13.1. GCC 4.4.4. Clean chroot build environment.
Building to install to /opt/trinity.
qt3, qca, qca-tls, tqtinterface, dbus-tqt, arts built without error.
Log:
http://humanreadable.nfshost.com/trinity/build_logs/kdelibs-3.5.13-i486-svn…
The log contains environment variables.
Darrell
Hi Timothy,
It seems there is still a problem with the dependencies of the oneiric
packages. Here is the output now:
http://pastebin.com/UJjBvrb5
It seems that libqt-perl still depends on the older perl version.
Also, the IRC chatlog does not seem to be able to handle all unicode.
Characters like ë work, but cyrillic (like привет) shows up as
&#<number>; for each character.
Julius
Hey,
A few weeks ago Micheal Martin posted bug 544 [1] on the tracker. The
bug report has sparked an interest in preserving the tutorials and
documentation that exists on the KDE servers for KDE 3.5. Much of this
information could be potentially useful to new developers, and it will
give us insight into previous development and practices.
I have started transferring pages from the KDE techbase, but there are
also many external links and other misc pages floating around the
Internet. Many of these links are broken, but can be found on the
Wayback Machine [2]. There are entire websites that have been saved on
the Wayback Machine as well.
The purpose of this email is to figure out what to do, and recruit any
interestoied parties to help out.
Should we just link to the archived pages? Should we copy them to our
own web server?
I am just getting started and this will be an ongoing project. So far
I have just created one page on the Wiki, the Developers Tutorial [3].
It is to be the central hub for development pages.
Any r / Comments would be appreciated.
Calvin Morrison
[1] http://bugs.trinitydesktop.org/show_bug.cgi?id=544
[2] http://www.archive.org/web/web.php
[3] http://www.trinitydesktop.org/wiki/bin/view/Documentation/DeveloperTutorial
Hi. I'm not sure if I'm writing the right mailing list so sorry if it isn't
so. Also sorry for my not very good english...
Is there any special need for using "add_subdirectory " insted of
"tde_conditional_add_subdirectory" for kcontrol, kdmlib etc?
I think it's better to include all subdirectories via tde's function...
isn't it?
This afternoon I browsed the developer's wiki to prepare for building packages.
Wiki: "You cannot build part of the tree with CMake and then start building with autoconf...Building with autoconf from the SVN tree is not advisable unless you are prepared to put additional effort into the build."
Recently Tim commented he uses cmake only for the four foundation packages (tqtinterface, arts, kdelibs, kdebase). IIRC one person said s/he was using only cmake. Should those statements be removed from the wiki or clarified?
In the Project Road Map there is a link to the Cmake Checklist. The link is to etherpad rather than a wiki page. I have an etherpad account but the extra work will discourage other people from getting involved. More importantly, that information should be directly available in the developer's HowToBuild web page so people know which packages to build with cmake and which with autotools. Should the information about cmake and package support be more clear?
The link to the QT3 page for the patch seems old (April). Over the past several months I recall reading about several QT3 patches. Have all QT3 patches and information been updated?
The wiki makes no mention about other packages such as dbus-tqt. Does dbus-tqt replace dbus-qt3? What about qca and qca-tls?
Wiki: "The current SVN code has been recently updated to build with gcc >= 4.5." Does that mean Trinity will not build with older versions of gcc?
There is no explanation about --enable-closure configure option. Why is that option needed?
Wiki: "You will need to choose where you wish to install Trinity (/opt/trinity, /opt/kde3, etc...) and update your path in order for a successful build." I presume much work has happened to ensure Trinity coexists peacefully with KDE4. Should the wiki mention that the expected install location is /opt/trinity?
Should references to /opt/kde3 be removed?
Wiki: "Please adjust the path variable to fit your system." The statement is in reference to building packages, but that statement applies to running Trinity too. Should the wiki remind builders to modify the run-time $PATH variable in accordance with the methods used for each distro? for example, Slackware uses /etc/profile.d scripts executed through /etc/profile.
Wiki: "Out of source building is recommended to avoid cluttering the original SVN tree you checked out." I remember some discussion about this months ago. Perhaps the wiki should explain or provide an example of what "out of source building" is?
Approximate build times are those I posted with 3.5.12 for autotools. Would be nice if somebody posted approximate build times for cmake?
There were several challenges building koffice. I believe the package remains officially supported. There is nothing in the wiki about koffice issues. What are the limitations and prerequisites for building koffice?
Thanks much!
Darrell
finally finished cmake build system for kdeartwork.
check and commit that =)
patch in the attach.
git repository is here: https://github.com/Fat-Zer/kdeartwork