tor/config.rust.in

# Used by our cargo build.rs script to get variables from autoconf.
#
# The "configure" script will generate "config.rust" from "config.rust.in",
# and then build.rs will read "config.rust".

BUILDDIR=@BUILDDIR@
TOR_LDFLAGS_zlib=@TOR_LDFLAGS_zlib@
TOR_LDFLAGS_nss=@TOR_LDFLAGS_nss@
TOR_LDFLAGS_openssl=@TOR_LDFLAGS_openssl@
TOR_LDFLAGS_libevent=@TOR_LDFLAGS_libevent@
TOR_ZLIB_LIBS=@TOR_ZLIB_LIBS@
TOR_LIB_MATH=@TOR_LIB_MATH@
TOR_LIBEVENT_LIBS=@TOR_LIBEVENT_LIBS@
TOR_OPENSSL_LIBS=@TOR_OPENSSL_LIBS@
TOR_LIB_WS32=@TOR_LIB_WS32@
TOR_LIB_GDI=@TOR_LIB_GDI@
TOR_LIB_USERENV=@TOR_LIB_USERENV@
CURVE25519_LIBS=@CURVE25519_LIBS@
TOR_SYSTEMD_LIBS=@TOR_SYSTEMD_LIBS@
TOR_LZMA_LIBS=@TOR_LZMA_LIBS@
TOR_ZSTD_LIBS=@TOR_ZSTD_LIBS@
LIBS=@LIBS@
LDFLAGS=@LDFLAGS@
NSS_LIBS=@NSS_LIBS@
Use a rust build script to set linker options correctly for tests. We need this trick because some of our Rust tests depend on our C code, which in turn depend on other native libraries, which thereby pulls a whole mess of our build system into "cargo test". To solve this, we add a build script (build.rs) to set most of the options that we want based on the contents of config.rust. Some options can't be set, and need to go to the linker directly: we use a linker replacement (link_rust.sh) for these. Both config.rust and link_rust.sh are generated by autoconf for us. This patch on its own should enough to make the crypto test build, but not necessarily enough to make it pass. 2018-06-18 23:08:23 +02:00			`# Used by our cargo build.rs script to get variables from autoconf.`
			`#`
			`# The "configure" script will generate "config.rust" from "config.rust.in",`
			`# and then build.rs will read "config.rust".`

			`BUILDDIR=@BUILDDIR@`
			`TOR_LDFLAGS_zlib=@TOR_LDFLAGS_zlib@`
Make the rust tests link. 2018-07-18 16:40:52 +02:00			`TOR_LDFLAGS_nss=@TOR_LDFLAGS_nss@`
Use a rust build script to set linker options correctly for tests. We need this trick because some of our Rust tests depend on our C code, which in turn depend on other native libraries, which thereby pulls a whole mess of our build system into "cargo test". To solve this, we add a build script (build.rs) to set most of the options that we want based on the contents of config.rust. Some options can't be set, and need to go to the linker directly: we use a linker replacement (link_rust.sh) for these. Both config.rust and link_rust.sh are generated by autoconf for us. This patch on its own should enough to make the crypto test build, but not necessarily enough to make it pass. 2018-06-18 23:08:23 +02:00			`TOR_LDFLAGS_openssl=@TOR_LDFLAGS_openssl@`
			`TOR_LDFLAGS_libevent=@TOR_LDFLAGS_libevent@`
			`TOR_ZLIB_LIBS=@TOR_ZLIB_LIBS@`
			`TOR_LIB_MATH=@TOR_LIB_MATH@`
			`TOR_LIBEVENT_LIBS=@TOR_LIBEVENT_LIBS@`
			`TOR_OPENSSL_LIBS=@TOR_OPENSSL_LIBS@`
			`TOR_LIB_WS32=@TOR_LIB_WS32@`
			`TOR_LIB_GDI=@TOR_LIB_GDI@`
			`TOR_LIB_USERENV=@TOR_LIB_USERENV@`
			`CURVE25519_LIBS=@CURVE25519_LIBS@`
			`TOR_SYSTEMD_LIBS=@TOR_SYSTEMD_LIBS@`
			`TOR_LZMA_LIBS=@TOR_LZMA_LIBS@`
			`TOR_ZSTD_LIBS=@TOR_ZSTD_LIBS@`
			`LIBS=@LIBS@`
			`LDFLAGS=@LDFLAGS@`
Make the rust tests link. 2018-07-18 16:40:52 +02:00			`NSS_LIBS=@NSS_LIBS@`