DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD Packages and Ports

OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 28th June 2016
Nureo Nureo is offline
Sam98
 
Join Date: May 2016
Posts: 24
Question 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!
Reply With Quote
  #2   (View Single Post)  
Old 28th June 2016
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 3,277
Default

Quote:
Originally Posted by Nureo View Post
Does anybody knows if Tox clients are installable in OpenBSD?
This application has not previously been officially ported to OpenBSD. If you want to run this application on OpenBSD, you may want to consider porting it yourself.
Quote:
Would it work by running the Source Code?
In looking at the GitHub repository, it appears that this application is a C++ application primarily using Qt5 as the GUI interface.

Applications fall into two categories -- either they are compiled or interpreted.
  • Compiled applications consist of one or more source files which are translated into binary instructions understood by the operating system (boot-up code) & processor.(application logic). A developer will translate source code into binary instructions through a compiler. The resulting binary image created by the compiler is executed directly by users as the application itself.
  • Interpreted applications are executed directly as the application by an interpreter. Every time the application is executed, the interpreter will translate the source into binary instructions which are immediately executed. In general, interpreted applications run slower than compiled applications because of the runtime overhead of real-time translation of source code.
The application I find on GitHub is C++ code which is a compiled language. If you want to run Tox on OpenBSD, you will need to figure out whether the source can simply be compiled through the tools provided, or whether you will have to modify the source code before compiling something which is recognizable by OpenBSD. This might be as simple as an evening's work. It may be as complicated as months of work.

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.
Reply With Quote
  #3   (View Single Post)  
Old 28th June 2016
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 5,934
Default

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:
The port is basically ready, but upstream discourages packaging because of API
instability. Probably this port should stage here ATM.
ATM is short for "At the Moment." The TODO file was posted one year ago.

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
Reply With Quote
  #4   (View Single Post)  
Old 1st July 2016
Nureo Nureo is offline
Sam98
 
Join Date: May 2016
Posts: 24
Default

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?
Reply With Quote
  #5   (View Single Post)  
Old 1st July 2016
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 3,277
Default

Quote:
Originally Posted by Nureo View Post
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.
Reply With Quote
  #6   (View Single Post)  
Old 1st July 2016
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 5,934
Default

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
Reply With Quote
  #7   (View Single Post)  
Old 15th July 2016
Nureo Nureo is offline
Sam98
 
Join Date: May 2016
Posts: 24
Default

Thank you for all your recommendations!

I will see what I can do!
Reply With Quote
  #8   (View Single Post)  
Old 17th September 2017
puffymon puffymon is offline
Real Name: Leonid
Port Guard
 
Join Date: Apr 2017
Location: Earth
Posts: 30
Default

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.
btw, I'd like to chat, so here is my toxid: 0F09F10750FF5FE90D80290ADCC10CBEB27BCEC449101195DC 0852A39AB5674DDDFB58D4D7AB

Last edited by puffymon; 2 Weeks Ago at 02:36 AM. Reason: I changed my toxid due to harm which I accidentally made to filesystem
Reply With Quote
  #9   (View Single Post)  
Old 17th September 2017
puffymon puffymon is offline
Real Name: Leonid
Port Guard
 
Join Date: Apr 2017
Location: Earth
Posts: 30
Default

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.
Reply With Quote
Old 6 Days Ago
puffymon puffymon is offline
Real Name: Leonid
Port Guard
 
Join Date: Apr 2017
Location: Earth
Posts: 30
Default

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
__________________
$ uname -a
OpenBSD puffy.pc 6.2 GENERIC.MP#146 amd64
$
Reply With Quote
Reply

Tags
tox

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

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


All times are GMT. The time now is 04:21 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick