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.
I've been trying to build tox, a multimedia messenger, and I was
aiming at building its qt client (qtox). So I successively went on
building/installing:
1. qrencode
2. sqlcipher
3. openal
4. lame
5. libxkbcommon
6. qt5
7. libfilteraudio
8. opus
9. libsodium
10. speex
11. x264
12. ffmpeg
13. toxcore
which went well, but when I tried to build qtox I got a compilation
error, so I switched to another client
14. utox
That one was easy to build, install, and test.
Do you know what the differences are between the two? I hadn't seen all the deps on qtox. I think I stopped first at just seeing qt5, since utox didn't need anything like that. Nothing wrong with qt5 of course, just not what I want to spend more than a few minutes on just for one app (I don't have any qt5 so far). But even then, ffmpeg, lame, openal, x264, are all things that are beyond utox. utox seems to be full featured enough as it is.
You could also share the compilation log so we can try and find a solution for the error.
I was planning on compiling qtox myself... for inclusion into one of my future PLASMA5 Live ISO images (since the majority of dependencies would already be fulfilled by the PLASMA5 package set).
Do you know what the differences are between the two? I hadn't seen all the deps on qtox. I think I stopped first at just seeing qt5, since utox didn't need anything like that. Nothing wrong with qt5 of course, just not what I want to spend more than a few minutes on just for one app (I don't have any qt5 so far). But even then, ffmpeg, lame, openal, x264, are all things that are beyond utox. utox seems to be full featured enough as it is.
As I was aiming at building a qt5 client, the list is longer than necessary for building a gtk client.
But still: toxcore, libfilteraudio, opus, libsodium, OpenAL are prerequisites for building utox
utox requires: libfilteraudio, toxcore
toxcore requires: requires: opus, libsodium
libfilteraudio requires: OpenAL
libsodium, OpenAL have no requirements
So for utox the list should be
1. openal
2. libfilteraudio
3. opus
4. libsodium
5. toxcore
6. utox
I just built qTox and all deps yesterday on a clean install of -current. I didn't have any issues.
I've used qTox since I found out about it and when I tried uTox it just felt "stripped down" to me and everything looked oversized. Things may have changed since then but I think that qTox is the better choice. That of course is just my opinion.
And I think your build list is a little long for qTox, this is what I build for qTox (and in this order);
As I was aiming at building a qt5 client, the list is longer than necessary for building a gtk client.
Oh ok. Now I understand the list you posted. So it is basically the same, plus qt5. I'll be interested in it in a later date, but not now. I think qtox might be a more complete client, but so far I can't see what the difference is. Do you know any difference?
Edit: @Skaendo, same question on qtox, since you are already there. How long ago did you try utox? Last time I was using any tox client, I don't think there was any kind of video support, so, it has changed quite rapidly.
Last edited by the3dfxdude; 08-26-2016 at 11:22 AM.
Oh ok. Now I understand the list you posted. So it is basically the same, plus qt5. I'll be interested in it in a later date, but not now. I think qtox might be a more complete client, but so far I can't see what the difference is. Do you know any difference?
Edit: @Skaendo, same question on qtox, since you are already there. How long ago did you try utox? Last time I was using any tox client, I don't think there was any kind of video support, so, it has changed quite rapidly.
It was some time ago that I tried uTox, probably not long after I heard about Tox, I'd say 6m to 1y ago. It just felt like a stripped down version to me. I couldn't tell you the specific differences, but the UI did look different than the image that is posted now. Everything looked "oversized". Honestly, to me it felt like comparing Windows to Linux (Linux being qTox).
On qTox I've used the chat, group chat, file transfer, smileys and screenshot. I haven't used the call or video chat yet. But I like qTox a lot.
You could also share the compilation log so we can try and find a solution for the error.
I was planning on compiling qtox myself... for inclusion into one of my future PLASMA5 Live ISO images (since the majority of dependencies would already be fulfilled by the PLASMA5 package set).
I figured out what went wrong. My qt5 symbolic links are all messed up.
qmake-qt5 points to the qt4 qmake
When I replaced
Code:
qmake-qt5 ....
by
Code:
/usr/lib$LIBDIRSUFFIX/qt5/bin/qmake ...
everything worked fine.
Now I'll have to fix my qt5.SlackBuild and rebuild and reinstall qt5
By the way these lines (in qtox.SlackBuild from slackbuilds.org) can be safely deleted:
Code:
# Prevent multilib interference
if [ "$ARCH" = "x86_64" ]; then
sed -i '/\/usr\/lib\/glib-2.0\/include/d' qtox.pro
sed -i '/\/usr\/lib\/gtk-2.0\/include/d' qtox.pro
fi
I built and installed qtox on slackware 14.2 without a hitch (after I rebuilt and reinstalled qt5).
Also on my slackware 14.1 system I built/installed utox (for that,
you need to add to the list of dependencies, mentioned earlier, lipvx
(should be installed before you start building toxcore).
lipvx is part of the slackware 14.2 distribution
I built and installed qtox on slackware 14.2 without a hitch (after I rebuilt and reinstalled qt5).
Also on my slackware 14.1 system I built/installed utox (for that,
you need to add to the list of dependencies, mentioned earlier, lipvx
(should be installed before you start building toxcore).
lipvx is part of the slackware 14.2 distribution
So is there any really visible or functional differences between uTox and qTox?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.