LinuxQuestions.org - Trinity Desktop for Slackware-13.37 i486 and x86

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Trinity Desktop for Slackware-13.37 i486 and x86_64 (https://www.linuxquestions.org/questions/slackware-14/trinity-desktop-for-slackware-13-37-i486-and-x86_64-a-4175412147/)

Trinity Desktop for Slackware-13.37 i486 and x86_64

I've gotten the base Trinity Desktop for Slackware-13.37, i486 and x86_64 Multilb System, as the native desktop. I am sure however, I will encounter more problems as I continue to compile more of the packages that are apart of the build. So I am creating this thread as a place to discuss the problems as they arrive.

For more information, see:

http://www.inpito.org/trinity.php

The page describes what I've been doing with the Trinity 3.5.13 desktop.

Great! KDE3 is a much more efficient desktop for working than KDE4. Thanks for sharing!

Unfortunately, my website isn't up as often as I like. So if it's down give it some time, the page is there. I think it's a DNS record problem with my hosting provider as I can ping the IP address, it just can't resolve the host name. The last recorded HTTP request that was successful was at [19/Jun/2012:16:57:04 -0500], so as of right now its been down for about 4 hours. I hope it comes back online soon.

It seems that kdebindings 3.5.13 can't find kdelibs.

Code:

checking for KDE... libraries /usr/lib64, headers /usr/include

checking if UIC has KDE plugins available... no

configure: error: 

you need to install kdelibs first.



If you did install kdelibs, then the Qt version that is picked up by

this configure is not the same version you used to compile kdelibs.

The Qt Plugin installed by kdelibs is *ONLY* loadable if it is the

_same Qt version_, compiled with the _same compiler_ and the same Qt

configuration settings.

Here is my configure:

Code:

./configure --prefix=/usr --sysconfdir=/etc/trinity --libdir=/usr/lib64 --mandir=/usr/man --enable-libsuffix=auto --with-qt-dir=/usr/lib64/qt3 --with-qt-includes=/usr/lib64/qt3/include --with-qt-libraries=/usr/lib64/qt3/lib64 --with-extra-includes=/usr/lib64/tqt3/include --with-extra-libs=/usr/lib64/tqt3/lib64 --enable-dependency-tracking --enable-closure

Added gtk-qt-engine-3.5.13

I added gtk-qt-engine-3.5.13 to the list. http://www.inpito.org/trinity.php For those who like a consistent looking desktop.

But that build packages requires HAL

I have been testing and using Trinity on Slackware 14. :)

To build without HAL requires building from GIT using the new TDEHW libs support, which also requires pmount. In my build scripts that explicitly look for HAL, such as tdebase, I do this:

Code:

if [ -x /usr/sbin/hald ]; then

  BUILD_HAL=${BUILD_HAL:-ON}

  BUILD_TDEHWLIB=${BUILD_TDEHWLIB:-OFF}

else

  BUILD_HAL=${BUILD_HAL:-OFF}

  BUILD_TDEHWLIB=${BUILD_TDEHWLIB:-ON}

  # pmount is required to use TDEHWLIB. pmount is not part of the stock Slackware.

  preinstall_check pmount

fi

if [ -x /usr/bin/upower ]; then

  BUILD_UPOWER=${BUILD_UPOWER:-ON}

else

  BUILD_UPOWER=${BUILD_UPOWER:-OFF}

fi

The TDEHW libs support is unfinished but almost complete and fairly robust. I have no problems with removable devices. The only work around is setting /usr/bin/eject setuid.

The existing 3.5.13 and upcoming 3.5.13.1 release does not contain TDEHW libs support. I tinkered a bit with creating my own HAL package, but had mixed success. TDEHE works nicely.

By the way, I'm sending this specific comment from Firefox 15.0.1 in Slackware 14 64-bit running Trinity from the latest GIT, built last night while I slept.

So yes, Trinity does build and install in 14. :)

Being the development branch, bugs exist, some work-arounds and build patches are needed, but I find Trinity stable and usable. :)

Could you make the packages available for testing?

Quote:

Could you make the packages available for testing?

Build scripts and build environment are available:

Trinity Desktop for Slackware

Quote:

Originally Posted by Woodsman (Post 4794277)

Build scripts and build environment are available:

Trinity Desktop for Slackware

I thought I would save some time not having to build the packages myself. I guess I'll just wait for the next major release. Thanks anyway. :-)

The significant changes are to the Trinity sources, to comply with GCC 4.7.x, glibc, libpng, etc; and to package names. All of that has been fixed in GIT and most if not all of those same build issues were back ported to the upcoming 3.5.13.1. My build run for the main packages and several others takes about 6 hours. To get TQt3 and the core packages built requires about an hour and a half. Building the core provides a basic testable environment. The "time consuming" part is renaming package names in the build scripts.

Quote:

Originally Posted by Woodsman (Post 4794277)

Build scripts and build environment are available:

Trinity Desktop for Slackware

I recently tried to visit Darrell Anderson's excellent site with Slackware info, only to find that the site is now closed. Darrell, if you're reading this forum, please consider posting some of your articles here.

Cheers!

Quote:

Originally Posted by JohnB316 (Post 4994868)

+1. I'd like to try Trinity on my Slackware 14 setup also and need all the help I can get on figuring out how to do so.

Try this:

http://humanreadable.nfshost.com/mis...ildtree.tar.gz

I will not guarantee how long I'll keep the file available. :)

Unpack the archive to an appropriate build directory.

I have not been publicly supporting this for a while --- don't be surprised the docs are outdated.

That said, I have been using Trinity pre-R14.0 from GIT for a long time and am building a new package set right now.

Just run ./TDE.SlackBuild.

I have things configured as a two-step build run. The first step is to build TQt3. The second step builds all remaining packages. Use the SUITE=false option to build beyond the basic package set and use SUITE=false ALLAPPS=true to build more packages. Like so:

SUITE=false ./TDE.SlackBuild

or

SUITE=false ALLAPPS=true ./TDE.SlackBuild

These build scripts presume a local GIT repository. Currently there is no upstream project support for GIT source tarballs. Source tarballs are available only for official releases. Once upon a time my build scripts supported making tarballs, but I haven't tested in a very long time.

The build scripts in the archive are horribly complicated because I'm part of the testing team and I need to support more than a typical user. Feel free to whittle the build scripts to the bare essentials, although you'll still need a local GIT repository or to make your own source tarballs. I don't have time but would be nice if somebody hacked the build scripts to something that could be maintained at slackbuilds.org. Take a look at the Slackware KDE 3.5.10 build scripts for 12.2 for an example how to streamline the build scripts to the essentials.

By coincidence, the pre-R14.0 sources are going into hard freeze tonight. That means focus is changing from testing anything to only fixing certain bug reports for the next weeks. An official R14.0 should be released within the next several weeks. At that time official source tarballs will be available, which will render things easier for many folks.

Last note: There are foundational changes in the upcoming release (the desktop still looks the same :)). Don't mix and match GIT with 3.5.13.X. Stick with one or the other until R14.0 is officially released. :)