Age | Commit message (Collapse) | Author |
|
This uses a single .cc file containing almost all the code in the
repository to perform whole program analysis.
|
|
Also, avoid the need for putting `_XOPEN_SOURCE` in every test file.
|
|
It's not supported in mingw.
See https://github.com/TokTok/c-toxcore/issues/786.
|
|
|
|
Also, add an auto-test for bootstrap and for LAN discovery.
Bootstrap is never tested otherwise, and LAN discovery is a prerequisite
for everything else. Having these two tests lets us rule out or identify
LAN discovery as a possible cause for test failures.
|
|
This is not used by anything in the code, so we shouldn't have it in the
header.
|
|
This changes only code, no string literals or comments.
|
|
|
|
Also, fix av_test.c, since I broke it last time.
|
|
I hadn't done this for the "fun" code, yet. Also, we should include
system headers after our own headers.
"In general, a module should be implemented by one or more .cpp files.
Each of these .cpp files should include the header that defines their
interface first. This ensures that all of the dependences of the module
header have been properly added to the module header itself, and are not
implicit. System headers should be included after user headers for a
translation unit."
-- http://llvm.org/docs/CodingStandards.html#a-public-header-file-is-a-module
|
|
We run astyle on Travis and check if there is a diff. The build terminates if
git finds a difference.
|
|
Allow users to play with keys generated outside Tox core without
depending on features from any specific client. Just generate a
stub save file that every client will understand.
|
|
https://github.com/nurupo/InsertProjectNameHere
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
JamoBox-master
Conflicts:
toxcore/LAN_discovery.h
|
|
comments so they follow a standard.
|
|
|