ffi-tox 0.1.1 → 0.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 1ea0d69f0ac06a753a7fb1299542b5f5ebfe935d
-  data.tar.gz: ecbc2f0a1fec17416aa57890fe6be315225d7d18
+  metadata.gz: 6b4b48b6ca2fc3e8f79346e6f27dcab40e701f39
+  data.tar.gz: 4446b08f8f799dd4683a75ad8d32ed0401137ee3
 SHA512:
-  metadata.gz: 68ae7ba6278cb10d41dbe042f59d10304444b25ef7802c0c19919e3ca63a93c86efb6cb5af63cb979906da9f6cacab43ddf85a434092bd550ed41151dbe7ff01
-  data.tar.gz: 678b27211d2dd376c8ee8d631c2f44b8da2b9039c68fa535e36bfeeb06dab5554cbc286b356183053fc5d6e61031e1a2f67e429c839bce17f14086bca6a28a41
+  metadata.gz: ffc13e740231617cff037e4377a909d19cc2103d1aedcc6a1a06cc4ba70c45130f35e579bac4055ca28a7632c765af95e66b73adb8632bec50a6952cd57ec2af
+  data.tar.gz: a6c6bab6fe9737cb9ca498e50c6b4ba4abfabdb31f8e05dd38375ac80594458abeaaf974d56a2153af9352b686437da805fa0b1f88a870ba8056306d8e7a6e01

data/ProjectTox-Core/INSTALL

@@ -0,0 +1,370 @@
+Installation Instructions
+*************************
+
+Copyright (C) 1994-1996, 1999-2002, 2004-2013 Free Software Foundation,
+Inc.
+
+   Copying and distribution of this file, with or without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved.  This file is offered as-is,
+without warranty of any kind.
+
+Basic Installation
+==================
+
+   Briefly, the shell commands `./configure; make; make install' should
+configure, build, and install this package.  The following
+more-detailed instructions are generic; see the `README' file for
+instructions specific to this package.  Some packages provide this
+`INSTALL' file but do not implement all of the features documented
+below.  The lack of an optional feature in a given package is not
+necessarily a bug.  More recommendations for GNU packages can be found
+in *note Makefile Conventions: (standards)Makefile Conventions.
+
+   The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation.  It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions.  Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+   It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring.  Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.
+
+   If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release.  If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+   The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'.  You need `configure.ac' if
+you want to change it or regenerate `configure' using a newer version
+of `autoconf'.
+
+   The simplest way to compile this package is:
+
+  1. `cd' to the directory containing the package's source code and type
+     `./configure' to configure the package for your system.
+
+     Running `configure' might take a while.  While running, it prints
+     some messages telling which features it is checking for.
+
+  2. Type `make' to compile the package.
+
+  3. Optionally, type `make check' to run any self-tests that come with
+     the package, generally using the just-built uninstalled binaries.
+
+  4. Type `make install' to install the programs and any data files and
+     documentation.  When installing into a prefix owned by root, it is
+     recommended that the package be configured and built as a regular
+     user, and only the `make install' phase executed with root
+     privileges.
+
+  5. Optionally, type `make installcheck' to repeat any self-tests, but
+     this time using the binaries in their final installed location.
+     This target does not install anything.  Running this target as a
+     regular user, particularly if the prior `make install' required
+     root privileges, verifies that the installation completed
+     correctly.
+
+  6. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  To also remove the
+     files that `configure' created (so you can compile the package for
+     a different kind of computer), type `make distclean'.  There is
+     also a `make maintainer-clean' target, but that is intended mainly
+     for the package's developers.  If you use it, you may have to get
+     all sorts of other programs in order to regenerate files that came
+     with the distribution.
+
+  7. Often, you can also type `make uninstall' to remove the installed
+     files again.  In practice, not all packages have tested that
+     uninstallation works correctly, even though it is required by the
+     GNU Coding Standards.
+
+  8. Some packages, particularly those that use Automake, provide `make
+     distcheck', which can by used by developers to test that all other
+     targets like `make install' and `make uninstall' work correctly.
+     This target is generally not run by end users.
+
+Compilers and Options
+=====================
+
+   Some systems require unusual options for compilation or linking that
+the `configure' script does not know about.  Run `./configure --help'
+for details on some of the pertinent environment variables.
+
+   You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment.  Here
+is an example:
+
+     ./configure CC=c99 CFLAGS=-g LIBS=-lposix
+
+   *Note Defining Variables::, for more details.
+
+Compiling For Multiple Architectures
+====================================
+
+   You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory.  To do this, you can use GNU `make'.  `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script.  `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.  This
+is known as a "VPATH" build.
+
+   With a non-GNU `make', it is safer to compile the package for one
+architecture at a time in the source code directory.  After you have
+installed the package for one architecture, use `make distclean' before
+reconfiguring for another architecture.
+
+   On MacOS X 10.5 and later systems, you can create libraries and
+executables that work on multiple system types--known as "fat" or
+"universal" binaries--by specifying multiple `-arch' options to the
+compiler but only a single `-arch' option to the preprocessor.  Like
+this:
+
+     ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+                 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+                 CPP="gcc -E" CXXCPP="g++ -E"
+
+   This is not guaranteed to produce working output in all cases, you
+may have to build one architecture at a time and combine the results
+using the `lipo' tool if you have problems.
+
+Installation Names
+==================
+
+   By default, `make install' installs the package's commands under
+`/usr/local/bin', include files under `/usr/local/include', etc.  You
+can specify an installation prefix other than `/usr/local' by giving
+`configure' the option `--prefix=PREFIX', where PREFIX must be an
+absolute file name.
+
+   You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files.  If you
+pass the option `--exec-prefix=PREFIX' to `configure', the package uses
+PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files still use the regular prefix.
+
+   In addition, if you use an unusual directory layout you can give
+options like `--bindir=DIR' to specify different values for particular
+kinds of files.  Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.  In general, the
+default for these options is expressed in terms of `${prefix}', so that
+specifying just `--prefix' will affect all of the other directory
+specifications that were not explicitly provided.
+
+   The most portable way to affect installation locations is to pass the
+correct locations to `configure'; however, many packages provide one or
+both of the following shortcuts of passing variable assignments to the
+`make install' command line to change installation locations without
+having to reconfigure or recompile.
+
+   The first method involves providing an override variable for each
+affected directory.  For example, `make install
+prefix=/alternate/directory' will choose an alternate location for all
+directory configuration variables that were expressed in terms of
+`${prefix}'.  Any directories that were specified during `configure',
+but not in terms of `${prefix}', must each be overridden at install
+time for the entire installation to be relocated.  The approach of
+makefile variable overrides for each directory variable is required by
+the GNU Coding Standards, and ideally causes no recompilation.
+However, some platforms have known limitations with the semantics of
+shared libraries that end up requiring recompilation when using this
+method, particularly noticeable in packages that use GNU Libtool.
+
+   The second method involves providing the `DESTDIR' variable.  For
+example, `make install DESTDIR=/alternate/directory' will prepend
+`/alternate/directory' before all installation names.  The approach of
+`DESTDIR' overrides is not required by the GNU Coding Standards, and
+does not work on platforms that have drive letters.  On the other hand,
+it does better at avoiding recompilation issues, and works well even
+when some directory options were not specified in terms of `${prefix}'
+at `configure' time.
+
+Optional Features
+=================
+
+   If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+   Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System).  The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+   For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+   Some packages offer the ability to configure how verbose the
+execution of `make' will be.  For these packages, running `./configure
+--enable-silent-rules' sets the default to minimal output, which can be
+overridden with `make V=1'; while running `./configure
+--disable-silent-rules' sets the default to verbose, which can be
+overridden with `make V=0'.
+
+Particular systems
+==================
+
+   On HP-UX, the default C compiler is not ANSI C compatible.  If GNU
+CC is not installed, it is recommended to use the following options in
+order to use an ANSI C compiler:
+
+     ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
+
+and if that doesn't work, install pre-built binaries of GCC for HP-UX.
+
+   HP-UX `make' updates targets which have the same time stamps as
+their prerequisites, which makes it generally unusable when shipped
+generated files such as `configure' are involved.  Use GNU `make'
+instead.
+
+   On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
+parse its `<wchar.h>' header file.  The option `-nodtk' can be used as
+a workaround.  If GNU CC is not installed, it is therefore recommended
+to try
+
+     ./configure CC="cc"
+
+and if that doesn't work, try
+
+     ./configure CC="cc -nodtk"
+
+   On Solaris, don't put `/usr/ucb' early in your `PATH'.  This
+directory contains several dysfunctional programs; working variants of
+these programs are available in `/usr/bin'.  So, if you need `/usr/ucb'
+in your `PATH', put it _after_ `/usr/bin'.
+
+   On Haiku, software installed for all users goes in `/boot/common',
+not `/usr/local'.  It is recommended to use the following options:
+
+     ./configure --prefix=/boot/common
+
+Specifying the System Type
+==========================
+
+   There may be some features `configure' cannot figure out
+automatically, but needs to determine by the type of machine the package
+will run on.  Usually, assuming the package is built to be run on the
+_same_ architectures, `configure' can figure that out, but if it prints
+a message saying it cannot guess the machine type, give it the
+`--build=TYPE' option.  TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+
+     CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+     OS
+     KERNEL-OS
+
+   See the file `config.sub' for the possible values of each field.  If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+
+   If you are _building_ compiler tools for cross-compiling, you should
+use the option `--target=TYPE' to select the type of system they will
+produce code for.
+
+   If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+
+Sharing Defaults
+================
+
+   If you want to set default values for `configure' scripts to share,
+you can create a site shell script called `config.site' that gives
+default values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists.  Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Defining Variables
+==================
+
+   Variables not defined in a site shell script can be set in the
+environment passed to `configure'.  However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost.  In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'.  For example:
+
+     ./configure CC=/usr/local2/bin/gcc
+
+causes the specified `gcc' to be used as the C compiler (unless it is
+overridden in the site shell script).
+
+Unfortunately, this technique does not work for `CONFIG_SHELL' due to
+an Autoconf limitation.  Until the limitation is lifted, you can use
+this workaround:
+
+     CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash
+
+`configure' Invocation
+======================
+
+   `configure' recognizes the following options to control how it
+operates.
+
+`--help'
+`-h'
+     Print a summary of all of the options to `configure', and exit.
+
+`--help=short'
+`--help=recursive'
+     Print a summary of the options unique to this package's
+     `configure', and exit.  The `short' variant lists options used
+     only in the top level, while the `recursive' variant lists options
+     also present in any nested packages.
+
+`--version'
+`-V'
+     Print the version of Autoconf used to generate the `configure'
+     script, and exit.
+
+`--cache-file=FILE'
+     Enable the cache: use and save the results of the tests in FILE,
+     traditionally `config.cache'.  FILE defaults to `/dev/null' to
+     disable caching.
+
+`--config-cache'
+`-C'
+     Alias for `--cache-file=config.cache'.
+
+`--quiet'
+`--silent'
+`-q'
+     Do not print messages saying which checks are being made.  To
+     suppress all normal output, redirect it to `/dev/null' (any error
+     messages will still be shown).
+
+`--srcdir=DIR'
+     Look for the package's source code in directory DIR.  Usually
+     `configure' can determine that directory automatically.
+
+`--prefix=DIR'
+     Use DIR as the installation prefix.  *note Installation Names::
+     for more details, including other options available for fine-tuning
+     the installation locations.
+
+`--no-create'
+`-n'
+     Run the configure checks, but stop before creating any output
+     files.
+
+`configure' also accepts some other, not widely useful, options.  Run
+`configure --help' for more details.

data/ProjectTox-Core/INSTALL.md

@@ -1,78 +1,167 @@
 #Install Instructions
 
 - [Installation](#installation)
-    - [Linux](#linux)
-    - [OS X](#osx)
-      - [Homebrew](#homebrew)
-      - [Non-Homebrew](#non-homebrew)
-    - [Windows](#windows)
-- [Usage](#usage)
+  - [Unix like](#unix)
+  - [OS X](#osx)
+    - [Homebrew](#homebrew)
+    - [Non-Homebrew](#non-homebrew)
+  - [Windows](#windows)
+    - [Cross-Compile](#windows-cross-compile)
+      - [Setting up a VM](#windows-cross-compile-vm)
+      - [Setting up the environment](#windows-cross-compile-environment)
+      - [Compiling](#windows-cross-compile-compiling)
+    - [Native](#windows-native)
+- [Additional](#additional)
+  - [Advanced configure options](#aconf)
+  - [A/V support](#av)
+    - [libtoxav](#libtoxav)
+  - [Bootstrap daemon](#bootstrapd)
+  - [nTox](#ntox)
 
 <a name="installation" />
 ##Installation
 
-<a name="linux" />
-###Linux:
+<a name="unix" />
+###Most Unix like OSes:
 
 Build dependencies:
 
+Note: package fetching commands may vary by OS.
+
+On Ubuntu:
+
 ```bash
-apt-get install build-essential libtool autotools-dev automake libconfig-dev ncurses-dev cmake checkinstall
+sudo apt-get install build-essential libtool autotools-dev automake checkinstall check git yasm
 ```
-Note that `libconfig-dev` should be >= 1.4.
+
+On Fedora:
+
+```bash
+yum groupinstall "Development Tools"
+yum install libtool autoconf automake check check-devel
+```
+
+On SunOS:
+
+```pfexcec
+pkg install autoconf automake gcc-47
+```
+On FreeBSD 10+:
+
+```tcsh
+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] (#libtoxav) section.**
 
 You should get and install [libsodium](https://github.com/jedisct1/libsodium):
 ```bash
 git clone git://github.com/jedisct1/libsodium.git
 cd libsodium
-git checkout tags/0.4.2
+git checkout tags/0.7.0
 ./autogen.sh
 ./configure && make check
-sudo checkinstall --install --pkgname libsodium --pkgversion 0.4.2 --nodoc
+sudo checkinstall --install --pkgname libsodium --pkgversion 0.7.0 --nodoc
 sudo ldconfig
+cd ..
 ```
 
-Then clone this repo and generate makefile:
+
+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:
+
 ```bash
-git clone git://github.com/irungentoo/ProjectTox-Core.git
-cd ProjectTox-Core
-mkdir build && cd build
-cmake ..
+git clone git://github.com/jedisct1/libsodium.git
+cd libsodium
+git checkout tags/0.7.0
+./autogen.sh
+./configure
+make check
+sudo make install
+cd ..
 ```
-Note that you should call cmake on the root [`CMakeLists.txt`](/CMakeLists.txt) file only.
 
-Then you can build any of the [`/testing`](/testing) and [`/other`](/other) that are currently supported on your platform by running:
-```bash
-make name_of_c_file
+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:
 ```
-For example, to build [`Messenger_test.c`](/others/Messenger_test.c) you would run:
-```bash
-make Messenger_test
+echo '/usr/local/lib/' | sudo tee -a /etc/ld.so.conf.d/locallib.conf
+sudo ldconfig
 ```
 
-Or you could just build everything that is supported on your platform by running:
+Then clone this repo and generate makefile:
 ```bash
+git clone git://github.com/irungentoo/toxcore.git
+cd toxcore
+autoreconf -i
+./configure
 make
+sudo make install
 ```
 
+
 <a name="osx" />
 ###OS X:
 
+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.
+
+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](#usage) below.
 <a name="homebrew" />
 ####Homebrew:
+To install from the formula:
+```bash
+brew tap Tox/tox
+brew install --HEAD libtoxcore
+```
+
+To do it manually:
 ```
-brew install libtool automake autoconf libconfig libsodium cmake
-cmake .
+brew install libtool automake autoconf libsodium check
+```
+Then clone this repo and generate makefile:
+```bash
+git clone git://github.com/irungentoo/toxcore.git
+cd toxcore
+autoreconf -i
+./configure
 make
-sudo make install
+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:
+
+Determine paths:
+```
+brew list libsodium
+```
+
+Configure include and lib folder and build again:
+```bash
+./configure --with-libsodium-headers=/usr/local/Cellar/libsodium/0.7.0/include/ --with-libsodium-libs=/usr/local/Cellar/libsodium/0.7.0/lib/
+make
+make install
 ```
 
+
 <a name="non-homebrew" />
 ####Non-homebrew:
 
-Much the same as Linux, remember to install the latest XCode and the developer tools (Preferences -> Downloads -> Command Line Tools).
-Users running Mountain Lion and the latest version of XCode (4.6.3) will also need to install libtool, automake and autoconf.
-They are easy enough to install, grab them from http://www.gnu.org/software/libtool/, http://www.gnu.org/software/autoconf/ and http://www.gnu.org/software/automake/, then follow these steps for each:
+Grab the following packages:
+  * https://gnu.org/software/libtool/
+  * https://gnu.org/software/autoconf/
+  * https://gnu.org/software/automake/
+  * https://github.com/jedisct1/libsodium
+  * http://check.sourceforge.net/
+  * http://yasm.tortall.net/Download.html
+  * https://code.google.com/p/webm/downloads/list
+  * http://www.opus-codec.org/downloads/
+  * http://www.freedesktop.org/wiki/Software/pkg-config/
+
+You must install yasm before installing libvpx, otherwise libvpx will fail to make correctly.
+
+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:
 
 ```bash
 ./configure
@@ -80,48 +169,358 @@ make
 sudo make install
 ```
 
-Do not install them from macports (or any dependencies for that matter) as they get shoved in the wrong directory
-and make your life more annoying.
+Compiling and installing Tox Core
+
+```bash
+cd toxcore
+autoreconf -i
+./configure
+make
+make install
+```
+
+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.
 
-Another thing you may want to install is the latest gcc, this caused me a few problems as XCode from 4.3
-no longer includes gcc and instead uses LLVM-GCC, a nice install guide can be found at
-http://caiustheory.com/install-gcc-421-apple-build-56663-with-xcode-42
+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:
+
+```
+export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
+```
 
 <a name="windows" />
 ###Windows:
 
-You should install:
-  - [MinGW](http://sourceforge.net/projects/mingw/)'s C compiler
-  - [CMake](http://www.cmake.org/cmake/resources/software.html)
+<a name="windows-cross-compile" />
 
-You have to [modify your PATH environment variable](http://www.computerhope.com/issues/ch000549.htm) so that it contains MinGW's bin folder path. With default settings, the bin folder is located at `C:\MinGW\bin`, which means that you would have to append `;C:\MinGW\bin` to the PATH variable.
+####Cross-compile
 
-Then you should either clone this repo by using git, or just download a [zip of current Master branch](https://github.com/irungentoo/ProjectTox-Core/archive/master.zip) and extract it somewhere.
+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.
 
-After that you should get precompiled package of libsodium from [here](https://download.libsodium.org/libsodium/releases/libsodium-win32-0.4.2.tar.gz) and extract the archive into this repo's root. That is, `sodium` folder should be along with `core`, `testing` and other folders.
+<a name="windows-cross-compile-vm" />
+#####Setting up a VM
 
-Navigate in `cmd` to this repo and run:
-```cmd
-mkdir build && cd build
-cmake -G "MinGW Makefiles" ..
+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](https://www.virtualbox.org/wiki/Downloads).
+
+For a Linux distribution we will use Lubuntu 14.04 32-bit, which you can get [here](https://help.ubuntu.com/community/Lubuntu/GetLubuntu).
+
+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**.
+
+Execute:
+```bash
+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.
+
+Execute:
+```bash
+sudo adduser `whoami` vboxsf
+```
+Note the use of a [grave accent](http://en.wikipedia.org/wiki/Grave_accent) instead of an apostrophe.
+
+Then just reboot the system with:
+```bash
+sudo reboot
+```
+
+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.
+
+<a name="windows-cross-compile-environment" />
+#####Setting up the environment
+
+First we will install all tools that we would need for building:
+```bash
+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:
+```bash
+WINDOWS_TOOLCHAIN=i686-w64-mingw32
+LIB_VPX_TARGET=x86-win32-gcc
+```
+
+For 64-bit Tox build, do:
+```bash
+WINDOWS_TOOLCHAIN=x86_64-w64-mingw32
+LIB_VPX_TARGET=x86_64-win64-gcc
+```
+
+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
+```bash
+cd ~
+mkdir prefix
+cd prefix
+PREFIX_DIR=$(pwd)
+cd ..
+mkdir build
+cd build
+```
+
+<a name="windows-cross-compile-compiling" />
+#####Compiling
+
+Now we will build libraries needed for audio/video: VPX and Opus.
+
+VPX:
+```bash
+git clone http://git.chromium.org/webm/libvpx.git
+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 ..
+```
+
+Opus:
+```bash
+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:
+```bash
+git clone https://github.com/jedisct1/libsodium/
+cd libsodium
+git checkout tags/0.7.0
+./autogen.sh
+./configure --host="$WINDOWS_TOOLCHAIN" --prefix="$PREFIX_DIR" --disable-shared --enable-static
+make
+make install
+cd ..
+```
+
+And finally we will build Tox:
+```bash
+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:
+```bash
+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-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
 ```
-Note that you should call cmake on the root [`CMakeLists.txt`](/CMakeLists.txt) file only.
 
-Then you can build any of the [`/testing`](/testing) and [`/other`](/other) that are currently supported on your platform by running:
+And we will copy it over to the `toxbuild` directory:
+```bash
+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/bin/libtox.dll`, `release/bin/libtox.dll.a` and `release/include/tox/<headers>` in your `toxbuild` directory on the Windows system.
+
+<a name="windows-native" />
+####Native
+
+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:
+  - [MinGW](http://sourceforge.net/projects/mingw/)
+
+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-0.7.0.tar.gz release:
 ```cmd
-mingw32-make name_of_c_file
+tar -zxvf libsodium-0.7.0.tar.gz
+cd libsodium-0.7.0
+./configure
+make
+make install
+cd ..
 ```
-For example, to build [`Messenger_test.c`](/others/Messenger_test.c) you would run:
+
+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](https://github.com/irungentoo/toxcore/archive/master.zip) and extract it somewhere.
+
+Assuming that you now have the sources in the toxcore directory:
+
 ```cmd
-mingw32-make Messenger_test
+cd toxcore
+autoreconf -i
+./configure
+make
+make install
+```
+
+<a name="Clients" />
+####Clients:
+While [Toxic](https://github.com/tox/toxic) is no longer in core, a list of Tox clients are located in our [wiki](http://wiki.tox.im/client)
+
+
+
+
+
+<a name="additional" />
+##Additional
+
+
+
+<a name="aconf" />
+###Advanced configure options:
+
+  - --prefix=/where/to/install
+  - --with-libsodium-headers=/path/to/libsodium/include/
+  - --with-libsodium-libs=/path/to/sodiumtest/lib/
+  - --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](#libtoxav)
+  - --enable-ntox build nTox client (default: no) see: [nTox](#ntox)
+  - --enable-daemon build DHT bootstrap daemon (default=no) see: [Bootstrap daemon](#bootstrapd)
+  - --enable-shared[=PKGS]  build shared libraries [default=yes]
+  - --enable-static[=PKGS]  build static libraries [default=yes]
+
+
+<a name="av" />
+###A/V support:
+
+<a name="libtoxav" />
+####libtoxav:
+
+'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:
+```bash
+./configure --disable-av
 ```
 
-Or you could just build everything that is supported on your platform by running:
+There are 2 dependencies required for libtoxav: libopus and libvpx. If they are not installed A/V support is dropped.
+
+Install on fedora:
 ```bash
-mingw32-make
+yum install libopus-devel libvpx-devel
 ```
 
-<a name="usage" />
-## Usage
+Install on ubuntu:
+```bash
+sudo apt-get install libopus-dev libvpx-dev
+```
+If you get the "Unable to locate package libopus-dev" message, add the following ppa and try again:
+```bash
+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):
+
+libvpx:
+```bash
+git clone http://git.chromium.org/webm/libvpx.git
+cd libvpx
+./configure
+make -j3
+sudo make install
+cd ..
+```
+
+libopus:
+```bash
+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 ..
+```
 
-- [Start Guide](start_guide.md)
+<a name="bootstrapd" />
+###Bootstrap daemon:
+
+Daemon is disabled by default. You can enable it by adding --enable-daemon argument to ./configure script like so:
+```bash
+./configure --enable-daemon
+```
+There is one dependency required for bootstrap daemon: `libconfig-dev` >= 1.4.
+
+Install on fedora:
+```bash
+yum install libconfig-devel
+```
+
+Install on ubuntu:
+```bash
+sudo apt-get install libconfig-dev
+```
+
+OS X homebrew:
+```
+brew install libconfig
+```
+OS X non-homebrew:
+Grab the following [package] (http://www.hyperrealm.com/libconfig/), uncompress and install
+
+See this [readme](other/bootstrap_daemon/README.md) on how to set up the bootstrap daemon.
+
+
+<a name="ntox" />
+###nTox test cli:
+
+nTox is disabled by default. You can enable it by adding --enable-ntox argument to ./configure script like so:
+```bash
+./configure --enable-ntox
+```
+There is one dependency required for nTox: libncurses.
+
+Install on fedora:
+```bash
+yum install ncurses-devel
+```
+
+Install on ubuntu:
+```bash
+sudo apt-get install ncurses-dev
+```