summaryrefslogtreecommitdiff
path: root/cmake/ModulePackage.cmake
AgeCommit message (Collapse)Author
2018-09-24Revert "Improve cmake build for MSVC."iphydf
This reverts commit f87f8719d02a9adbc9413256fe22958267cfefee.
2018-09-22Improve cmake build for MSVC.Mick Sayson
2018-02-22Fix toxcore.pc generation.iphydf
It's missing vpx and opus at the moment.
2018-02-18Don't build all the small sub-libraries.iphydf
This caused us to build everything 2-4 times, now we only build it 1-2 times (depending on selection of static/shared builds). The disadvantage is that now it's more up to the reviewer to ensure modularity (we still catch it in the bazel build, though).
2018-01-25Install runtime modules into bin directoryMaxim Biro
Runtime modules, such as executables and shared libraries should be installed into "bin" instead of "lib".
2018-01-22Use <stdlib.h> for alloca on FreeBSD.iphydf
https://www.freebsd.org/cgi/man.cgi?alloca If stdlib.h does not define alloca, and we're using GCC (or Clang), we define the macro ourselves in terms of a GCC builtin.
2018-01-21Make the monolith test a C++ binary.iphydf
This way, developers compile toxcore, toxav, and toxencryptsave as C++ at least once at home, reducing the likelyhood of running into travis failures where we compile as C++ in the windows build.
2018-01-20Remove nTox from the repo.iphydf
It's a maintenance burden nobody uses. Let's make toxic the official console client, instead.
2018-01-15update rpm spec and use variables in cmake instead of hardcoded paths (#624)Smoked Cheese
2018-01-12Fix some typos in code and cmake commentsyangfl
2017-12-28Generate only one large library "libtoxcore".iphydf
This library contains all the code for the old libtoxcore, libtoxav, libtoxdns, and libtoxencryptsave. The build for toxav is still optional, and disabling it causes libtoxcore to simply not contain those symbols and the pkg-config file to not include opus and vpx as dependencies.
2017-04-22Revert "Implement tox_loop"Maxim Biro
This reverts commit 5ff099763b1f56414572e1c12eb2f003117db5a0.
2017-04-01Implement tox_loopAnsa89
2017-01-22Add appveyor build for native windows tests.iphydf
It doesn't compile, yet. A few changes (like VLA support) need to be made before we can enable appveyor as a required PR check.
2017-01-18SO versions for cmake and libtoolCarsten Brandt
this updates the version-sync script to generate proper SO versions which will be used by cmake and libtool to create version symlinks on the system when a library is installed as well as setting the SO version in the binary. To see what this does, you have to configure tox with a prefix: ./configure --prefix=/tmp/tox-with-libtool mkdir cbuild && cd cbuild && cmake -DCMAKE_INSTALL_PREFIX=/tmp/tox-with-cmake .. Then run `make && make install`. in both instances you should see the following installed in `lib/`: libtoxcore.so -> libtoxcore.so.1.4.0 libtoxcore.so.1 -> libtoxcore.so.1.4.0 libtoxcore.so.1.4.0 inside the binary the soname should be the one with .1 and it should not contain the full version: $ objdump -p libtoxcore.so.1.4.0 | grep SONAME SONAME libtoxcore.so.1
2017-01-08Add soversion to library files to generate proper symlinksCarsten Brandt
As mentioned in https://github.com/TokTok/c-toxcore/issues/359#issuecomment-270710463 the current CMake build does not generate version symlinks for library .so files. This is because the version is not specified for library targets. See - https://cmake.org/cmake/help/v3.0/prop_tgt/SOVERSION.html#prop_tgt:SOVERSION - https://cmake.org/cmake/help/v3.0/prop_tgt/VERSION.html#prop_tgt:VERSION Use PROJECT_VERSION_MAJOR and MINOR for SOVERSION because api may break from 0.1 to 0.2 in the 0.x release cycle.
2017-01-05Test a few cmake option combinations before the build.iphydf
This takes a few seconds but allows us to cover cases that aren't checked often.
2016-11-06Enable all possible C compiler warning flags.iphydf
We disable the ones that fire, so we can use -Werror. We can then investigate each warning individually and see whether to fix it or to keep silencing it.
2016-11-02Compile as C++ for windows builds.iphydf
Compiling as C++ changes nothing semantically, but ensures that we don't break C++ compatibility while also retaining C compatibility. C++ compatibility is useful for tooling and additional diagnostics and analyses.
2016-09-26C++ the second round.iphydf
Group chats were changed and now need to be updated. This change got lost in the merge.
2016-09-24Make toxcore code C++ compatible.iphydf
It is still C code, so still compatible with C compilers as well. This change lets us see more clearly where implicit conversions occur by making them explicit.
2016-09-14Add option to build static libraries.iphydf