This version brings a lot of changes, breaks the ABI, and changes the structure of the libraries.
Details
To be testes with all Tox clients:
net-im/toxic
net-im/uTox
net-im/py-toxcore-c
net-im/qTox
Diff Detail
- Repository
- rP FreeBSD ports repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
All of them fail.
qTox fails with this error message:
-- Checking for one of the modules 'libtoxav' CMake Error at cmake/Dependencies.cmake:73 (message): TOXAV package, library or framework not found
You need to tell them. I saw that they were saying that they will release toxcore once qTox works with it.
Yes, of course, this is why I did not upgrade net-im/tox but submitted this on phabricator!
We have to wait for updates of the clients and synchronize them.
E.g., toxic released a new version today: see
https://github.com/JFreegman/toxic/releases/tag/v0.8.2
I've just submitted a PR, it will be easier to coordinate the different ports:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226310
uTox: I asked the maintainer to update: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226329
There are many .so removed. If there are any port that link with them, you need to bump them so that they get rebuilt.
There is a disagreement in uTox https://github.com/uTox/uTox/pull/1157
One influential project member doesn't trust the TokTok/c-toxcore version.
Otherwise, the patch is ready there since Dec 30, 2017.
I think you should branch out net-im/tox12, keep uTox on it, and commit the new tox-0.2.0.
Otherwise there could be months until this is resolved.