StarMirror/toxcore
1
0
Fork 0
mirror of https://github.com/irungentoo/toxcore.git synced 2024-03-22 13:30:51 +08:00
Code Issues Projects Releases Wiki Activity
d573271f03
toxcore/testing/Makefile.inc

94 lines
2.6 KiB
PHP
Raw Normal View History

Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
if BUILD_NTOX
bin_PROGRAMS += nTox
Forward compatibility with automake 1.14 This update makes sure that the build still works with automake prior to 1.12 and at the same time does not give any warnings or errors with automake 1.14
2013-08-30 18:35:48 +08:00
nTox_SOURCES = ../testing/nTox.h \
../testing/nTox.c
Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
nTox_CFLAGS = $(LIBSODIUM_CFLAGS) \
Allow to build vs nacl instead of libsodium By default libsodium is used. Only if --enable-nacl is specified, then nacl will be used instead of libsodium. Pass locations of nacl headers and libraries by using the following options: --with-nacl-headers=/home/me/somewhere/nacl-20110221/build/469/include/amd64/ --with-nacl-libs=/home/me/somewhere/nacl-20110221/build/469/lib/amd64/
2013-09-05 18:02:26 +08:00
$(NACL_CFLAGS) \
Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
$(NCURSES_CFLAGS)
nTox_LDADD = $(LIBSODIUM_LDFLAGS) \
Allow to build vs nacl instead of libsodium By default libsodium is used. Only if --enable-nacl is specified, then nacl will be used instead of libsodium. Pass locations of nacl headers and libraries by using the following options: --with-nacl-headers=/home/me/somewhere/nacl-20110221/build/469/include/amd64/ --with-nacl-libs=/home/me/somewhere/nacl-20110221/build/469/lib/amd64/
2013-09-05 18:02:26 +08:00
$(NAC_LDFLAGS) \
Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
libtoxcore.la \
$(LIBSODIUM_LIBS) \
Allow to build vs nacl instead of libsodium By default libsodium is used. Only if --enable-nacl is specified, then nacl will be used instead of libsodium. Pass locations of nacl headers and libraries by using the following options: --with-nacl-headers=/home/me/somewhere/nacl-20110221/build/469/include/amd64/ --with-nacl-libs=/home/me/somewhere/nacl-20110221/build/469/lib/amd64/
2013-09-05 18:02:26 +08:00
$(NACL_LIBS) \
Make nTox work on MinGW/Win32
2013-08-27 19:06:19 +08:00
$(NCURSES_LIBS) \
$(WINSOCK2_LIBS)
Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
endif
Some configuration/build fixes, so building basicaly everything else than the library can be disabled
2013-10-07 07:58:57 +08:00
if BUILD_TESTING
Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
noinst_PROGRAMS += DHT_test \
Messenger_test \
Do not build tox_sync on win32
2013-10-16 23:42:00 +08:00
crypto_speed_test
Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
Forward compatibility with automake 1.14 This update makes sure that the build still works with automake prior to 1.12 and at the same time does not give any warnings or errors with automake 1.14
2013-08-30 18:35:48 +08:00
DHT_test_SOURCES = ../testing/DHT_test.c
Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
Allow to build vs nacl instead of libsodium By default libsodium is used. Only if --enable-nacl is specified, then nacl will be used instead of libsodium. Pass locations of nacl headers and libraries by using the following options: --with-nacl-headers=/home/me/somewhere/nacl-20110221/build/469/include/amd64/ --with-nacl-libs=/home/me/somewhere/nacl-20110221/build/469/lib/amd64/
2013-09-05 18:02:26 +08:00
DHT_test_CFLAGS = $(LIBSODIUM_CFLAGS) \
$(NACL_CFLAGS)
Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
DHT_test_LDADD = $(LIBSODIUM_LDFLAGS) \
Allow to build vs nacl instead of libsodium By default libsodium is used. Only if --enable-nacl is specified, then nacl will be used instead of libsodium. Pass locations of nacl headers and libraries by using the following options: --with-nacl-headers=/home/me/somewhere/nacl-20110221/build/469/include/amd64/ --with-nacl-libs=/home/me/somewhere/nacl-20110221/build/469/lib/amd64/
2013-09-05 18:02:26 +08:00
$(NACL_LDFLAGS) \
Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
libtoxcore.la \
$(LIBSODIUM_LIBS) \
Fix NaCl builds for *BSD 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.
2014-03-23 09:01:45 +08:00
$(NACL_OBJECTS) \
Allow to build vs nacl instead of libsodium By default libsodium is used. Only if --enable-nacl is specified, then nacl will be used instead of libsodium. Pass locations of nacl headers and libraries by using the following options: --with-nacl-headers=/home/me/somewhere/nacl-20110221/build/469/include/amd64/ --with-nacl-libs=/home/me/somewhere/nacl-20110221/build/469/lib/amd64/
2013-09-05 18:02:26 +08:00
$(NACL_LIBS) \
Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
$(WINSOCK2_LIBS)
Messenger_test_SOURCES = \
Forward compatibility with automake 1.14 This update makes sure that the build still works with automake prior to 1.12 and at the same time does not give any warnings or errors with automake 1.14
2013-08-30 18:35:48 +08:00
../testing/Messenger_test.c
Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
Allow to build vs nacl instead of libsodium By default libsodium is used. Only if --enable-nacl is specified, then nacl will be used instead of libsodium. Pass locations of nacl headers and libraries by using the following options: --with-nacl-headers=/home/me/somewhere/nacl-20110221/build/469/include/amd64/ --with-nacl-libs=/home/me/somewhere/nacl-20110221/build/469/lib/amd64/
2013-09-05 18:02:26 +08:00
Messenger_test_CFLAGS = $(LIBSODIUM_CFLAGS) \
$(NACL_CFLAGS)
Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
Messenger_test_LDADD = $(LIBSODIUM_LDFLAGS) \
Allow to build vs nacl instead of libsodium By default libsodium is used. Only if --enable-nacl is specified, then nacl will be used instead of libsodium. Pass locations of nacl headers and libraries by using the following options: --with-nacl-headers=/home/me/somewhere/nacl-20110221/build/469/include/amd64/ --with-nacl-libs=/home/me/somewhere/nacl-20110221/build/469/lib/amd64/
2013-09-05 18:02:26 +08:00
$(NACL_LDFLAGS) \
Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
libtoxcore.la \
$(LIBSODIUM_LIBS) \
Fix NaCl builds for *BSD 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.
2014-03-23 09:01:45 +08:00
$(NACL_OBJECTS) \
Allow to build vs nacl instead of libsodium By default libsodium is used. Only if --enable-nacl is specified, then nacl will be used instead of libsodium. Pass locations of nacl headers and libraries by using the following options: --with-nacl-headers=/home/me/somewhere/nacl-20110221/build/469/include/amd64/ --with-nacl-libs=/home/me/somewhere/nacl-20110221/build/469/lib/amd64/
2013-09-05 18:02:26 +08:00
$(NACL_LIBS) \
Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
$(WINSOCK2_LIBS)
crypto_speed_test_SOURCES = \
Forward compatibility with automake 1.14 This update makes sure that the build still works with automake prior to 1.12 and at the same time does not give any warnings or errors with automake 1.14
2013-08-30 18:35:48 +08:00
../testing/crypto_speed_test.c
Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
crypto_speed_test_CFLAGS = \
Allow to build vs nacl instead of libsodium By default libsodium is used. Only if --enable-nacl is specified, then nacl will be used instead of libsodium. Pass locations of nacl headers and libraries by using the following options: --with-nacl-headers=/home/me/somewhere/nacl-20110221/build/469/include/amd64/ --with-nacl-libs=/home/me/somewhere/nacl-20110221/build/469/lib/amd64/
2013-09-05 18:02:26 +08:00
$(LIBSODIUM_CFLAGS) \
$(NACL_CFLAGS)
Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
crypto_speed_test_LDADD = \
$(LIBSODIUM_LDFLAGS) \
Allow to build vs nacl instead of libsodium By default libsodium is used. Only if --enable-nacl is specified, then nacl will be used instead of libsodium. Pass locations of nacl headers and libraries by using the following options: --with-nacl-headers=/home/me/somewhere/nacl-20110221/build/469/include/amd64/ --with-nacl-libs=/home/me/somewhere/nacl-20110221/build/469/lib/amd64/
2013-09-05 18:02:26 +08:00
$(NACL_LDFLAGS) \
Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
libtoxcore.la \
$(LIBSODIUM_LIBS) \
Fix NaCl builds for *BSD 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.
2014-03-23 09:01:45 +08:00
$(NACL_OBJECTS) \
Allow to build vs nacl instead of libsodium By default libsodium is used. Only if --enable-nacl is specified, then nacl will be used instead of libsodium. Pass locations of nacl headers and libraries by using the following options: --with-nacl-headers=/home/me/somewhere/nacl-20110221/build/469/include/amd64/ --with-nacl-libs=/home/me/somewhere/nacl-20110221/build/469/lib/amd64/
2013-09-05 18:02:26 +08:00
$(NACL_LIBS) \
Implemented autotools based build scripts supported options: --with-dependency-search=DIR will tell configure to look for various dependencies in DIR/include and DIR/lib Alternatively you can also specify libsodium header and libs location with --with-libsodium-headers and --with-libsodium-libs if it is installed elsewhere. Ncurses and libconfig are handled via the default pkg-config way, see ./configure --help=short for detailed information. The tox library is compiled as libtoxcore in shared and static variants, public headers are installed to ${prefix}/include/tox A pkg-config libtoxcore.pc configuration file is provided. Use ./configure --help for a full list of configure options or ./configure --help=short for the options that I added. To generate the configure script after pulling from git use: autoreconf -i To generate a release tarball use: make dist Unit tests are handled by the libcheck library integration that is provided by autotools, use: make check to compile and run the tests. Unit tests are currently optional, i.e. - if the check library is not found on the system, then tests will be disabled. Same goes for nTox and DHT bootstrap daemon - they will be enabled or disabled depending on the availability of ncurses (for nTox) or libconfig (for DHT bootstrap daemon). The above can be also tuned by: --enable-tests / --disable-tests --enable-ntox / --disable-ntox --enable-dht-bootstrap-daemon / --disable-dht-bootstrap-daemon
2013-08-14 02:55:32 +08:00
$(WINSOCK2_LIBS)
Do not build tox_sync on win32
2013-10-16 23:42:00 +08:00
if !WIN32
Tox sync added. Tox sync is a proof of concept bittorrent sync inspired application that uses tox to sync the contents of two folders. Currently only works on POSIX compilant operating systems.
2013-10-05 23:14:06 +08:00
Do not build tox_sync on win32
2013-10-16 23:42:00 +08:00
noinst_PROGRAMS += tox_sync
tox_sync_SOURCES = ../testing/tox_sync.c
tox_sync_CFLAGS = $(LIBSODIUM_CFLAGS) \
Tox sync added. Tox sync is a proof of concept bittorrent sync inspired application that uses tox to sync the contents of two folders. Currently only works on POSIX compilant operating systems.
2013-10-05 23:14:06 +08:00
$(NACL_CFLAGS)
Do not build tox_sync on win32
2013-10-16 23:42:00 +08:00
tox_sync_LDADD = $(LIBSODIUM_LDFLAGS) \
Tox sync added. Tox sync is a proof of concept bittorrent sync inspired application that uses tox to sync the contents of two folders. Currently only works on POSIX compilant operating systems.
2013-10-05 23:14:06 +08:00
$(NACL_LDFLAGS) \
libtoxcore.la \
$(LIBSODIUM_LIBS) \
Fix NaCl builds for *BSD 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.
2014-03-23 09:01:45 +08:00
$(NACL_OBJECTS) \
Tox sync added. Tox sync is a proof of concept bittorrent sync inspired application that uses tox to sync the contents of two folders. Currently only works on POSIX compilant operating systems.
2013-10-05 23:14:06 +08:00
$(NACL_LIBS) \
$(WINSOCK2_LIBS)
Do not build tox_sync on win32
2013-10-16 23:42:00 +08:00
endif
Tox sync added. Tox sync is a proof of concept bittorrent sync inspired application that uses tox to sync the contents of two folders. Currently only works on POSIX compilant operating systems.
2013-10-05 23:14:06 +08:00
Add forgoten source to the dist target
2013-09-02 02:44:26 +08:00
EXTRA_DIST += $(top_srcdir)/testing/misc_tools.c
Some configuration/build fixes, so building basicaly everything else than the library can be disabled
2013-10-07 07:58:57 +08:00
endif
Reference in New Issue Copy Permalink