Age | Commit message (Collapse) | Author |
|
We want to use the same libtool style .so versions in both build systems,
ideally both systems should read the version information from the same
configuration file.
This commit introduces an so.version configuration file and sets up
the autotools to use it.
The version numbers in so.version define the ABI compatibility and should be
updated prior to each release.
implements #323
|
|
|
|
These are cheap asserts. I've also replaced the fprintf's with
`LOGGER_ERROR` calls.
|
|
c-tocxocre will start using C99 code, so check if the compiler supports
it and abort in configure with an error if it does not.
closes #413
|
|
|
|
closes #319
|
|
|
|
|
|
Fixes #216.
|
|
We also never really tested this, because we run make distcheck, which
does another configure with default flags instead of the ones we passed.
Fixes #317.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If libsodium can't be found with PKG_CHECK_MODULES, try AC_CHECK_LIB. If that
also fails, abort configure. If a user passes --with-libsodium-libs explicitly,
that overrides the pkg-config found location.
|
|
Fixed bug from merged PR.
Don't build useless files when building with libsodium.
|
|
|
|
|
|
|
|
Autotools requires a bunch of files that toxcore doesn't use or plan to use
in the near future. By adding 'foreign' to AM_INIT_AUTOMAKE autotools stops
being stupid, and works normally.
|
|
|
|
clock_gettime is in OpenBSD's libc
|
|
The spec file gets processed by configure, the version will be filled
in automatically.
To generate an rpm make sure to install rpm-build, then "configure" as you
would usually do, run "make dist", then process the generated tarball
with rpmbuild:
rpmbuild -tb tox-0.0.0.tar.gz
Tested on Fedora 22.
|
|
Modify tar options to allow extra long filen and directory names, if not set
souces under toxencryptsave might not end up in the tarball.
|
|
|
|
libtoxcore.pc now has -lpthread like it's supposed to on systems
where it is needed.
|
|
Tox now uses some crypto_pwhash functions that are only available in the
newer libsodium releases; check this in configure to prevent compile
time errors.
|
|
|
|
|
|
ethernet devices.
Added some code to get real adapter broadcast addresses on windows.
|
|
when supported.
|
|
Fixed possible thread bug with sending A/V packets.
TODO: eventually make toxcore thread safe.
|
|
|
|
|
|
|
|
|
|
|
|
We don't need it anymore. jin-eld pls do not kill
|
|
|
|
|
|
|
|
|
|
|
|
From what I see there is a difference between *BSD and Linux when
linking vs. toxcore which has been bulit vs. the NaCl library:
on Linux it only links if NaCl's object files (i.e. randombytes.o) is
present in the linker options, however on *BSD systems this will cause a
linking error, see:
https://github.com/Tox/toxic/issues/31#issuecomment-38224441
This commit makes sure that we do not add the NaCl object files to our
pkg-config settings on *BSD, but do add them on Linux.
|
|
Make sure the shared lib build is really disabled when compiling vs.
NaCl:
moved settings before libtool initialization
fixed parameter name
|
|
My previous attempt that was supposed to disable shared library builds
with nacl had a side effect which basically disabled shared libs for all
configurations.
Eventhough AC_DISABLE_SHARED was used inside an if clause it seemed to
take over in any case.
I could not find a clean way around this, so had to override internal
libtool variables. Will check with the libtool people regarding a
cleaner implementation.
|
|
|
|
|