diff options
Diffstat (limited to 'libs/libtox/docs')
| -rw-r--r-- | libs/libtox/docs/CHANGELOG.md | 450 | ||||
| -rw-r--r-- | libs/libtox/docs/COPYING | 674 | ||||
| -rw-r--r-- | libs/libtox/docs/DONATORS | 7 | ||||
| -rw-r--r-- | libs/libtox/docs/README.md | 174 |
4 files changed, 0 insertions, 1305 deletions
diff --git a/libs/libtox/docs/CHANGELOG.md b/libs/libtox/docs/CHANGELOG.md deleted file mode 100644 index e3275a16df..0000000000 --- a/libs/libtox/docs/CHANGELOG.md +++ /dev/null @@ -1,450 +0,0 @@ - - -## v0.1.10 - -### Merged PRs: - -- [#564](https://github.com/TokTok/c-toxcore/pull/564) Fix Windows build -- [#542](https://github.com/TokTok/c-toxcore/pull/542) Save bandwidth by moderating onion pinging - -## v0.1.9 - -### Merged PRs: - -- [#563](https://github.com/TokTok/c-toxcore/pull/563) Release v0.1.9 -- [#561](https://github.com/TokTok/c-toxcore/pull/561) Remove unused variable -- [#560](https://github.com/TokTok/c-toxcore/pull/560) Fix non-portable zeroing out of doubles -- [#559](https://github.com/TokTok/c-toxcore/pull/559) Fix theoretical memory leaks -- [#557](https://github.com/TokTok/c-toxcore/pull/557) Document inverted mutex lock/unlock. -- [#556](https://github.com/TokTok/c-toxcore/pull/556) Build tests on appveyor, the MSVC build, but don't run them yet. -- [#555](https://github.com/TokTok/c-toxcore/pull/555) Fold hstox tests into the general linux test. -- [#554](https://github.com/TokTok/c-toxcore/pull/554) Add a monolith_test that includes all toxcore sources. -- [#553](https://github.com/TokTok/c-toxcore/pull/553) Factor out strict_abi cmake code into a separate module. -- [#552](https://github.com/TokTok/c-toxcore/pull/552) Fix formatting and spelling in version-sync script. -- [#551](https://github.com/TokTok/c-toxcore/pull/551) Forbid undefined symbols in shared libraries. -- [#546](https://github.com/TokTok/c-toxcore/pull/546) Make variable names in file saving test less cryptic -- [#539](https://github.com/TokTok/c-toxcore/pull/539) Make OSX test failures fail the Travis CI build. -- [#537](https://github.com/TokTok/c-toxcore/pull/537) Fix TokTok/c-toxcore#535 -- [#534](https://github.com/TokTok/c-toxcore/pull/534) Fix markdown formatting -- [#530](https://github.com/TokTok/c-toxcore/pull/530) Implement missing TES constant functions. -- [#511](https://github.com/TokTok/c-toxcore/pull/511) Save bandwidth by avoiding superfluous Nodes Requests to peers already on the Close List -- [#506](https://github.com/TokTok/c-toxcore/pull/506) Add test case for title change -- [#498](https://github.com/TokTok/c-toxcore/pull/498) DHT refactoring -- [#487](https://github.com/TokTok/c-toxcore/pull/487) Split daemon's logging backends in separate modules -- [#468](https://github.com/TokTok/c-toxcore/pull/468) Test for memberlist not changing after changing own name -- [#449](https://github.com/TokTok/c-toxcore/pull/449) Use new encoding of `Maybe` in msgpack results. - -### Closed issues: - -- [#482](https://github.com/TokTok/c-toxcore/issues/482) CMake can't detect and compile ToxAV on OSX - -## v0.1.8 - -### Merged PRs: - -- [#538](https://github.com/TokTok/c-toxcore/pull/538) Reverting tox_loop PR changes -- [#536](https://github.com/TokTok/c-toxcore/pull/536) Release v0.1.8 -- [#526](https://github.com/TokTok/c-toxcore/pull/526) Add TOX_NOSPAM_SIZE to the public API. -- [#525](https://github.com/TokTok/c-toxcore/pull/525) Retry autotools tests the same way as cmake tests. -- [#524](https://github.com/TokTok/c-toxcore/pull/524) Reduce ctest timeout to 2 minutes from 5 minutes. -- [#512](https://github.com/TokTok/c-toxcore/pull/512) Add test for DHT pack_nodes and unpack_nodes -- [#504](https://github.com/TokTok/c-toxcore/pull/504) CMake: install bootstrapd if it is built -- [#488](https://github.com/TokTok/c-toxcore/pull/488) Save compiled Android artifacts after CircleCI builds. -- [#473](https://github.com/TokTok/c-toxcore/pull/473) Added missing includes: <netinet/in.h> and <sys/socket.h> -- [#335](https://github.com/TokTok/c-toxcore/pull/335) Implement tox_loop - -### Closed issues: - -- [#535](https://github.com/TokTok/c-toxcore/issues/535) OS X tests failing -- [#503](https://github.com/TokTok/c-toxcore/issues/503) Undefined functions: tox_pass_salt_length, tox_pass_key_length, tox_pass_encryption_extra_length -- [#456](https://github.com/TokTok/c-toxcore/issues/456) Tox.h doesn't expose the size of the nospam. -- [#411](https://github.com/TokTok/c-toxcore/issues/411) Reduce CTest timeout to 2 minutes - -## v0.1.7 - -### Merged PRs: - -- [#523](https://github.com/TokTok/c-toxcore/pull/523) Release v0.1.7 -- [#521](https://github.com/TokTok/c-toxcore/pull/521) Fix appveyor script: install curl from chocolatey. -- [#510](https://github.com/TokTok/c-toxcore/pull/510) Fix list malloc(0) bug -- [#509](https://github.com/TokTok/c-toxcore/pull/509) Fix network malloc(0) bug -- [#497](https://github.com/TokTok/c-toxcore/pull/497) Fix network -- [#496](https://github.com/TokTok/c-toxcore/pull/496) Fix Travis always succeeding despite tests failing -- [#491](https://github.com/TokTok/c-toxcore/pull/491) Add crypto_memzero for temp buffer -- [#490](https://github.com/TokTok/c-toxcore/pull/490) Move c_sleep to helpers.h and misc_tools.h -- [#486](https://github.com/TokTok/c-toxcore/pull/486) Remove empty line in Messenger.c -- [#483](https://github.com/TokTok/c-toxcore/pull/483) Make BUILD_TOXAV an option and fail if dependencies are missing -- [#481](https://github.com/TokTok/c-toxcore/pull/481) Remove dependency on strings.h -- [#480](https://github.com/TokTok/c-toxcore/pull/480) Use VLA macro -- [#479](https://github.com/TokTok/c-toxcore/pull/479) Fix pthreads in AppVeyor build -- [#471](https://github.com/TokTok/c-toxcore/pull/471) Remove statics used in onion comparison functions. -- [#461](https://github.com/TokTok/c-toxcore/pull/461) Replace part of network functions on platform-independent implementation -- [#452](https://github.com/TokTok/c-toxcore/pull/452) Add VLA compatibility macro for C89-ish compilers. - -### Closed issues: - -- [#474](https://github.com/TokTok/c-toxcore/issues/474) TOX_VERSION_PATCH isn't in sync with the version - -## v0.1.6 - -### Merged PRs: - -- [#460](https://github.com/TokTok/c-toxcore/pull/460) Release v0.1.6. -- [#459](https://github.com/TokTok/c-toxcore/pull/459) Add Android build to CI. -- [#454](https://github.com/TokTok/c-toxcore/pull/454) Add appveyor build for native windows tests. -- [#448](https://github.com/TokTok/c-toxcore/pull/448) Only retry failed tests on Circle CI instead of all. -- [#434](https://github.com/TokTok/c-toxcore/pull/434) Replace redundant packet type check in handler with assert. -- [#432](https://github.com/TokTok/c-toxcore/pull/432) Remove some static variables -- [#385](https://github.com/TokTok/c-toxcore/pull/385) Add platform-independent Socket and IP implementation - -### Closed issues: - -- [#415](https://github.com/TokTok/c-toxcore/issues/415) Set up a native windows build on appveyor - -## v0.1.5 - -### Merged PRs: - -- [#447](https://github.com/TokTok/c-toxcore/pull/447) Release v0.1.5. -- [#446](https://github.com/TokTok/c-toxcore/pull/446) Limit number of retries to 3. -- [#445](https://github.com/TokTok/c-toxcore/pull/445) Make Travis tests slightly more robust by re-running them. -- [#443](https://github.com/TokTok/c-toxcore/pull/443) Make building `DHT_bootstrap` in cmake optional. -- [#433](https://github.com/TokTok/c-toxcore/pull/433) Add tutorial and "danger: experimental" banner to README. -- [#431](https://github.com/TokTok/c-toxcore/pull/431) Update license headers and remove redundant file name comment. -- [#424](https://github.com/TokTok/c-toxcore/pull/424) Fixed the FreeBSD build failure due to the undefined MSG_NOSIGNAL. -- [#420](https://github.com/TokTok/c-toxcore/pull/420) Setup autotools to read .so version info from a separate file -- [#418](https://github.com/TokTok/c-toxcore/pull/418) Clarify how the autotools build is done on Travis. -- [#414](https://github.com/TokTok/c-toxcore/pull/414) Explicitly check if compiler supports C99 - -## v0.1.4 - -### Merged PRs: - -- [#422](https://github.com/TokTok/c-toxcore/pull/422) Release v0.1.4. -- [#410](https://github.com/TokTok/c-toxcore/pull/410) Fix NaCl build: tar was called incorrectly. -- [#409](https://github.com/TokTok/c-toxcore/pull/409) Clarify that the pass key `new` function can fail. -- [#407](https://github.com/TokTok/c-toxcore/pull/407) Don't use `git.depth=1` anymore. -- [#404](https://github.com/TokTok/c-toxcore/pull/404) Issue 404: semicolon not found -- [#403](https://github.com/TokTok/c-toxcore/pull/403) Warn on -pedantic, don't error yet. -- [#401](https://github.com/TokTok/c-toxcore/pull/401) Add logging callback to messenger_test. -- [#400](https://github.com/TokTok/c-toxcore/pull/400) Run windows tests but ignore their failures. -- [#398](https://github.com/TokTok/c-toxcore/pull/398) Portability Fixes -- [#397](https://github.com/TokTok/c-toxcore/pull/397) Replace make_quick_sort with qsort -- [#396](https://github.com/TokTok/c-toxcore/pull/396) Add an OSX build that doesn't run tests. -- [#394](https://github.com/TokTok/c-toxcore/pull/394) CMake: Add soversion to library files to generate proper symlinks -- [#393](https://github.com/TokTok/c-toxcore/pull/393) Set up autotools build to build against vanilla NaCl. -- [#392](https://github.com/TokTok/c-toxcore/pull/392) Check that TCP connections aren't dropped in callbacks. -- [#391](https://github.com/TokTok/c-toxcore/pull/391) Minor simplification in `file_seek` code. -- [#390](https://github.com/TokTok/c-toxcore/pull/390) Always kill invalid file transfers when receiving file controls. -- [#388](https://github.com/TokTok/c-toxcore/pull/388) Fix logging condition for IPv6 client timestamp updates. -- [#387](https://github.com/TokTok/c-toxcore/pull/387) Eliminate dead return statement. -- [#386](https://github.com/TokTok/c-toxcore/pull/386) Avoid accessing uninitialised memory in `net_crypto`. -- [#381](https://github.com/TokTok/c-toxcore/pull/381) Remove `TOX_DEBUG` and have asserts always enabled. - -### Closed issues: - -- [#378](https://github.com/TokTok/c-toxcore/issues/378) Replace all uses of `make_quick_sort` with `qsort` -- [#364](https://github.com/TokTok/c-toxcore/issues/364) Delete misc_tools.h after replacing its use by qsort. -- [#363](https://github.com/TokTok/c-toxcore/issues/363) Test against NaCl in addition to libsodium on Travis. - -## v0.1.3 - -### Merged PRs: - -- [#395](https://github.com/TokTok/c-toxcore/pull/395) Revert "Portability fixes" -- [#380](https://github.com/TokTok/c-toxcore/pull/380) Test a few cmake option combinations before the build. -- [#377](https://github.com/TokTok/c-toxcore/pull/377) Fix SSL verification in coveralls. -- [#376](https://github.com/TokTok/c-toxcore/pull/376) Bring back autotools instructions -- [#373](https://github.com/TokTok/c-toxcore/pull/373) Only fetch 1 revision from git during Travis builds. -- [#369](https://github.com/TokTok/c-toxcore/pull/369) Integrate with CircleCI to build artifacts in the future -- [#366](https://github.com/TokTok/c-toxcore/pull/366) Release v0.1.3. -- [#362](https://github.com/TokTok/c-toxcore/pull/362) Remove .cabal-sandbox option from tox-spectest find line. -- [#361](https://github.com/TokTok/c-toxcore/pull/361) Simplify integration as a third-party lib in cmake projects -- [#354](https://github.com/TokTok/c-toxcore/pull/354) Add secure memcmp and memzero implementation. -- [#324](https://github.com/TokTok/c-toxcore/pull/324) Do not compile and install DHT_bootstrap if it was disabled in configure -- [#297](https://github.com/TokTok/c-toxcore/pull/297) Portability fixes - -### Closed issues: - -- [#347](https://github.com/TokTok/c-toxcore/issues/347) Implement our own secure `memcmp` and `memzero` if libsodium isn't available -- [#319](https://github.com/TokTok/c-toxcore/issues/319) toxcore installs `DHT_bootstrap` even though `--disable-daemon` is passed to `./configure` - -## v0.1.2 - -### Merged PRs: - -- [#355](https://github.com/TokTok/c-toxcore/pull/355) Release v0.1.2 -- [#353](https://github.com/TokTok/c-toxcore/pull/353) Fix toxav use after free caused by premature MSI destruction -- [#346](https://github.com/TokTok/c-toxcore/pull/346) Avoid array out of bounds read in friend saving. -- [#344](https://github.com/TokTok/c-toxcore/pull/344) Remove unused get/set salt/key functions from toxencryptsave. -- [#343](https://github.com/TokTok/c-toxcore/pull/343) Wrap all sodium/nacl functions in crypto_core.c. -- [#341](https://github.com/TokTok/c-toxcore/pull/341) Add test to check if tox_new/tox_kill leaks. -- [#336](https://github.com/TokTok/c-toxcore/pull/336) Correct TES docs to reflect how many bytes functions actually require. -- [#333](https://github.com/TokTok/c-toxcore/pull/333) Use `tox_options_set_*` instead of direct member access. - -### Closed issues: - -- [#345](https://github.com/TokTok/c-toxcore/issues/345) Array out of bounds read in "save" function -- [#342](https://github.com/TokTok/c-toxcore/issues/342) Wrap all libsodium functions we use in toxcore in `crypto_core`. -- [#278](https://github.com/TokTok/c-toxcore/issues/278) ToxAV use-after-free bug - -## v0.1.1 - -### Merged PRs: - -- [#337](https://github.com/TokTok/c-toxcore/pull/337) Release v0.1.1 -- [#332](https://github.com/TokTok/c-toxcore/pull/332) Add test for encrypted savedata. -- [#330](https://github.com/TokTok/c-toxcore/pull/330) Strengthen the note about ABI compatibility in tox.h. -- [#328](https://github.com/TokTok/c-toxcore/pull/328) Drop the broken `TOX_VERSION_REQUIRE` macro. -- [#326](https://github.com/TokTok/c-toxcore/pull/326) Fix unresolved reference in toxencryptsave API docs. -- [#309](https://github.com/TokTok/c-toxcore/pull/309) Fixed attempt to join detached threads (fixes toxav test crash) -- [#306](https://github.com/TokTok/c-toxcore/pull/306) Add option to disable local peer discovery - -### Closed issues: - -- [#327](https://github.com/TokTok/c-toxcore/issues/327) The `TOX_VERSION_REQUIRE` macro is broken. -- [#221](https://github.com/TokTok/c-toxcore/issues/221) Option to disable local peer detection - -## v0.1.0 - -### Merged PRs: - -- [#325](https://github.com/TokTok/c-toxcore/pull/325) Fix Libs line in toxcore.pc pkg-config file. -- [#322](https://github.com/TokTok/c-toxcore/pull/322) Add compatibility pkg-config modules: libtoxcore, libtoxav. -- [#318](https://github.com/TokTok/c-toxcore/pull/318) Fix `--enable-logging` flag in autotools configure script. -- [#316](https://github.com/TokTok/c-toxcore/pull/316) Release 0.1.0. -- [#315](https://github.com/TokTok/c-toxcore/pull/315) Fix version compatibility test. -- [#314](https://github.com/TokTok/c-toxcore/pull/314) Fix off by one error in saving our own status message. -- [#313](https://github.com/TokTok/c-toxcore/pull/313) Fix padding being in the wrong place in `SAVED_FRIEND` struct -- [#312](https://github.com/TokTok/c-toxcore/pull/312) Conditionally enable non-portable assert on LP64. -- [#310](https://github.com/TokTok/c-toxcore/pull/310) Add apidsl file for toxencryptsave. -- [#307](https://github.com/TokTok/c-toxcore/pull/307) Clarify toxencryptsave documentation regarding buffer sizes -- [#305](https://github.com/TokTok/c-toxcore/pull/305) Fix static builds -- [#303](https://github.com/TokTok/c-toxcore/pull/303) Don't build nTox by default. -- [#301](https://github.com/TokTok/c-toxcore/pull/301) Renamed messenger functions, prepend `m_`. -- [#299](https://github.com/TokTok/c-toxcore/pull/299) net_crypto give handle_data_packet_helper a better name -- [#294](https://github.com/TokTok/c-toxcore/pull/294) Don't error on warnings by default - -### Closed issues: - -- [#317](https://github.com/TokTok/c-toxcore/issues/317) toxcore fails to build with autotools and debugging level enabled -- [#311](https://github.com/TokTok/c-toxcore/issues/311) Incorrect padding -- [#308](https://github.com/TokTok/c-toxcore/issues/308) Review TES and port it to APIDSL -- [#293](https://github.com/TokTok/c-toxcore/issues/293) error building on ubuntu 14.04 -- [#292](https://github.com/TokTok/c-toxcore/issues/292) Don't build nTox by default with CMake -- [#290](https://github.com/TokTok/c-toxcore/issues/290) User Feed -- [#266](https://github.com/TokTok/c-toxcore/issues/266) Support all levels listed in TOX_DHT_NAT_LEVEL -- [#216](https://github.com/TokTok/c-toxcore/issues/216) When v0.1 release? - -## v0.0.5 - -### Merged PRs: - -- [#289](https://github.com/TokTok/c-toxcore/pull/289) Version Patch v0.0.4 => v0.0.5 -- [#287](https://github.com/TokTok/c-toxcore/pull/287) Add CMake knobs to suppress building tests -- [#286](https://github.com/TokTok/c-toxcore/pull/286) Support float32 and float64 in msgpack type printer. -- [#285](https://github.com/TokTok/c-toxcore/pull/285) Mark `Tox_Options` struct as deprecated. -- [#284](https://github.com/TokTok/c-toxcore/pull/284) Add NONE enumerator to bit mask. -- [#281](https://github.com/TokTok/c-toxcore/pull/281) Made save format platform-independent -- [#277](https://github.com/TokTok/c-toxcore/pull/277) Fix a memory leak in hstox interface -- [#276](https://github.com/TokTok/c-toxcore/pull/276) Fix NULL pointer dereference in log calls -- [#275](https://github.com/TokTok/c-toxcore/pull/275) Fix a memory leak in GroupAV -- [#274](https://github.com/TokTok/c-toxcore/pull/274) Options in `new_messenger()` must never be null. -- [#271](https://github.com/TokTok/c-toxcore/pull/271) Convert to and from network byte order in set/get nospam. -- [#262](https://github.com/TokTok/c-toxcore/pull/262) Add ability to disable UDP hole punching - -### Closed issues: - -- [#254](https://github.com/TokTok/c-toxcore/issues/254) Add option to disable UDP hole punching -- [#215](https://github.com/TokTok/c-toxcore/issues/215) The current tox save format is non-portable -- [#205](https://github.com/TokTok/c-toxcore/issues/205) nospam value is reversed in array returned by `tox_self_get_address()` - -## v0.0.4 - -### Merged PRs: - -- [#272](https://github.com/TokTok/c-toxcore/pull/272) v0.0.4 -- [#265](https://github.com/TokTok/c-toxcore/pull/265) Disable -Wunused-but-set-variable compiler warning flag. -- [#261](https://github.com/TokTok/c-toxcore/pull/261) Work around Travis issue that causes build failures. -- [#260](https://github.com/TokTok/c-toxcore/pull/260) Support arbitrary video resolutions in av_test -- [#257](https://github.com/TokTok/c-toxcore/pull/257) Add decode/encode PlainText test support. -- [#256](https://github.com/TokTok/c-toxcore/pull/256) Add spectest to the cmake test suite. -- [#255](https://github.com/TokTok/c-toxcore/pull/255) Disable some gcc-specific warnings. -- [#249](https://github.com/TokTok/c-toxcore/pull/249) Use apidsl for the crypto_core API. -- [#248](https://github.com/TokTok/c-toxcore/pull/248) Remove new_nonce function in favour of random_nonce. -- [#224](https://github.com/TokTok/c-toxcore/pull/224) Add DHT_create_packet, an abstraction for DHT RPC packets - -## v0.0.3 - -### Merged PRs: - -- [#251](https://github.com/TokTok/c-toxcore/pull/251) Rename log levels to remove the extra "LOG" prefix. -- [#250](https://github.com/TokTok/c-toxcore/pull/250) Release v0.0.3. -- [#245](https://github.com/TokTok/c-toxcore/pull/245) Change packet kind enum to use hex constants. -- [#243](https://github.com/TokTok/c-toxcore/pull/243) Enable address sanitizer on the cmake build. -- [#242](https://github.com/TokTok/c-toxcore/pull/242) Remove assoc -- [#241](https://github.com/TokTok/c-toxcore/pull/241) Move log callback to options. -- [#233](https://github.com/TokTok/c-toxcore/pull/233) Enable all possible C compiler warning flags. -- [#230](https://github.com/TokTok/c-toxcore/pull/230) Move packing and unpacking DHT request packets to DHT module. -- [#228](https://github.com/TokTok/c-toxcore/pull/228) Remove unimplemented "time delta" parameter. -- [#227](https://github.com/TokTok/c-toxcore/pull/227) Compile as C++ for windows builds. -- [#223](https://github.com/TokTok/c-toxcore/pull/223) TravisCI shorten IRC message -- [#220](https://github.com/TokTok/c-toxcore/pull/220) toxav renaming: group.{h,c} -> groupav.{h,c} -- [#218](https://github.com/TokTok/c-toxcore/pull/218) Rename some internal "group chat" thing to "conference". -- [#212](https://github.com/TokTok/c-toxcore/pull/212) Convert series of `NET_PACKET_*` defines into a typedef enum -- [#196](https://github.com/TokTok/c-toxcore/pull/196) Update readme, moved the roadmap to a higher position -- [#193](https://github.com/TokTok/c-toxcore/pull/193) Remove duplicate tests: split tests part 2. - -### Closed issues: - -- [#40](https://github.com/TokTok/c-toxcore/issues/40) Stateless callbacks in toxcore's public API - -## v0.0.2 - -### Merged PRs: - -- [#207](https://github.com/TokTok/c-toxcore/pull/207) docs: correct instructions for cloning & harden agains repo name changes -- [#206](https://github.com/TokTok/c-toxcore/pull/206) Corrected libsodium tag -- [#204](https://github.com/TokTok/c-toxcore/pull/204) Error if format_test can't be executed. -- [#202](https://github.com/TokTok/c-toxcore/pull/202) Version Patch v0.0.2 -- [#190](https://github.com/TokTok/c-toxcore/pull/190) Install libraries with RPATH. -- [#189](https://github.com/TokTok/c-toxcore/pull/189) Use `socklen_t` instead of `unsigned int` in call to `accept`. -- [#188](https://github.com/TokTok/c-toxcore/pull/188) Add option to set test timeout -- [#187](https://github.com/TokTok/c-toxcore/pull/187) Add option to build tox-bootstrapd -- [#185](https://github.com/TokTok/c-toxcore/pull/185) Import the hstox SUT interface from hstox. -- [#183](https://github.com/TokTok/c-toxcore/pull/183) Set log level for DEBUG=ON to LOG_DEBUG. -- [#182](https://github.com/TokTok/c-toxcore/pull/182) Remove return after no-return situation. -- [#181](https://github.com/TokTok/c-toxcore/pull/181) Minor documentation fixes. -- [#180](https://github.com/TokTok/c-toxcore/pull/180) Add the 'Tox' context object to the logger. -- [#179](https://github.com/TokTok/c-toxcore/pull/179) Remove the `_test` suffix in `auto_test` calls. -- [#178](https://github.com/TokTok/c-toxcore/pull/178) Rebuild apidsl'd headers in cmake. -- [#177](https://github.com/TokTok/c-toxcore/pull/177) docs(INSTALL): update compiling instructions for Linux -- [#176](https://github.com/TokTok/c-toxcore/pull/176) Merge irungentoo/toxcore into TokTok/c-toxcore. -- [#173](https://github.com/TokTok/c-toxcore/pull/173) Duplicate tox_test to 4 other files. - -### Closed issues: - -- [#201](https://github.com/TokTok/c-toxcore/issues/201) Logging callback was broken - -## v0.0.1 - -### Merged PRs: - -- [#174](https://github.com/TokTok/c-toxcore/pull/174) Remove redundant callback objects. -- [#171](https://github.com/TokTok/c-toxcore/pull/171) Simple Version tick to v0.0.1 -- [#170](https://github.com/TokTok/c-toxcore/pull/170) C++ the second round. -- [#166](https://github.com/TokTok/c-toxcore/pull/166) Add version-sync script. -- [#164](https://github.com/TokTok/c-toxcore/pull/164) Replace `void*` with `RingBuffer*` to avoid conversions. -- [#163](https://github.com/TokTok/c-toxcore/pull/163) Move ring buffer out of toxcore/util into toxav. -- [#162](https://github.com/TokTok/c-toxcore/pull/162) Allow the OSX build to fail on travis. -- [#161](https://github.com/TokTok/c-toxcore/pull/161) Minor cleanups: unused vars, unreachable code, static globals. -- [#160](https://github.com/TokTok/c-toxcore/pull/160) Work around bug in opencv3 headers. -- [#157](https://github.com/TokTok/c-toxcore/pull/157) Make TCP_Connections module-private. -- [#156](https://github.com/TokTok/c-toxcore/pull/156) Make TCP_Server opaque. -- [#153](https://github.com/TokTok/c-toxcore/pull/153) Fix strict-ld grep expressions to include digits. -- [#151](https://github.com/TokTok/c-toxcore/pull/151) Revert #130 "Make ToxAV stateless" -- [#148](https://github.com/TokTok/c-toxcore/pull/148) Added UB comment r/t deleting a friend w/ active call -- [#146](https://github.com/TokTok/c-toxcore/pull/146) Make group callbacks stateless -- [#145](https://github.com/TokTok/c-toxcore/pull/145) Make internal chat list function take uint32_t* as well. -- [#144](https://github.com/TokTok/c-toxcore/pull/144) Only build toxav if opus and vpx are found. -- [#143](https://github.com/TokTok/c-toxcore/pull/143) Make toxcore code C++ compatible. -- [#142](https://github.com/TokTok/c-toxcore/pull/142) Fix for windows dynamic libraries. -- [#141](https://github.com/TokTok/c-toxcore/pull/141) const-correctness in windows code. -- [#140](https://github.com/TokTok/c-toxcore/pull/140) Use C99 %zu format conversion in printf for size_t. -- [#139](https://github.com/TokTok/c-toxcore/pull/139) Clean up Travis build a bit in preparation for osx/win. -- [#138](https://github.com/TokTok/c-toxcore/pull/138) Remove format-source from travis script. -- [#135](https://github.com/TokTok/c-toxcore/pull/135) Convert old groupchats to new API format -- [#134](https://github.com/TokTok/c-toxcore/pull/134) Add some astyle options to make it do more. -- [#133](https://github.com/TokTok/c-toxcore/pull/133) Ensure that all TODOs have an owner. -- [#132](https://github.com/TokTok/c-toxcore/pull/132) Remove `else` directly after `return`. -- [#130](https://github.com/TokTok/c-toxcore/pull/130) Make ToxAV stateless -- [#129](https://github.com/TokTok/c-toxcore/pull/129) Use TokTok's apidsl instead of the iphydf one. -- [#127](https://github.com/TokTok/c-toxcore/pull/127) Use "phase" script for travis build phases. -- [#126](https://github.com/TokTok/c-toxcore/pull/126) Add option to build static libraries. -- [#125](https://github.com/TokTok/c-toxcore/pull/125) Group #include directives in 3-4 groups. -- [#123](https://github.com/TokTok/c-toxcore/pull/123) Use correct logical operator for tox_test -- [#120](https://github.com/TokTok/c-toxcore/pull/120) make the majority of the callbacks stateless and add some status to a testcase -- [#118](https://github.com/TokTok/c-toxcore/pull/118) Use `const` for version numbers. -- [#117](https://github.com/TokTok/c-toxcore/pull/117) Add STRICT_ABI cmake flag to generate export lists. -- [#116](https://github.com/TokTok/c-toxcore/pull/116) Fix potential null pointer dereference. -- [#115](https://github.com/TokTok/c-toxcore/pull/115) Fix memory leak on error paths in tox_new. -- [#114](https://github.com/TokTok/c-toxcore/pull/114) Fix compilation for Windows. -- [#111](https://github.com/TokTok/c-toxcore/pull/111) Add debugging option to autotools configuration -- [#110](https://github.com/TokTok/c-toxcore/pull/110) Comment intentional switch fallthroughs -- [#109](https://github.com/TokTok/c-toxcore/pull/109) Separate ip_port packing from pack_nodes() and unpack_nodes() -- [#108](https://github.com/TokTok/c-toxcore/pull/108) Prevent `<winsock.h>` inclusion by `<windows.h>`. -- [#107](https://github.com/TokTok/c-toxcore/pull/107) Print a message about missing astyle in format-source. -- [#104](https://github.com/TokTok/c-toxcore/pull/104) Merge with irungentoo/master -- [#103](https://github.com/TokTok/c-toxcore/pull/103) Allocate `sizeof(IP_ADAPTER_INFO)` bytes instead of `sizeof(T*)`. -- [#101](https://github.com/TokTok/c-toxcore/pull/101) Add TODO for @mannol. -- [#100](https://github.com/TokTok/c-toxcore/pull/100) Remove the packet mutation in toxav's bwcontroller. -- [#99](https://github.com/TokTok/c-toxcore/pull/99) Make packet data a ptr-to-const. -- [#97](https://github.com/TokTok/c-toxcore/pull/97) Improve static and const correctness. -- [#96](https://github.com/TokTok/c-toxcore/pull/96) Improve C standard compliance. -- [#94](https://github.com/TokTok/c-toxcore/pull/94) Rearrange fields to decrease size of structure -- [#84](https://github.com/TokTok/c-toxcore/pull/84) Remove useless casts. -- [#82](https://github.com/TokTok/c-toxcore/pull/82) Add missing #include <pthread.h> to av_test.c. -- [#81](https://github.com/TokTok/c-toxcore/pull/81) Match parameter names in declarations with their definitions. -- [#80](https://github.com/TokTok/c-toxcore/pull/80) Sort #includes in all source files. -- [#79](https://github.com/TokTok/c-toxcore/pull/79) Remove redundant `return` statements. -- [#78](https://github.com/TokTok/c-toxcore/pull/78) Do not use `else` after `return`. -- [#77](https://github.com/TokTok/c-toxcore/pull/77) Add OSX and Windows build to travis config. -- [#76](https://github.com/TokTok/c-toxcore/pull/76) Remove unused and bit-rotten friends_test. -- [#75](https://github.com/TokTok/c-toxcore/pull/75) Enable build of av_test. -- [#74](https://github.com/TokTok/c-toxcore/pull/74) Add missing #includes to headers and rename tox_old to tox_group. -- [#73](https://github.com/TokTok/c-toxcore/pull/73) Add braces to all if statements. -- [#72](https://github.com/TokTok/c-toxcore/pull/72) Add getters/setters for options. -- [#70](https://github.com/TokTok/c-toxcore/pull/70) Expose constants as functions. -- [#68](https://github.com/TokTok/c-toxcore/pull/68) Add address sanitizer option to cmake file. -- [#66](https://github.com/TokTok/c-toxcore/pull/66) Fix plane size calculation in test -- [#65](https://github.com/TokTok/c-toxcore/pull/65) Avoid large stack allocations on thread stacks. -- [#64](https://github.com/TokTok/c-toxcore/pull/64) Comment out useless TODO'd if block. -- [#63](https://github.com/TokTok/c-toxcore/pull/63) Initialise the id in assoc_test. -- [#62](https://github.com/TokTok/c-toxcore/pull/62) Reduce the timeout on travis to something much more reasonable -- [#60](https://github.com/TokTok/c-toxcore/pull/60) Make friend requests stateless -- [#59](https://github.com/TokTok/c-toxcore/pull/59) Replace uint with unsigned int in assoc.c. -- [#58](https://github.com/TokTok/c-toxcore/pull/58) Make Message received receipts stateless -- [#57](https://github.com/TokTok/c-toxcore/pull/57) Make Friend User Status stateless -- [#55](https://github.com/TokTok/c-toxcore/pull/55) docs(INSTALL.md): update instructions for Gentoo -- [#54](https://github.com/TokTok/c-toxcore/pull/54) Make typing change callback stateless -- [#53](https://github.com/TokTok/c-toxcore/pull/53) Add format-source script. -- [#52](https://github.com/TokTok/c-toxcore/pull/52) Build assoc DHT code on travis. -- [#51](https://github.com/TokTok/c-toxcore/pull/51) Fix operation sequencing in TCP_test. -- [#49](https://github.com/TokTok/c-toxcore/pull/49) Apidsl test -- [#48](https://github.com/TokTok/c-toxcore/pull/48) Make friend message callback stateless -- [#46](https://github.com/TokTok/c-toxcore/pull/46) Move logging to a callback. -- [#45](https://github.com/TokTok/c-toxcore/pull/45) Stateless friend status message -- [#43](https://github.com/TokTok/c-toxcore/pull/43) Allow NULL as argument to tox_kill. -- [#41](https://github.com/TokTok/c-toxcore/pull/41) Fix warnings -- [#39](https://github.com/TokTok/c-toxcore/pull/39) Merge irungentoo/toxcore into TokTok/c-toxcore. -- [#38](https://github.com/TokTok/c-toxcore/pull/38) Try searching for libsodium with pkg-config in ./configure. -- [#37](https://github.com/TokTok/c-toxcore/pull/37) Add missing DHT_bootstrap to CMakeLists.txt. -- [#36](https://github.com/TokTok/c-toxcore/pull/36) Make tox_callback_friend_name stateless. -- [#33](https://github.com/TokTok/c-toxcore/pull/33) Update readme with tentative roadmap, removed old todo.md -- [#32](https://github.com/TokTok/c-toxcore/pull/32) Fix a bug I introduced that would make toxcore fail to initialise a second time -- [#31](https://github.com/TokTok/c-toxcore/pull/31) 7. Travis envs -- [#30](https://github.com/TokTok/c-toxcore/pull/30) 2. Hstox test -- [#29](https://github.com/TokTok/c-toxcore/pull/29) 1. Move toxcore travis build scripts out of .travis.yml. -- [#27](https://github.com/TokTok/c-toxcore/pull/27) 8. Stateless -- [#26](https://github.com/TokTok/c-toxcore/pull/26) 6. Cmake bootstrapd -- [#25](https://github.com/TokTok/c-toxcore/pull/25) 5. Coverage clang -- [#24](https://github.com/TokTok/c-toxcore/pull/24) Silence/fix some compiler warnings. -- [#23](https://github.com/TokTok/c-toxcore/pull/23) 4. Cmake -- [#20](https://github.com/TokTok/c-toxcore/pull/20) 3. Travis astyle -- [#13](https://github.com/TokTok/c-toxcore/pull/13) Enable, and report test status -- [#12](https://github.com/TokTok/c-toxcore/pull/12) Fix readme for TokTok -- [#11](https://github.com/TokTok/c-toxcore/pull/11) Documentation: SysVInit workaround for <1024 ports -- [#2](https://github.com/TokTok/c-toxcore/pull/2) Enable toxcore logging when building on Travis. -- [#1](https://github.com/TokTok/c-toxcore/pull/1) Apidsl fixes and start tracking test coverage - -### Closed issues: - -- [#158](https://github.com/TokTok/c-toxcore/issues/158) Error while build with OpenCV 3.1 -- [#147](https://github.com/TokTok/c-toxcore/issues/147) Add comment to m_delfriend about the NULL passing to the internal conn status cb -- [#136](https://github.com/TokTok/c-toxcore/issues/136) Replace astyle by clang-format -- [#113](https://github.com/TokTok/c-toxcore/issues/113) Toxcore tests fail -- [#83](https://github.com/TokTok/c-toxcore/issues/83) Travis tests are hard to quickly parse from their output. -- [#22](https://github.com/TokTok/c-toxcore/issues/22) Make the current tests exercise both ipv4 and ipv6. -- [#9](https://github.com/TokTok/c-toxcore/issues/9) Fix the failing test -- [#8](https://github.com/TokTok/c-toxcore/issues/8) Toxcore should make more liberal use of assertions -- [#4](https://github.com/TokTok/c-toxcore/issues/4) Integrate hstox tests with toxcore Travis build diff --git a/libs/libtox/docs/COPYING b/libs/libtox/docs/COPYING deleted file mode 100644 index 94a9ed024d..0000000000 --- a/libs/libtox/docs/COPYING +++ /dev/null @@ -1,674 +0,0 @@ - GNU GENERAL PUBLIC LICENSE - Version 3, 29 June 2007 - - Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/> - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - Preamble - - The GNU General Public License is a free, copyleft license for -software and other kinds of works. - - The licenses for most software and other practical works are designed -to take away your freedom to share and change the works. By contrast, -the GNU General Public License is intended to guarantee your freedom to -share and change all versions of a program--to make sure it remains free -software for all its users. We, the Free Software Foundation, use the -GNU General Public License for most of our software; it applies also to -any other work released this way by its authors. You can apply it to -your programs, too. - - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -them if you wish), that you receive source code or can get it if you -want it, that you can change the software or use pieces of it in new -free programs, and that you know you can do these things. - - To protect your rights, we need to prevent others from denying you -these rights or asking you to surrender the rights. Therefore, you have -certain responsibilities if you distribute copies of the software, or if -you modify it: responsibilities to respect the freedom of others. - - For example, if you distribute copies of such a program, whether -gratis or for a fee, you must pass on to the recipients the same -freedoms that you received. You must make sure that they, too, receive -or can get the source code. And you must show them these terms so they -know their rights. - - Developers that use the GNU GPL protect your rights with two steps: -(1) assert copyright on the software, and (2) offer you this License -giving you legal permission to copy, distribute and/or modify it. - - For the developers' and authors' protection, the GPL clearly explains -that there is no warranty for this free software. For both users' and -authors' sake, the GPL requires that modified versions be marked as -changed, so that their problems will not be attributed erroneously to -authors of previous versions. - - Some devices are designed to deny users access to install or run -modified versions of the software inside them, although the manufacturer -can do so. This is fundamentally incompatible with the aim of -protecting users' freedom to change the software. The systematic -pattern of such abuse occurs in the area of products for individuals to -use, which is precisely where it is most unacceptable. Therefore, we -have designed this version of the GPL to prohibit the practice for those -products. If such problems arise substantially in other domains, we -stand ready to extend this provision to those domains in future versions -of the GPL, as needed to protect the freedom of users. - - Finally, every program is threatened constantly by software patents. -States should not allow patents to restrict development and use of -software on general-purpose computers, but in those that do, we wish to -avoid the special danger that patents applied to a free program could -make it effectively proprietary. To prevent this, the GPL assures that -patents cannot be used to render the program non-free. - - The precise terms and conditions for copying, distribution and -modification follow. - - TERMS AND CONDITIONS - - 0. Definitions. - - "This License" refers to version 3 of the GNU General Public License. - - "Copyright" also means copyright-like laws that apply to other kinds of -works, such as semiconductor masks. - - "The Program" refers to any copyrightable work licensed under this -License. Each licensee is addressed as "you". "Licensees" and -"recipients" may be individuals or organizations. - - To "modify" a work means to copy from or adapt all or part of the work -in a fashion requiring copyright permission, other than the making of an -exact copy. The resulting work is called a "modified version" of the -earlier work or a work "based on" the earlier work. - - A "covered work" means either the unmodified Program or a work based -on the Program. - - To "propagate" a work means to do anything with it that, without -permission, would make you directly or secondarily liable for -infringement under applicable copyright law, except executing it on a -computer or modifying a private copy. Propagation includes copying, -distribution (with or without modification), making available to the -public, and in some countries other activities as well. - - To "convey" a work means any kind of propagation that enables other -parties to make or receive copies. Mere interaction with a user through -a computer network, with no transfer of a copy, is not conveying. - - An interactive user interface displays "Appropriate Legal Notices" -to the extent that it includes a convenient and prominently visible -feature that (1) displays an appropriate copyright notice, and (2) -tells the user that there is no warranty for the work (except to the -extent that warranties are provided), that licensees may convey the -work under this License, and how to view a copy of this License. If -the interface presents a list of user commands or options, such as a -menu, a prominent item in the list meets this criterion. - - 1. Source Code. - - The "source code" for a work means the preferred form of the work -for making modifications to it. "Object code" means any non-source -form of a work. - - A "Standard Interface" means an interface that either is an official -standard defined by a recognized standards body, or, in the case of -interfaces specified for a particular programming language, one that -is widely used among developers working in that language. - - The "System Libraries" of an executable work include anything, other -than the work as a whole, that (a) is included in the normal form of -packaging a Major Component, but which is not part of that Major -Component, and (b) serves only to enable use of the work with that -Major Component, or to implement a Standard Interface for which an -implementation is available to the public in source code form. A -"Major Component", in this context, means a major essential component -(kernel, window system, and so on) of the specific operating system -(if any) on which the executable work runs, or a compiler used to -produce the work, or an object code interpreter used to run it. - - The "Corresponding Source" for a work in object code form means all -the source code needed to generate, install, and (for an executable -work) run the object code and to modify the work, including scripts to -control those activities. However, it does not include the work's -System Libraries, or general-purpose tools or generally available free -programs which are used unmodified in performing those activities but -which are not part of the work. For example, Corresponding Source -includes interface definition files associated with source files for -the work, and the source code for shared libraries and dynamically -linked subprograms that the work is specifically designed to require, -such as by intimate data communication or control flow between those -subprograms and other parts of the work. - - The Corresponding Source need not include anything that users -can regenerate automatically from other parts of the Corresponding -Source. - - The Corresponding Source for a work in source code form is that -same work. - - 2. Basic Permissions. - - All rights granted under this License are granted for the term of -copyright on the Program, and are irrevocable provided the stated -conditions are met. This License explicitly affirms your unlimited -permission to run the unmodified Program. The output from running a -covered work is covered by this License only if the output, given its -content, constitutes a covered work. This License acknowledges your -rights of fair use or other equivalent, as provided by copyright law. - - You may make, run and propagate covered works that you do not -convey, without conditions so long as your license otherwise remains -in force. You may convey covered works to others for the sole purpose -of having them make modifications exclusively for you, or provide you -with facilities for running those works, provided that you comply with -the terms of this License in conveying all material for which you do -not control copyright. Those thus making or running the covered works -for you must do so exclusively on your behalf, under your direction -and control, on terms that prohibit them from making any copies of -your copyrighted material outside their relationship with you. - - Conveying under any other circumstances is permitted solely under -the conditions stated below. Sublicensing is not allowed; section 10 -makes it unnecessary. - - 3. Protecting Users' Legal Rights From Anti-Circumvention Law. - - No covered work shall be deemed part of an effective technological -measure under any applicable law fulfilling obligations under article -11 of the WIPO copyright treaty adopted on 20 December 1996, or -similar laws prohibiting or restricting circumvention of such -measures. - - When you convey a covered work, you waive any legal power to forbid -circumvention of technological measures to the extent such circumvention -is effected by exercising rights under this License with respect to -the covered work, and you disclaim any intention to limit operation or -modification of the work as a means of enforcing, against the work's -users, your or third parties' legal rights to forbid circumvention of -technological measures. - - 4. Conveying Verbatim Copies. - - You may convey verbatim copies of the Program's source code as you -receive it, in any medium, provided that you conspicuously and -appropriately publish on each copy an appropriate copyright notice; -keep intact all notices stating that this License and any -non-permissive terms added in accord with section 7 apply to the code; -keep intact all notices of the absence of any warranty; and give all -recipients a copy of this License along with the Program. - - You may charge any price or no price for each copy that you convey, -and you may offer support or warranty protection for a fee. - - 5. Conveying Modified Source Versions. - - You may convey a work based on the Program, or the modifications to -produce it from the Program, in the form of source code under the -terms of section 4, provided that you also meet all of these conditions: - - a) The work must carry prominent notices stating that you modified - it, and giving a relevant date. - - b) The work must carry prominent notices stating that it is - released under this License and any conditions added under section - 7. This requirement modifies the requirement in section 4 to - "keep intact all notices". - - c) You must license the entire work, as a whole, under this - License to anyone who comes into possession of a copy. This - License will therefore apply, along with any applicable section 7 - additional terms, to the whole of the work, and all its parts, - regardless of how they are packaged. This License gives no - permission to license the work in any other way, but it does not - invalidate such permission if you have separately received it. - - d) If the work has interactive user interfaces, each must display - Appropriate Legal Notices; however, if the Program has interactive - interfaces that do not display Appropriate Legal Notices, your - work need not make them do so. - - A compilation of a covered work with other separate and independent -works, which are not by their nature extensions of the covered work, -and which are not combined with it such as to form a larger program, -in or on a volume of a storage or distribution medium, is called an -"aggregate" if the compilation and its resulting copyright are not -used to limit the access or legal rights of the compilation's users -beyond what the individual works permit. Inclusion of a covered work -in an aggregate does not cause this License to apply to the other -parts of the aggregate. - - 6. Conveying Non-Source Forms. - - You may convey a covered work in object code form under the terms -of sections 4 and 5, provided that you also convey the -machine-readable Corresponding Source under the terms of this License, -in one of these ways: - - a) Convey the object code in, or embodied in, a physical product - (including a physical distribution medium), accompanied by the - Corresponding Source fixed on a durable physical medium - customarily used for software interchange. - - b) Convey the object code in, or embodied in, a physical product - (including a physical distribution medium), accompanied by a - written offer, valid for at least three years and valid for as - long as you offer spare parts or customer support for that product - model, to give anyone who possesses the object code either (1) a - copy of the Corresponding Source for all the software in the - product that is covered by this License, on a durable physical - medium customarily used for software interchange, for a price no - more than your reasonable cost of physically performing this - conveying of source, or (2) access to copy the - Corresponding Source from a network server at no charge. - - c) Convey individual copies of the object code with a copy of the - written offer to provide the Corresponding Source. This - alternative is allowed only occasionally and noncommercially, and - only if you received the object code with such an offer, in accord - with subsection 6b. - - d) Convey the object code by offering access from a designated - place (gratis or for a charge), and offer equivalent access to the - Corresponding Source in the same way through the same place at no - further charge. You need not require recipients to copy the - Corresponding Source along with the object code. If the place to - copy the object code is a network server, the Corresponding Source - may be on a different server (operated by you or a third party) - that supports equivalent copying facilities, provided you maintain - clear directions next to the object code saying where to find the - Corresponding Source. Regardless of what server hosts the - Corresponding Source, you remain obligated to ensure that it is - available for as long as needed to satisfy these requirements. - - e) Convey the object code using peer-to-peer transmission, provided - you inform other peers where the object code and Corresponding - Source of the work are being offered to the general public at no - charge under subsection 6d. - - A separable portion of the object code, whose source code is excluded -from the Corresponding Source as a System Library, need not be -included in conveying the object code work. - - A "User Product" is either (1) a "consumer product", which means any -tangible personal property which is normally used for personal, family, -or household purposes, or (2) anything designed or sold for incorporation -into a dwelling. In determining whether a product is a consumer product, -doubtful cases shall be resolved in favor of coverage. For a particular -product received by a particular user, "normally used" refers to a -typical or common use of that class of product, regardless of the status -of the particular user or of the way in which the particular user -actually uses, or expects or is expected to use, the product. A product -is a consumer product regardless of whether the product has substantial -commercial, industrial or non-consumer uses, unless such uses represent -the only significant mode of use of the product. - - "Installation Information" for a User Product means any methods, -procedures, authorization keys, or other information required to install -and execute modified versions of a covered work in that User Product from -a modified version of its Corresponding Source. The information must -suffice to ensure that the continued functioning of the modified object -code is in no case prevented or interfered with solely because -modification has been made. - - If you convey an object code work under this section in, or with, or -specifically for use in, a User Product, and the conveying occurs as -part of a transaction in which the right of possession and use of the -User Product is transferred to the recipient in perpetuity or for a -fixed term (regardless of how the transaction is characterized), the -Corresponding Source conveyed under this section must be accompanied -by the Installation Information. But this requirement does not apply -if neither you nor any third party retains the ability to install -modified object code on the User Product (for example, the work has -been installed in ROM). - - The requirement to provide Installation Information does not include a -requirement to continue to provide support service, warranty, or updates -for a work that has been modified or installed by the recipient, or for -the User Product in which it has been modified or installed. Access to a -network may be denied when the modification itself materially and -adversely affects the operation of the network or violates the rules and -protocols for communication across the network. - - Corresponding Source conveyed, and Installation Information provided, -in accord with this section must be in a format that is publicly -documented (and with an implementation available to the public in -source code form), and must require no special password or key for -unpacking, reading or copying. - - 7. Additional Terms. - - "Additional permissions" are terms that supplement the terms of this -License by making exceptions from one or more of its conditions. -Additional permissions that are applicable to the entire Program shall -be treated as though they were included in this License, to the extent -that they are valid under applicable law. If additional permissions -apply only to part of the Program, that part may be used separately -under those permissions, but the entire Program remains governed by -this License without regard to the additional permissions. - - When you convey a copy of a covered work, you may at your option -remove any additional permissions from that copy, or from any part of -it. (Additional permissions may be written to require their own -removal in certain cases when you modify the work.) You may place -additional permissions on material, added by you to a covered work, -for which you have or can give appropriate copyright permission. - - Notwithstanding any other provision of this License, for material you -add to a covered work, you may (if authorized by the copyright holders of -that material) supplement the terms of this License with terms: - - a) Disclaiming warranty or limiting liability differently from the - terms of sections 15 and 16 of this License; or - - b) Requiring preservation of specified reasonable legal notices or - author attributions in that material or in the Appropriate Legal - Notices displayed by works containing it; or - - c) Prohibiting misrepresentation of the origin of that material, or - requiring that modified versions of such material be marked in - reasonable ways as different from the original version; or - - d) Limiting the use for publicity purposes of names of licensors or - authors of the material; or - - e) Declining to grant rights under trademark law for use of some - trade names, trademarks, or service marks; or - - f) Requiring indemnification of licensors and authors of that - material by anyone who conveys the material (or modified versions of - it) with contractual assumptions of liability to the recipient, for - any liability that these contractual assumptions directly impose on - those licensors and authors. - - All other non-permissive additional terms are considered "further -restrictions" within the meaning of section 10. If the Program as you -received it, or any part of it, contains a notice stating that it is -governed by this License along with a term that is a further -restriction, you may remove that term. If a license document contains -a further restriction but permits relicensing or conveying under this -License, you may add to a covered work material governed by the terms -of that license document, provided that the further restriction does -not survive such relicensing or conveying. - - If you add terms to a covered work in accord with this section, you -must place, in the relevant source files, a statement of the -additional terms that apply to those files, or a notice indicating -where to find the applicable terms. - - Additional terms, permissive or non-permissive, may be stated in the -form of a separately written license, or stated as exceptions; -the above requirements apply either way. - - 8. Termination. - - You may not propagate or modify a covered work except as expressly -provided under this License. Any attempt otherwise to propagate or -modify it is void, and will automatically terminate your rights under -this License (including any patent licenses granted under the third -paragraph of section 11). - - However, if you cease all violation of this License, then your -license from a particular copyright holder is reinstated (a) -provisionally, unless and until the copyright holder explicitly and -finally terminates your license, and (b) permanently, if the copyright -holder fails to notify you of the violation by some reasonable means -prior to 60 days after the cessation. - - Moreover, your license from a particular copyright holder is -reinstated permanently if the copyright holder notifies you of the -violation by some reasonable means, this is the first time you have -received notice of violation of this License (for any work) from that -copyright holder, and you cure the violation prior to 30 days after -your receipt of the notice. - - Termination of your rights under this section does not terminate the -licenses of parties who have received copies or rights from you under -this License. If your rights have been terminated and not permanently -reinstated, you do not qualify to receive new licenses for the same -material under section 10. - - 9. Acceptance Not Required for Having Copies. - - You are not required to accept this License in order to receive or -run a copy of the Program. Ancillary propagation of a covered work -occurring solely as a consequence of using peer-to-peer transmission -to receive a copy likewise does not require acceptance. However, -nothing other than this License grants you permission to propagate or -modify any covered work. These actions infringe copyright if you do -not accept this License. Therefore, by modifying or propagating a -covered work, you indicate your acceptance of this License to do so. - - 10. Automatic Licensing of Downstream Recipients. - - Each time you convey a covered work, the recipient automatically -receives a license from the original licensors, to run, modify and -propagate that work, subject to this License. You are not responsible -for enforcing compliance by third parties with this License. - - An "entity transaction" is a transaction transferring control of an -organization, or substantially all assets of one, or subdividing an -organization, or merging organizations. If propagation of a covered -work results from an entity transaction, each party to that -transaction who receives a copy of the work also receives whatever -licenses to the work the party's predecessor in interest had or could -give under the previous paragraph, plus a right to possession of the -Corresponding Source of the work from the predecessor in interest, if -the predecessor has it or can get it with reasonable efforts. - - You may not impose any further restrictions on the exercise of the -rights granted or affirmed under this License. For example, you may -not impose a license fee, royalty, or other charge for exercise of -rights granted under this License, and you may not initiate litigation -(including a cross-claim or counterclaim in a lawsuit) alleging that -any patent claim is infringed by making, using, selling, offering for -sale, or importing the Program or any portion of it. - - 11. Patents. - - A "contributor" is a copyright holder who authorizes use under this -License of the Program or a work on which the Program is based. The -work thus licensed is called the contributor's "contributor version". - - A contributor's "essential patent claims" are all patent claims -owned or controlled by the contributor, whether already acquired or -hereafter acquired, that would be infringed by some manner, permitted -by this License, of making, using, or selling its contributor version, -but do not include claims that would be infringed only as a -consequence of further modification of the contributor version. For -purposes of this definition, "control" includes the right to grant -patent sublicenses in a manner consistent with the requirements of -this License. - - Each contributor grants you a non-exclusive, worldwide, royalty-free -patent license under the contributor's essential patent claims, to -make, use, sell, offer for sale, import and otherwise run, modify and -propagate the contents of its contributor version. - - In the following three paragraphs, a "patent license" is any express -agreement or commitment, however denominated, not to enforce a patent -(such as an express permission to practice a patent or covenant not to -sue for patent infringement). To "grant" such a patent license to a -party means to make such an agreement or commitment not to enforce a -patent against the party. - - If you convey a covered work, knowingly relying on a patent license, -and the Corresponding Source of the work is not available for anyone -to copy, free of charge and under the terms of this License, through a -publicly available network server or other readily accessible means, -then you must either (1) cause the Corresponding Source to be so -available, or (2) arrange to deprive yourself of the benefit of the -patent license for this particular work, or (3) arrange, in a manner -consistent with the requirements of this License, to extend the patent -license to downstream recipients. "Knowingly relying" means you have -actual knowledge that, but for the patent license, your conveying the -covered work in a country, or your recipient's use of the covered work -in a country, would infringe one or more identifiable patents in that -country that you have reason to believe are valid. - - If, pursuant to or in connection with a single transaction or -arrangement, you convey, or propagate by procuring conveyance of, a -covered work, and grant a patent license to some of the parties -receiving the covered work authorizing them to use, propagate, modify -or convey a specific copy of the covered work, then the patent license -you grant is automatically extended to all recipients of the covered -work and works based on it. - - A patent license is "discriminatory" if it does not include within -the scope of its coverage, prohibits the exercise of, or is -conditioned on the non-exercise of one or more of the rights that are -specifically granted under this License. You may not convey a covered -work if you are a party to an arrangement with a third party that is -in the business of distributing software, under which you make payment -to the third party based on the extent of your activity of conveying -the work, and under which the third party grants, to any of the -parties who would receive the covered work from you, a discriminatory -patent license (a) in connection with copies of the covered work -conveyed by you (or copies made from those copies), or (b) primarily -for and in connection with specific products or compilations that -contain the covered work, unless you entered into that arrangement, -or that patent license was granted, prior to 28 March 2007. - - Nothing in this License shall be construed as excluding or limiting -any implied license or other defenses to infringement that may -otherwise be available to you under applicable patent law. - - 12. No Surrender of Others' Freedom. - - If conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot convey a -covered work so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you may -not convey it at all. For example, if you agree to terms that obligate you -to collect a royalty for further conveying from those to whom you convey -the Program, the only way you could satisfy both those terms and this -License would be to refrain entirely from conveying the Program. - - 13. Use with the GNU Affero General Public License. - - Notwithstanding any other provision of this License, you have -permission to link or combine any covered work with a work licensed -under version 3 of the GNU Affero General Public License into a single -combined work, and to convey the resulting work. The terms of this -License will continue to apply to the part which is the covered work, -but the special requirements of the GNU Affero General Public License, -section 13, concerning interaction through a network will apply to the -combination as such. - - 14. Revised Versions of this License. - - The Free Software Foundation may publish revised and/or new versions of -the GNU General Public License from time to time. Such new versions will -be similar in spirit to the present version, but may differ in detail to -address new problems or concerns. - - Each version is given a distinguishing version number. If the -Program specifies that a certain numbered version of the GNU General -Public License "or any later version" applies to it, you have the -option of following the terms and conditions either of that numbered -version or of any later version published by the Free Software -Foundation. If the Program does not specify a version number of the -GNU General Public License, you may choose any version ever published -by the Free Software Foundation. - - If the Program specifies that a proxy can decide which future -versions of the GNU General Public License can be used, that proxy's -public statement of acceptance of a version permanently authorizes you -to choose that version for the Program. - - Later license versions may give you additional or different -permissions. However, no additional obligations are imposed on any -author or copyright holder as a result of your choosing to follow a -later version. - - 15. Disclaimer of Warranty. - - THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY -APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT -HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY -OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, -THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR -PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM -IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF -ALL NECESSARY SERVICING, REPAIR OR CORRECTION. - - 16. Limitation of Liability. - - IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING -WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS -THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY -GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE -USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF -DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD -PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), -EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF -SUCH DAMAGES. - - 17. Interpretation of Sections 15 and 16. - - If the disclaimer of warranty and limitation of liability provided -above cannot be given local legal effect according to their terms, -reviewing courts shall apply local law that most closely approximates -an absolute waiver of all civil liability in connection with the -Program, unless a warranty or assumption of liability accompanies a -copy of the Program in return for a fee. - - END OF TERMS AND CONDITIONS - - How to Apply These Terms to Your New Programs - - If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make it -free software which everyone can redistribute and change under these terms. - - To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -state the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. - - <one line to give the program's name and a brief idea of what it does.> - Copyright (C) <year> <name of author> - - This program is free software: you can redistribute it and/or modify - it under the terms of the GNU General Public License as published by - the Free Software Foundation, either version 3 of the License, or - (at your option) any later version. - - This program is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU General Public License for more details. - - You should have received a copy of the GNU General Public License - along with this program. If not, see <http://www.gnu.org/licenses/>. - -Also add information on how to contact you by electronic and paper mail. - - If the program does terminal interaction, make it output a short -notice like this when it starts in an interactive mode: - - <program> Copyright (C) <year> <name of author> - This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. - This is free software, and you are welcome to redistribute it - under certain conditions; type `show c' for details. - -The hypothetical commands `show w' and `show c' should show the appropriate -parts of the General Public License. Of course, your program's commands -might be different; for a GUI interface, you would use an "about box". - - You should also get your employer (if you work as a programmer) or school, -if any, to sign a "copyright disclaimer" for the program, if necessary. -For more information on this, and how to apply and follow the GNU GPL, see -<http://www.gnu.org/licenses/>. - - The GNU General Public License does not permit incorporating your program -into proprietary programs. If your program is a subroutine library, you -may consider it more useful to permit linking proprietary applications with -the library. If this is what you want to do, use the GNU Lesser General -Public License instead of this License. But first, please read -<http://www.gnu.org/philosophy/why-not-lgpl.html>. diff --git a/libs/libtox/docs/DONATORS b/libs/libtox/docs/DONATORS deleted file mode 100644 index dcce32c869..0000000000 --- a/libs/libtox/docs/DONATORS +++ /dev/null @@ -1,7 +0,0 @@ -Minnesota > Florida -vdo <vdo@greyfaze.net> -Spitfire is best technicolor horse. -if bad people don't hate you, you're doing something wrong -Pinkie Pie is best pony. -JRS was here -qTox is so bloated it doesn't even fit in a 64-bit address space diff --git a/libs/libtox/docs/README.md b/libs/libtox/docs/README.md deleted file mode 100644 index 7a1ffe7ffa..0000000000 --- a/libs/libtox/docs/README.md +++ /dev/null @@ -1,174 +0,0 @@ -#  - -**Current build status:** [](https://travis-ci.org/TokTok/c-toxcore) -**Current Coverage:** [](https://coveralls.io/github/TokTok/toxcore?branch=master) - -[**Website**](https://tox.chat) **|** [**Wiki**](https://wiki.tox.chat/) **|** [**Blog**](https://blog.tox.chat/) **|** [**FAQ**](https://wiki.tox.chat/doku.php?id=users:faq) **|** [**Binaries/Downloads**](https://wiki.tox.chat/Binaries) **|** [**Clients**](https://wiki.tox.chat/doku.php?id=clients) **|** [**Compiling**](/INSTALL.md) - -**IRC Channels:** Users: [#tox@freenode](https://webchat.freenode.net/?channels=tox), Developers: [#toktok@freenode](https://webchat.freenode.net/?channels=toktok) - -## What is Tox - -Tox is a peer to peer (serverless) instant messenger aimed at making security -and privacy easy to obtain for regular users. It uses -[NaCl](https://nacl.cr.yp.to/) for its encryption and authentication. - -## IMPORTANT! - -###  - -This is an **experimental** cryptographic network library. It has not been -formally audited by an independent third party that specializes in -cryptography or cryptanalysis. **Use this library at your own risk.** - -The underlying crypto library [NaCl](https://nacl.cr.yp.to/install.html) -provides reliable encryption, but the security model has not yet been fully -specified. See [issue 210](https://github.com/TokTok/c-toxcore/issues/210) for -a discussion on developing a threat model. See other issues for known -weaknesses (e.g. [issue 426](https://github.com/TokTok/c-toxcore/issues/426) -describes what can happen if your secret key is stolen). - -## Toxcore Development Roadmap - -The roadmap and changelog are generated from GitHub issues. You may view them -on the website, where they are updated at least once every 24 hours: - -- Changelog: https://toktok.ltd/changelog/c-toxcore -- Roadmap: https://toktok.ltd/roadmap/c-toxcore - -## Installing toxcore - -Detailed installation instructions can be found in [INSTALL.md](INSTALL.md). - -In a nutshell, if you have [libsodium](https://github.com/jedisct1/libsodium) -or [nacl](https://nacl.cr.yp.to/install.html) installed, run: - -```sh -autoreconf -fi -mkdir _build && cd _build -../configure -make -sudo make install -``` - -If you have [libvpx](https://github.com/webmproject/libvpx) and -[opus](https://github.com/xiph/opus) installed, the above will also build the -A/V library for multimedia chats. - -## Using toxcore - -The simplest "hello world" example could be an echo bot. Here we will walk -through the implementation of a simple bot. - -### Creating the tox instance - -All toxcore API functions work with error parameters. They are enums with one -`OK` value and several error codes that describe the different situations in -which the function might fail. - -```c -TOX_ERR_NEW err_new; -Tox *tox = tox_new(NULL, &err_new); -if (err_new != TOX_ERR_NEW_OK) { - fprintf(stderr, "tox_new failed with error code %d\n", err_new); - exit(1); -} -``` - -Here, we simply exit the program, but in a real client you will probably want -to do some error handling and proper error reporting to the user. The `NULL` -argument given to the first parameter of `tox_new` is the `Tox_Options`. It -contains various write-once network settings and allows you to load a -previously serialised instance. See [toxcore/tox.h](tox.h) for details. - -### Setting up callbacks - -Toxcore works with callbacks that you can register to listen for certain -events. Examples of such events are "friend request received" or "friend sent -a message". Search the API for `tox_callback_*` to find all of them. - -Here, we will set up callbacks for receiving friend requests and receiving -messages. We will always accept any friend request (because we're a bot), and -when we receive a message, we send it back to the sender. - -```c -tox_callback_friend_request(tox, handle_friend_request); -tox_callback_friend_message(tox, handle_friend_message); -``` - -These two function calls set up the callbacks. Now we also need to implement -these "handle" functions. - -### Handle friend requests - -```c -static void handle_friend_request( - Tox *tox, const uint8_t *public_key, const uint8_t *message, size_t length, - void *user_data) { - // Accept the friend request: - TOX_ERR_FRIEND_ADD err_friend_add; - tox_friend_add_norequest(tox, public_key, &err_friend_add); - if (err_friend_add != TOX_ERR_FRIEND_ADD_OK) { - fprintf(stderr, "unable to add friend: %d\n", err_friend_add); - } -} -``` - -The `tox_friend_add_norequest` function adds the friend without sending them a -friend request. Since we already got a friend request, this is the right thing -to do. If you wanted to send a friend request yourself, you would use -`tox_friend_add`, which has an extra parameter for the message. - -### Handle messages - -Now, when the friend sends us a message, we want to respond to them by sending -them the same message back. This will be our "echo". - -```c -static void handle_friend_message( - Tox *tox, uint32_t friend_number, TOX_MESSAGE_TYPE type, - const uint8_t *message, size_t length, - void *user_data) { - TOX_ERR_FRIEND_SEND_MESSAGE err_send; - tox_friend_send_message(tox, friend_number, type, message, length, - &err_send); - if (err_send != TOX_ERR_FRIEND_SEND_MESSAGE_OK) { - fprintf(stderr, "unable to send message back to friend %d: %d\n", - friend_number, err_send); - } -} -``` - -That's it for the setup. Now we want to actually run the bot. - -### Main event loop - -Toxcore works with a main event loop function `tox_iterate` that you need to -call at a certain frequency dictated by `tox_iteration_interval`. This is a -polling function that receives new network messages and processes them. - -```c -while (true) { - usleep(1000 * tox_iteration_interval(tox)); - tox_iterate(tox, NULL); -} -``` - -That's it! Now you have a working echo bot. The only problem is that since Tox -works with public keys, and you can't really guess your bot's public key, you -can't add it as a friend in your client. For this, we need to call another API -function: `tox_self_get_address(tox, address)`. This will fill the 38 byte -friend address into the `address` buffer. You can then display that binary -string as hex and input it into your client. Writing a `bin2hex` function is -left as exercise for the reader. - -We glossed over a lot of details, such as the user data which we passed to -`tox_iterate` (passing `NULL`), bootstrapping into an actual network (this bot -will work in the LAN, but not on an internet server) and the fact that we now -have no clean way of stopping the bot (`while (true)`). If you want to write a -real bot, you will probably want to read up on all the API functions. Consult -the API documentation in [toxcore/tox.h](tox.h) for more information. - -### Other resources - -- [Another echo bot](https://wiki.tox.chat/developers/client_examples/echo_bot) |