Trinity Desktop for Slackware-13.37 i486 and x86_64
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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.
Last edited by Stragonian; 06-19-2012 at 07:58 PM.
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.
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.
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.
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.
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!
+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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.