Differences
This shows you the differences between two versions of the page.
| Both sides previous revision
Previous revision
|
|
clients:ratox [2015/09/23 06:29]
cmotc [Features] made features an unordered list and fixed a typo |
clients:ratox [2015/09/23 06:30] (current)
cmotc [debootstrap/chroot method(Debian, Ubuntu, etc only] fixed a typo I missed a second ago |
| ratox has not been updated to use the new Tox API yet, and must be compiled against the old api, which is available here [[https://github.com/irungentoo/toxcore/releases/tag/api_old_version|here]] as a zip and as a tar.gz file. However, installing the old API alongside the contemporary API can be confusing and potentially cause conflicts. There are a few ways to work around this and get a binary of ratox running. | ratox has not been updated to use the new Tox API yet, and must be compiled against the old api, which is available here [[https://github.com/irungentoo/toxcore/releases/tag/api_old_version|here]] as a zip and as a tar.gz file. However, installing the old API alongside the contemporary API can be confusing and potentially cause conflicts. There are a few ways to work around this and get a binary of ratox running. |
| |
| ==== debootstrap/chroot method(Debian, Ubuntu, etc only ==== | ==== debootstrap/chroot method(Debian, Ubuntu, etc only) ==== |
| |
| This one is time and space consuming, but it's also relatively easy and offers an environment in which you can continue to build against the old API for as long as it works. As of the time of this posting(2015/9/23), it's still possible to send messages between an official version of nTox from the Debian repo and a home-compiled version of ratox built in a chroot. This means that the old API still works, for now. For any fledgling programmers and admins new to the concept of a chroot, it's a way of using a directory on your computer as if it were your root filesystem, which allows you to install the dependencies you'll need to build ratox without interfering with your real root system. | This one is time and space consuming, but it's also relatively easy and offers an environment in which you can continue to build against the old API for as long as it works. As of the time of this posting(2015/9/23), it's still possible to send messages between an official version of nTox from the Debian repo and a home-compiled version of ratox built in a chroot. This means that the old API still works, for now. For any fledgling programmers and admins new to the concept of a chroot, it's a way of using a directory on your computer as if it were your root filesystem, which allows you to install the dependencies you'll need to build ratox without interfering with your real root system. |
