I am unable to build kdenetwork 3.5.13 from the source tarballs on Slackware 13.1 unless I use the -DBUILD_WIFI=OFF option.
The error message:
-- Looking for iw_get_stats in iw
-- Looking for iw_get_stats in iw - not found
CMake Error at cmake/modules/TDEMacros.cmake:20 (message):
#################################################
wifi support needs wireless tools >= 27, but was not found on your system
Slackware 13.1 has wireless-tools-29 and the package is installed in my build environment. There is a /usr/sbin/iw command installed.
I want to build the package to support wireless. How do I get around this error?
Thanks.
Darrell
As you are probably aware the Trinity website went dark for a sizable
chunk of November 2, 2011. This was due to one of our Internet service
provider's fiber optic lines being cut, and all Trinity services have now
been restored.
However, this event has delayed the publishing of the Trinity 3.5.13
binary packages for all supported distributions. While the complete
3.5.13 source tree is currently available for download, binary packages
will not be available for download until Friday, November 4, 2011 at the
earliest.
The Trinity Desktop Project apologizes for the inconvenience, and hopes
that you will enjoy our latest release in a couple days.
Timothy Pearson
As suggested previously I created a sym link for qglobal.h. That got me past the previous build failure.
kdelibs now builds to 70% and stops with errors about kdeprint.
cups 1.4.5 if that makes any difference.
Log:
http://humanreadable.nfshost.com/trinity/build_logs/kdelibs-3.5.13-i486-1-b…
Thanks.
Darrell
How are these bindings supposed to be built now?
In the past pyqt3 and pykde3 were built separatebly before building kdebindings.
I notice in the 3.5.13 tarballs two packages named pykdeextensions and python-trinity. Do these packages replace pyqt3 and pykde3?
Darrell
Recently I reported I could not build kdelibs from SVN. I now am trying to build from the 3.5.13 tarballs. I am having the same failure.
Building on Slackware 13.1. GCC 4.4.4. Clean chroot build environment.
I am building everything to install to /opt/trinity including tqtinterface.
qt3, qca, qca-tls, tqtinterface, dbus-tqt, dbus-1-tqt, arts built without error. I built qt3 from the Trinity 3.3.8.d sources.
I am building kdelibs using cmake and I am building "out of source."
Log:
http://humanreadable.nfshost.com/trinity/build_logs/kdelibs-3.5.13-i486-1-b…
The log contains environment variables. The variables show that my build script is finding all paths.
My cmake directives:
cmake ${TMP}/${PRGNAM} \
-DCMAKE_C_FLAGS:STRING="$CPUOPT" \
-DCMAKE_CXX_FLAGS:STRING="$CPUOPT" \
-DCMAKE_INSTALL_PREFIX=${PREFIX} \
-DSYSCONF_INSTALL_DIR=${SYSCONFDIR} \
-DLIB_SUFFIX=${LIBDIRSUFFIX} \
-DMAN_INSTALL_DIR=${MANDIR} \
-DQTDIR=$QTDIR \
-DQT_LIBRARY_DIRS=${QTDIR}/lib \
-DCMAKE_SKIP_RPATH=OFF \
-DBUILD_ALL=ON \
-DWITH_LIBART=ON \
-DWITH_LIBIDN=ON \
-DWITH_LUA=$LUA \
-DWITH_TIFF=ON \
-DWITH_JASPER=ON \
-DWITH_OPENEXR=ON \
-DWITH_UTEMPTER=ON \
-DWITH_AVAHI=$DNSSD \
-DWITH_ASPELL=ON \
-DWITH_HSPELL=OFF
Thanks much.
Darrell
Hello.
Having some trouble with building kdebase. It doesn't seem to be able to
find dbus-tqt
==> Making package: trinity 1240522-1 (Thu Nov 3 15:35:40 EDT 2011)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
-> Found kdebase-3.5.13.tar.gz
==> Validating source files with md5sums...
kdebase-3.5.13.tar.gz ... Passed
==> Extracting Sources...
-> Extracting kdebase-3.5.13.tar.gz with bsdtar
==> Removing existing pkg/ directory...
==> Starting build()...
==> Setting PATH, CMAKE and Trinity Environment variables
==> Creating out-of-source build directory:
/mnt/home/calvin/builds/trinity/tde-packaging/arch/release/trinity-kdebase/src/build
==> Starting cmake...
-- tmoc path: /opt/trinity/bin/tmoc
-- moc path: /opt/qt/bin/moc
-- uic path: /opt/qt/bin/uic
-- checking for 'TDE'
-- found 'TDE', version 3.5.13
CMake Error at cmake/modules/TDEMacros.cmake:20 (message):
#################################################
dbus-tqt is required, but was not found on your system
#################################################
Call Stack (most recent call first):
ConfigureChecks.cmake:203 (tde_message_fatal)
CMakeLists.txt:139 (include)
what is weird is that my PKG_CONFIG_PATH is set to:
/opt/trinity/lib/pkgconfig:/opt/qt/lib/pkgconfig:/opt/qt/pkgconfig:/opt/qt/pkgconfig
and in /opt/trinity/lib/pkgconfig/ are: dbus-1-tqt.pc and dbus-tqt.pc
Anyone have ideas for this?
Calvin
I don't see either package in svn or the tarballs. Are these packages now obsolete with 3.5.13? Or just build them separately as done previously?
Darrell
Hello all,
Good work team, and thank you to everyone who helped with the release!
Now that the release is out the door, we are looking ahead to the next
release. At this meeting we will discuss our goals and our ideas for
3.5.14. If everyone could start to thinking about what they would like to
do, or see done for 3.5.14 that would be great. Please bring your thoughts
to the meeting.
Please checkout the following links and contribute as such:
Roadmap for 3.5.14:
http://www.trinitydesktop.org/wiki/bin/view/Developers/3_5_14_Roadmap
Release Goals for 3.5.14:
http://www.trinitydesktop.org/wiki/bin/view/Developers/3_5_14_Release_Goals
Etherpad for November Meeting: http://trinity.etherpad.trinitydesktop.org/15
This meeting is for everyone interested helping trinity desktop. That
means, Packagers, Contributors, Developers, and even Users! If you are
interested in getting involved and don't know where to start, please come
to this meeting to find out how you can help!
There will more detailed time information as we draw closer to the meeting.
The meeting will probably occur in the early evening EST.
Please RSVP and let us know if you can/cannot make it.
Thank you,
Calvin Morrison
Trinity Desktop Team.
hi everyone ...
first off, congratulations on a new release!
the way i see Trinity, it is the continuation of work on the 3.5 codebase.
nobody else is doing it, nobody else seems willing to do it outside of Trinity
and there are people who want to use it. these are all great things and a
strength of free and open source software.
as such, i see Trinity doing a service by giving those who wish to continue
using KDE 3.x the ability to do so without facing software obsolence through
bit rot. this makes those folks happier, and prevents them from feeling like
their only remaining response is to behave poorly towards those working on the
4.x codebases. it's win-win in the truest sense of the word.
but i'm not going to whitewash things either: there are those who use Trinity
who really dislike 4.x and those in the KDE community who see Trinity as a
safe haven for people who have (or continue to) behave poorly. this is beyond
unfortunate since Trinity and the KDE Platform and Workspaces 4.x both provide
good things to the same group of people: those who use KDE software. so i'd
like to see the remaining negativity put behind us so all of us working on KDE
code can co-exist in good spirit, happy in the knowledge that everyone is
getting what they want and doing so in the spirit of true freedom. i hope you
feel similarly.
this was the spirit in which we encouraged people to work on the 3.x code if
they wanted to and, unlike some other communities who have in recent times
openly berated and made fun of people who wanted to do similar things for
their software, have been supporters and agreed with the goals you have.
so when i see the announcements on sites starting with quotes like this:
"Disappointed with KDE 4's performance and other shortcomings, Timothy Pearson
continued KDE 3.5 development under the name Trinity."
i cringe a little inside because that does nothing but stir up hornets' nests.
when i read this in the announcement to the mailing list:
"Why upgrade from KDE3.5.10, the latest release available from KDE e.V.?
Simply put, Trinity is faster, more secure, and far more feature rich than
3.5.10 ever was!" (http://trinity-devel.pearsoncomputing.net/?0::3271)
i feel sad because Trinity should really not be trying to stand out as a
_competitor_ to 3.5.10 but as the continuation of that code base. (btw, KDE
e.V. never puts out KDE releases; the community of participants and
contirbutors does that.)
by positioning Trinity as a competitor when no such competition exists only
serves to strengthen us/them lines that simply do not exist in reality.
personally, i'm tired of the needless divisions in F/OSS that arise because
people can not simply live and let live, because we for some reason feel the
need to constantly tear each other down in an attempt to make our own efforts
seem more presentable and respectable. what rubbish. Trinity, as the
continuation of the 3.5 codebase, stands on its own feet alongside Plasma
Desktop and the rest of the 4.x products. we should therefore also stand as
allies and friends. we should also stand for what we are, not for what (or
who) we are not.
as the developers, and therefore leaders of the Trinity project, please
consider this when working on and then publicizing your next release.
i appreciate your time and patience if you've read this far :)
--
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
KDE core developer sponsored by Qt Development Frameworks
