# layman -f && layman -a tox-overlay && emerge net-libs/tox
And you're done
If you happen to run some other distro which isn't made for compiling, there are steps below:
Note: package fetching commands may vary by OS.
< 15.04 / Debian
sudo apt-get install build-essential libtool autotools-dev automake checkinstall check git yasm
>= 15.04 / Debian
sudo apt-get install build-essential libtool autotools-dev automake checkinstall check git yasm libsodium13 libsodium-dev
dnf groupinstall "Development Tools" dnf install libtool autoconf automake check check-devel
dnf install @"Development Tools" is also valid and slightly shorter / cleaner way.
@"Rpm Development Tools" would carry the remaining dependencies listed here.
pkg install autoconf automake gcc-47
On FreeBSD 10+:
pkg install net-im/tox
Note, if you install from ports select NaCl for performance, and sodium if you want it to be portable.
For A/V support, also install the dependences listed in the libtoxav section. Note that you have to install those dependencies before compiling
You should get and install libsodium. If you have installed
libsodium from repo, ommit this step, and jump directly to compiling toxcore:
git clone https://github.com/jedisct1/libsodium.git cd libsodium git checkout tags/1.0.3 ./autogen.sh ./configure && make check sudo checkinstall --install --pkgname libsodium --pkgversion 1.0.0 --nodoc sudo ldconfig cd ..
Or if checkinstall is not easily available for your distribution (e.g., Fedora), this will install the libs to /usr/local/lib and the headers to /usr/local/include:
git clone https://github.com/jedisct1/libsodium.git cd libsodium git checkout tags/1.0.3 ./autogen.sh ./configure make check sudo make install cd ..
If your default prefix is
/usr/local and you happen to get an error that says
"error while loading shared libraries: libtoxcore.so.0: cannot open shared object file: No such file or directory", then you can try running
sudo ldconfig. If that doesn't fix it, run:
echo '/usr/local/lib/' | sudo tee -a /etc/ld.so.conf.d/locallib.conf sudo ldconfig
You may run into a situation where there is no
/etc/ld.so.conf.d directory. You could either create it manually, or append path to local library to
echo '/usr/local/lib/' | sudo tee -a /etc/ld.so.conf sudo ldconfig
Then clone this repo, generate makefile, and install
git clone https://github.com/irungentoo/toxcore.git cd toxcore autoreconf -i ./configure make sudo make install
You need the latest XCode with the Developer Tools (Preferences -> Downloads -> Command Line Tools). The following libraries are required along with libsodium and cmake for Mountain Lion and XCode 4.6.3 install libtool, automake and autoconf. You can download them with Homebrew, or install them manually.
Note: OS X users can also install Toxcore using osx_build_script_toxcore.sh
There are no binaries/executables going to /bin/ or /usr/bin/ now. Everything is compiled and ran from the inside your local branch. See Usage below. ####Homebrew: To install from the formula:
brew tap Tox/tox brew install --HEAD libtoxcore
To do it manually:
brew install libtool automake autoconf libsodium check
Then clone this repo and generate makefile:
git clone https://github.com/irungentoo/toxcore.git cd toxcore autoreconf -i ./configure make make install
If execution fails with errors like "dyld: Library not loaded: /opt/tox-im/lib/libtoxcore.0.dylib", you may need to specify libsodium path:
brew list libsodium
Configure include and lib folder and build again:
./configure --with-libsodium-headers=/usr/local/Cellar/libsodium/1.0.0/include/ --with-libsodium-libs=/usr/local/Cellar/libsodium/1.0.0/lib/ make make install
Grab the following packages:
- http://yasm.tortall.net/Download.html (install before libvpx)
Macports: (https://www.macports.org/) All toxcore dependencies can be installed from MacPorts. This is often easier on PowerPC Macs, and any version of OS X prior to 10.6, since Homebrew is supported on 10.6 and up, but not much (or at all) on older systems. A few packages have slightly different names from the corresponding package in Debian.
Same: libtool autoconf automake libsodium check yasm Different: libvpx (webm) libopus pkgconfig gettext
(the libintl, from gettext, built into OS X 10.5 is missing libintl_setlocale, but the Macports build has it)
Verify where libintl is on your system: (MacPorts puts it in /opt/local)
for d in /usr/local/lib /opt/local/lib /usr/lib /lib; do ls -l $d/libintl.*; done
Check if that copy has libintl_setlocale:
nm /opt/local/lib/libintl.8.dylib | grep _libintl_setlocale
Certain other tools may not be installed, or outdated, and should also be installed from MacPorts for simplicity: git cmake
If libsodium was installed with MacPorts, you may want to symlink the copy in /opt/local/lib to /usr/local/lib. That way you don't need special configure switches for toxcore to find libsodium, and every time MacPorts updates libsodium, the new version will be linked to toxcore every time you build:
ln -s /opt/local/lib/libsodium.dylib /usr/local/lib/libsodium.dylib
Much of the build can then be done as for other platforms: git clone, and so on. Differences will be noted with (OS X 10.5 specific)
pkg-config is important for enabling a/v support in tox core, failure to install pkg-config will prevent tox core form finding the required libopus/libvpx libraries. (pkg-config may not configure properly, if you get an error about GLIB, run configure with the following parameter, --with-internal-glib).
Uncompress and install them all. Make sure to follow the README as the instructions change, but they all follow the same pattern below:
./configure make sudo make install
Compiling and installing Tox Core
cd toxcore autoreconf -i ./configure (OS X 10.5 specific) ./configure CC="gcc -arch ppc -arch i386" CXX="g++ -arch ppc -arch i386" CPP="gcc -E" CXXCPP="g++ -E" make make install (OS X 10.5 specific) should be: sudo make install If it worked, you should have all the toxcore dylibs in /usr/local/lib: (besides the four below, the rest are symlinks to these) $ ls -la /usr/local/lib/libtox*.dylib libtoxav.0.dylib libtoxcore.0.dylib libtoxdns.0.dylib libtoxencryptsave.0.dylib to check what CPU architecture they're compiled for: $ lipo -i /usr/local/lib/libtoxencryptsave.0.dylib You should now be able to move on to compiling Toxic/Venom or some other client application There is also a shell script called "osx_build_script_toxcore.txt" which automates everything from "git pull" to "sudo make install", once the dependencies are already taken care of by MacPorts.
If after running ./configure you get an error about core being unable to find libsodium (and you have installed it) run the following in place of ./configure;
./configure --with-libsodium-headers=/usr/local/include/ --with-libsodium-libs=/usr/local/lib
Ensure you set the locations correctly depending on where you installed libsodium on your computer.
If there is a problem with opus (for A/V) and you don't get a libtoxav, then try to set the pkg-config environment variable beforehand:
It's a bit challenging to build Tox and all of its dependencies nativly on Windows, so we will show an easier, less error and headache prone method of building it -- cross-compiling.#####Setting up a VM
We will assume that you don't have any VM running Linux around and will guide you from the ground up.
First, you would need to get a virtual machine and a Linux distribution image file.
For a virtual machine we will use VirtualBox. You can get it here.
For a Linux distribution we will use Lubuntu 14.04 32-bit, which you can get here.
After you have those downloaded, install the VirtualBox and create a VM in it. The default of 512mb of RAM and 8gb of dynamically-allocated virtual hard drive would be enough.
When you have created the VM, go into its Settings -> System -> Processor and add some cores, if you have any additional available, for faster builds.
Then, go to Settings -> Storage, click on Empty under Controller: IDE, click on the little disc icon on the right side of the window, click on Choose a virtual CD/DVD disk file and select the downloaded Lubuntu image file.
Start the VM and follow the installation instructions.
After Lubuntu is installed and you have booted into it, in VirtualBox menu on top of the window select Devices -> Insert Guest Additions CD image....
Open terminal from Lubuntu's menu -> Accessories.
sudo apt-get update sudo apt-get install build-essential -y cd /media/*/*/ sudo ./VBoxLinuxAdditions.run
After that, create a folder called
toxbuild somewhere on your Windows system. The go to Devices -> Shared Folders Settings... in the VirtualBox menu, add the
toxbuild folder there and set Auto-mount and Make Permanent options.
sudo adduser `whoami` vboxsf
Note the use of a grave accent instead of an apostrophe.
Then just reboot the system with:
After the system is booted, go to Devices -> Shared Clipboard and select Bidirectional. Now you will be able to copy-paste text between the host and the guest systems.
Now that the virtual machine is all set up, let's move to getting build dependencies and setting up environment variables.#####Setting up the environment
First we will install all tools that we would need for building:
sudo apt-get install build-essential libtool autotools-dev automake checkinstall check git yasm pkg-config mingw-w64 -y
Then we will define a few variables, depending on which you will build either 32-bit or 64-bit Tox.
For 32-bit Tox build, do:
For 64-bit Tox build, do:
This is the only difference between 32-bit and 64-bit build procedures.
For speeding up the build process do:
MAKEFLAGS=j$(nproc) export MAKEFLAGS
And let's make a folder where we will be building everything at
cd ~ mkdir prefix cd prefix PREFIX_DIR=$(pwd) cd .. mkdir build cd build
Now we will build libraries needed for audio/video: VPX and Opus.
git clone https://chromium.googlesource.com/webm/libvpx cd libvpx git checkout tags/v1.3.0 CROSS="$WINDOWS_TOOLCHAIN"- ./configure --target="$LIB_VPX_TARGET" --prefix="$PREFIX_DIR" --disable-examples --disable-unit-tests --disable-shared --enable-static make make install cd ..
wget http://downloads.xiph.org/releases/opus/opus-1.1.tar.gz tar -xf opus-1.1.tar.gz cd opus-1.1 ./configure --host="$WINDOWS_TOOLCHAIN" --prefix="$PREFIX_DIR" --disable-extra-programs --disable-doc --disable-shared --enable-static make make install cd ..
Now we will build sodium crypto library:
git clone https://github.com/jedisct1/libsodium/ cd libsodium git checkout tags/1.0.3 ./autogen.sh ./configure --host="$WINDOWS_TOOLCHAIN" --prefix="$PREFIX_DIR" --disable-shared --enable-static make make install cd ..
And finally we will build Tox:
git clone https://github.com/irungentoo/toxcore cd toxcore ./autogen.sh ./configure --host="$WINDOWS_TOOLCHAIN" --prefix="$PREFIX_DIR" --disable-ntox --disable-tests --disable-testing --with-dependency-search="$PREFIX_DIR" --disable-shared --enable-static make make install cd ..
Then we make Tox shared library:
cd "$PREFIX_DIR" mkdir tmp cd tmp $WINDOWS_TOOLCHAIN-ar x ../lib/libtoxcore.a $WINDOWS_TOOLCHAIN-ar x ../lib/libtoxav.a $WINDOWS_TOOLCHAIN-ar x ../lib/libtoxdns.a $WINDOWS_TOOLCHAIN-ar x ../lib/libtoxencryptsave.a $WINDOWS_TOOLCHAIN-gcc -Wl,--export-all-symbols -Wl,--out-implib=libtox.dll.a -shared -o libtox.dll *.o ../lib/*.a /usr/$WINDOWS_TOOLCHAIN/lib/libwinpthread.a -liphlpapi -lws2_32 -static-libgcc
And we will copy it over to the
mkdir -p /media/sf_toxbuild/release/lib cp libtox.dll.a /media/sf_toxbuild/release/lib mkdir -p /media/sf_toxbuild/release/bin cp libtox.dll /media/sf_toxbuild/release/bin mkdir -p /media/sf_toxbuild/release/include cp -r ../include/tox /media/sf_toxbuild/release/include
That's it. Now you should have
release/include/tox/<headers> in your
toxbuild directory on the Windows system.
Note that the Native instructions are incomplete, in a sense that they miss instructions needed for adding audio/video support to Tox. You also might stumble upon some unknown MinGW+msys issues while trying to build it.
You should install:
When installing MinGW, make sure to select the MSYS option in the installer. MinGW will install an "MinGW shell" (you should get a shortcut for it), make sure to perform all operations (i.e., generating/running configure script, compiling, etc.) from the MinGW shell.
First download the source tarball from https://download.libsodium.org/libsodium/releases/ and build it. Assuming that you got the libsodium-1.0.0.tar.gz release:
tar -zxvf libsodium-1.0.0.tar.gz cd libsodium-1.0.0 ./configure make make install cd ..
You can also use a precompiled win32 binary of libsodium, however you will have to place the files in places where they can be found, i.e., dll's go to /bin headers to /include and libraries to /lib directories in your MinGW shell.
Next, install toxcore library, should either clone this repo by using git, or just download a zip of current Master branch and extract it somewhere.
Assuming that you now have the sources in the toxcore directory:
cd toxcore autoreconf -i ./configure make make install
- --enable-silent-rules less verbose build output (undo: "make V=1")
- --disable-silent-rules verbose build output (undo: "make V=0")
- --disable-tests build unit tests (default: auto)
- --disable-av disable A/V support (default: auto) see: libtoxav
- --enable-ntox build nTox client (default: no) see: nTox
- --enable-daemon build DHT bootstrap daemon (default=no) see: Bootstrap daemon
- --enable-shared[=PKGS] build shared libraries [default=yes]
- --enable-static[=PKGS] build static libraries [default=yes]
'libtoxav' is needed for A/V support and it's enabled by default. You can disable it by adding --disable-av argument to ./configure script like so:
There are 2 dependencies required for libtoxav: libopus and libvpx. If they are not installed A/V support is dropped.
Install on fedora:
yum install opus-devel libvpx-devel
Install on ubuntu:
sudo apt-get install libopus-dev libvpx-dev pkg-config
If you get the "Unable to locate package libopus-dev" message, add the following ppa and try again:
sudo add-apt-repository ppa:ubuntu-sdk-team/ppa && sudo apt-get update && sudo apt-get dist-upgrade
Install from source (example for most unix-like OS's):
git clone https://chromium.googlesource.com/webm/libvpx cd libvpx ./configure make -j3 sudo make install cd ..
wget http://downloads.xiph.org/releases/opus/opus-1.0.3.tar.gz tar xvzf opus-1.0.3.tar.gz cd opus-1.0.3 ./configure make -j3 sudo make install cd ..
Daemon is disabled by default. You can enable it by adding --enable-daemon argument to ./configure script like so:
There is one dependency required for bootstrap daemon:
libconfig-dev >= 1.4.
Install on fedora:
yum install libconfig-devel
Install on ubuntu:
sudo apt-get install libconfig-dev
OS X homebrew:
brew install libconfig
OS X non-homebrew: Grab the following package, uncompress and install
See this readme on how to set up the bootstrap daemon.###nTox test cli:
nTox is disabled by default. You can enable it by adding --enable-ntox argument to ./configure script like so:
There is one dependency required for nTox: libncurses.
Install on fedora:
yum install ncurses-devel
Install on ubuntu:
sudo apt-get install ncurses-dev