|
OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
Tox clients in OpenBSD?
Hello to everyone there!
Well. My question is: Does anybody knows if Tox clients are installable in OpenBSD? Would it work by running the Source Code? If is that possible, how can I make it? Thanks for your time! |
|
|||
Quote:
Quote:
Applications fall into two categories -- either they are compiled or interpreted.
From what I can see, Tox is a peer-to-peer messaging system -- a slight variation of more familiar XMPP applications such as net/prosody (which is an interpreted Python application...). While I understand their statements about "increased security", I would think that an XMPP application running over IPSec links would be as secure, if not more so. In other threads, I see where you have stated that you do not have development experience. To successfully port an application to OpenBSD requires substantial knowledge, patience, & tenacity. You might see this as a personal challenge to learning new skills. If you decide not to pursue this task, you might be better served by exploring what applications already have been officially ported to OpenBSD. http://openports.se/ may be a good site for searching for existing applications already ported to OpenBSD. |
|
||||
I am aware of two Tox-related ports in development for OpenBSD. There is a port of Toxic in development, and it is dependent on the toxcore library, also in development. There is a TODO file for the work-in-progress OpenBSD port of toxcore which states:
Quote:
I have just searched with Google and noted one discussion of a test of a uTox/Toxic builds on OpenBSD, with some success and some outstanding issues. Last edited by jggimi; 29th June 2016 at 12:02 AM. Reason: typo |
|
|||
Thanks, and thanks! Well, that is good information.
I should wait that someone develop a Tox client for OpenBSD. I was wondering if is it possible to use a port from FreeBSD. Am I mad? Can it be done? |
|
|||
The package system used by FreeBSD is different than that used by OpenBSD. They are not compatible.
|
|
||||
You might have more success building and running the work-in-progress ports I mentioned above. They are among the many ports available at https://github.com/jasperla/openbsd-wip
See the README.md file on that web page for information about this collection of uncommitted ports, by paging down on the web page or clicking here: https://github.com/jasperla/openbsd-...ster/README.md --- You may want to review the OpenBSD FAQ on packages and ports: http://www.openbsd.org/faq/faq15.html If you want to develop an OpenBSD port, perhaps based on a FreeBSD port, you will need to use the OpenBSD Porter's Handbook: http://www.openbsd.org/faq/ports/index.html Within the Handbook is the Port Testing Guide, which you should use when building and installing any work-in-progress port: http://www.openbsd.org/faq/ports/testing.html |
|
|||
Thank you for all your recommendations!
I will see what I can do! |
|
|||
uTox 0.15.0 and newer has experimental support for OpenBSD.
Also to compile uTox 0.16.0 and newer, you have to install uTox's version of toxcore https://github.com/uTox/toxcore Also if a gtk filepicker doesn't work (versions older than 0.16.0), in src/xlib/gtk.c change #define LIBGTK_FILENAME "libgtk-3.so.blablabla" to #define LIBGTK_FILENAME "libgtk-3.so" If you would like to run a stable uTox, compile uTox 0.11.1: you'll need patches from FreeBSD https://github.com/freebsd/freebsd-p...-im/uTox/files In src/main.c instead of "#if !defined(__OBJC__) || defined(__NetBSD__) || defined(__FreeBSD__)" write "#if !defined(__OBJC__) || defined(__OpenBSD__)" I hope I've helped, but still I prefer toxic and toxcore which openbsd-wip provides, it's sad that they won't get in OpenBSD ports. Also note that openal doesn't currently support sndio input, so you won't be able to talk in audio calls (but you'll hear everyone because openal supports sndio output, that's weird). If you would like to do videocalls (I tested only desktop sharing), uTox 0.16.0 and newer will crash at any OS. Last edited by puffymon; 29th April 2018 at 11:42 AM. Reason: I changed my toxid due to harm which I accidentally made to filesystem, again -_- |
|
|||
btw I forgot to mention that compiling uTox 0.11.1 may require you to manually add some flags to compiler (include paths to local and X11 environments and lib paths to local and X11 environments) and remove 'dl' and 'resolv' libraries from CMakeLists.txt because OpenBSD's libc provides them.
|
|
|||
Now Toxic officially supports OpenBSD https://github.com/JFreegman/toxic/pull/468
Besides current uTox has a video preview fix and it builds with c-toxcore, so I recommend to try it
__________________
mazocomp$ uname -a OpenBSD mazocomp.lan 6.3 GENERIC.MP#47 amd64 mazocomp$ |
|
|||
Good news!
Tox core, Toxic and uTox are finally at ports tree! Commits which made a difference (yes, I am maintainer): https://marc.info/?l=openbsd-ports-c...0045705397&w=2 https://marc.info/?l=openbsd-ports-c...0052105440&w=2 https://marc.info/?l=openbsd-ports-c...0059805471&w=2 https://marc.info/?l=openbsd-ports-c...0079605542&w=2 https://marc.info/?l=openbsd-ports-c...0086505580&w=2 My new toxid is BC252E4D78BADE36A9DED84CD55A872082282E1A425C77403C 5170642533EC27910AC1B25BBB You are free to contact me.
__________________
mazocomp$ uname -a OpenBSD mazocomp.lan 6.3 GENERIC.MP#47 amd64 mazocomp$ |
Tags |
tox |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
How to use the external interface and a VPN tunnel for different services/clients? | alikzus | OpenBSD Security | 1 | 26th June 2014 10:29 AM |
evdo on server: clients can ping www, but not browse | amorphousone | OpenBSD Security | 2 | 24th September 2010 04:56 AM |
torrent clients are driving me nuts | graudeejs | FreeBSD General | 28 | 9th January 2009 12:43 PM |
FreeBSD server, Windows clients, daily backups | Weaseal | FreeBSD General | 4 | 25th December 2008 05:50 PM |
Exempting clients from AuthPF | Kristijan | NetBSD Security | 1 | 12th July 2008 12:09 AM |