suricata/rust/Makefile.am

EXTRA_DIST =	Cargo.lock \
		src \
		.cargo/config.in \
		gen-c-headers.py

if HAVE_CARGO_VENDOR
EXTRA_DIST +=	vendor
endif

if HAVE_RUST_VENDOR
FROZEN = --frozen
endif

if !DEBUG
RELEASE = --release
endif

if HAVE_LUA
RUST_FEATURES +=	lua $(LUA_INT8)
endif

if DEBUG
RUST_FEATURES +=	debug
endif

if RUST_CROSS_COMPILE 
RUST_TARGET = --target $(host_triplet)
endif

all-local:
if HAVE_PYTHON
	cd $(top_srcdir)/rust && $(HAVE_PYTHON) ./gen-c-headers.py
endif
if HAVE_CYGPATH
	rustpath=`cygpath -a -t mixed $(abs_top_builddir)`
	cd $(top_srcdir)/rust && @rustup_home@ \
		CARGO_HOME="$(CARGO_HOME)" \
		CARGO_TARGET_DIR="$$rustpath/rust/target" \
		$(CARGO) build $(RELEASE) $(FROZEN) \
			--features "$(RUST_FEATURES)" $(RUST_TARGET)
else
	cd $(top_srcdir)/rust && @rustup_home@ \
		CARGO_HOME="$(CARGO_HOME)" \
		CARGO_TARGET_DIR="$(abs_top_builddir)/rust/target" \
		$(CARGO) build $(RELEASE) $(FROZEN) \
			--features "$(RUST_FEATURES)" $(RUST_TARGET)
endif

clean-local:
	-rm -rf target gen

distclean-local: clean-local
	rm -rf vendor gen Cargo.lock

check:
	CARGO_HOME="$(CARGO_HOME)" @rustup_home@
		$(CARGO) test --features "$(RUST_FEATURES)"

Cargo.lock: Cargo.toml
	CARGO_HOME="$(CARGO_HOME)" @rustup_home@ $(CARGO) \
		generate-lockfile

if HAVE_CARGO_VENDOR
vendor:
	CARGO_HOME="$(CARGO_HOME)" @rustup_home@ $(CARGO) vendor > /dev/null
else
vendor:
endif

# Can only include the headers if we have Python to generate them.
if HAVE_PYTHON
EXTRA_DIST +=	gen/c-headers
gen/c-headers:
	cd $(top_srcdir)/rust && $(HAVE_PYTHON) ./gen-c-headers.py
else
gen/c-headers:
endif
rust/Makefile: Don't include Cargo.toml There is no need to include Cargo.toml in the distribution, it is always generated from Cargo.toml.in during ./configure. 5 years ago			`EXTRA_DIST = Cargo.lock \`
rust: generate headers as part of build 8 years ago			`src \`
			`.cargo/config.in \`
rust: don't fail distcheck if cargo-vendor not found Allow distcheck to pass if cargo vendor is not found by not failing out. It is not required to successfully build a dist tarball, the Rust sources will just not be vendored in. Also don't fail out make dist if Python is not installed. A build will still be successful is Python is available on the end build system. 8 years ago			`gen-c-headers.py`
rust: hook rust into the build Rust is currently optional, use the --enable-rust configure argument to enable Rust. By default Rust will be built in release mode. If debug is enabled then it will be built in debug mode. On make dist, "cargo vendor" will be run to make a local copy of Rust dependencies for the distribution archive file. Add autoconf checks to test for the vendored source, and if it exists setup the build to use the vendored code instead of fetching it from the network. Also, as Cargo requires semantic versioning, the Suricata version had to change from 4.0dev to 4.0.0-dev. 8 years ago
rust: don't fail distcheck if cargo-vendor not found Allow distcheck to pass if cargo vendor is not found by not failing out. It is not required to successfully build a dist tarball, the Rust sources will just not be vendored in. Also don't fail out make dist if Python is not installed. A build will still be successful is Python is available on the end build system. 8 years ago			`if HAVE_CARGO_VENDOR`
			`EXTRA_DIST += vendor`
rust: hook rust into the build Rust is currently optional, use the --enable-rust configure argument to enable Rust. By default Rust will be built in release mode. If debug is enabled then it will be built in debug mode. On make dist, "cargo vendor" will be run to make a local copy of Rust dependencies for the distribution archive file. Add autoconf checks to test for the vendored source, and if it exists setup the build to use the vendored code instead of fetching it from the network. Also, as Cargo requires semantic versioning, the Suricata version had to change from 4.0dev to 4.0.0-dev. 8 years ago			`endif`

			`if HAVE_RUST_VENDOR`
			`FROZEN = --frozen`
			`endif`

			`if !DEBUG`
			`RELEASE = --release`
			`endif`

rust: lua wrapper Rust wrapper for working with lua state. 8 years ago			`if HAVE_LUA`
configure: detect lua integer size Lua 5.1 and 5.3 use a different integer size. Run a test program to set the integer size used in the Rust FFI layer to Rust. 6 years ago			`RUST_FEATURES += lua $(LUA_INT8)`
rust: lua wrapper Rust wrapper for working with lua state. 8 years ago			`endif`

Rust: add 'debug' feature The 'debug' feature is enabled if suricata was configured with the --enabled-debug' flag. If enabled, the SCLogDebug format and calls the logging function as usual. Otherwise, this macro is a no-op (similarly to the C code). 7 years ago			`if DEBUG`
			`RUST_FEATURES += debug`
			`endif`

configure: fixing rust/cargo cross compile command adding --target argument to cargo command line when cross compiling 5 years ago			`if RUST_CROSS_COMPILE`
			`RUST_TARGET = --target $(host_triplet)`
			`endif`

rust: hook rust into the build Rust is currently optional, use the --enable-rust configure argument to enable Rust. By default Rust will be built in release mode. If debug is enabled then it will be built in debug mode. On make dist, "cargo vendor" will be run to make a local copy of Rust dependencies for the distribution archive file. Add autoconf checks to test for the vendored source, and if it exists setup the build to use the vendored code instead of fetching it from the network. Also, as Cargo requires semantic versioning, the Suricata version had to change from 4.0dev to 4.0.0-dev. 8 years ago			`all-local:`
rust: generate headers as part of build 8 years ago			`if HAVE_PYTHON`
rust: cargo fixes for out of tree build 7 years ago			`cd $(top_srcdir)/rust && $(HAVE_PYTHON) ./gen-c-headers.py`
rust: generate headers as part of build 8 years ago			`endif`
rust/mingw: build fixes Fix path passed to cargo by using 'cygpath' if available. 6 years ago			`if HAVE_CYGPATH`
			rustpath=`cygpath -a -t mixed $(abs_top_builddir)`
rustup: handle rustup for sudo and su If rustup is in use, and a user uses sudo or su for the make install, the install may fail with a "no default toolchain" error. To prevent this, detect at configure if rustup is being used, then set RUSTUP_HOME for all calls to cargo. 5 years ago			`cd $(top_srcdir)/rust && @rustup_home@ \`
rust: fix build when source directory has spaces in it Redmine issue: https://redmine.openinfosecfoundation.org/issues/2668 6 years ago			`CARGO_HOME="$(CARGO_HOME)" \`
rust/mingw: build fixes Fix path passed to cargo by using 'cygpath' if available. 6 years ago			`CARGO_TARGET_DIR="$$rustpath/rust/target" \`
			`$(CARGO) build $(RELEASE) $(FROZEN) \`
configure: fixing rust/cargo cross compile command adding --target argument to cargo command line when cross compiling 5 years ago			`--features "$(RUST_FEATURES)" $(RUST_TARGET)`
rust/mingw: build fixes Fix path passed to cargo by using 'cygpath' if available. 6 years ago			`else`
rustup: handle rustup for sudo and su If rustup is in use, and a user uses sudo or su for the make install, the install may fail with a "no default toolchain" error. To prevent this, detect at configure if rustup is being used, then set RUSTUP_HOME for all calls to cargo. 5 years ago			`cd $(top_srcdir)/rust && @rustup_home@ \`
rust: fix build when source directory has spaces in it Redmine issue: https://redmine.openinfosecfoundation.org/issues/2668 6 years ago			`CARGO_HOME="$(CARGO_HOME)" \`
			`CARGO_TARGET_DIR="$(abs_top_builddir)/rust/target" \`
rust: fix (again) out of tree builds As the generated Cargo.toml is shipped as part of a release tarball, build from the source directory but set the cargo CARGO_TARGET_DIR to the build directory. 6 years ago			`$(CARGO) build $(RELEASE) $(FROZEN) \`
configure: fixing rust/cargo cross compile command adding --target argument to cargo command line when cross compiling 5 years ago			`--features "$(RUST_FEATURES)" $(RUST_TARGET)`
rust/mingw: build fixes Fix path passed to cargo by using 'cygpath' if available. 6 years ago			`endif`
rust: hook rust into the build Rust is currently optional, use the --enable-rust configure argument to enable Rust. By default Rust will be built in release mode. If debug is enabled then it will be built in debug mode. On make dist, "cargo vendor" will be run to make a local copy of Rust dependencies for the distribution archive file. Add autoconf checks to test for the vendored source, and if it exists setup the build to use the vendored code instead of fetching it from the network. Also, as Cargo requires semantic versioning, the Suricata version had to change from 4.0dev to 4.0.0-dev. 8 years ago
			`clean-local:`
make: Remove rust generated headers during clean 6 years ago			`-rm -rf target gen`
rust: hook rust into the build Rust is currently optional, use the --enable-rust configure argument to enable Rust. By default Rust will be built in release mode. If debug is enabled then it will be built in debug mode. On make dist, "cargo vendor" will be run to make a local copy of Rust dependencies for the distribution archive file. Add autoconf checks to test for the vendored source, and if it exists setup the build to use the vendored code instead of fetching it from the network. Also, as Cargo requires semantic versioning, the Suricata version had to change from 4.0dev to 4.0.0-dev. 8 years ago
rust: cargo fixes for out of tree build 7 years ago			`distclean-local: clean-local`
rust: make distcheck fixes 8 years ago			`rm -rf vendor gen Cargo.lock`
rust: hook rust into the build Rust is currently optional, use the --enable-rust configure argument to enable Rust. By default Rust will be built in release mode. If debug is enabled then it will be built in debug mode. On make dist, "cargo vendor" will be run to make a local copy of Rust dependencies for the distribution archive file. Add autoconf checks to test for the vendored source, and if it exists setup the build to use the vendored code instead of fetching it from the network. Also, as Cargo requires semantic versioning, the Suricata version had to change from 4.0dev to 4.0.0-dev. 8 years ago
			`check:`
rust: run tests with same features as build Cargo check wasn't being passed --features so could have a different configuration than the build. 5 years ago			`CARGO_HOME="$(CARGO_HOME)" @rustup_home@`
			`$(CARGO) test --features "$(RUST_FEATURES)"`
rust: build fixes and nom update Update nom to ~3.0. Prefix dependencies with ~, which will allow for newer patch versions only. Minor version updates should get a test before using. Remove Cargo.lock from the repo, but still generate as part of the vendoring process for release builds. This will ensure that all users of a particular distribution tarball will be linking against the same Rust dependencies. 8 years ago
			`Cargo.lock: Cargo.toml`
rustup: handle rustup for sudo and su If rustup is in use, and a user uses sudo or su for the make install, the install may fail with a "no default toolchain" error. To prevent this, detect at configure if rustup is being used, then set RUSTUP_HOME for all calls to cargo. 5 years ago			`CARGO_HOME="$(CARGO_HOME)" @rustup_home@ $(CARGO) \`
			`generate-lockfile`
rust: hook rust into the build Rust is currently optional, use the --enable-rust configure argument to enable Rust. By default Rust will be built in release mode. If debug is enabled then it will be built in debug mode. On make dist, "cargo vendor" will be run to make a local copy of Rust dependencies for the distribution archive file. Add autoconf checks to test for the vendored source, and if it exists setup the build to use the vendored code instead of fetching it from the network. Also, as Cargo requires semantic versioning, the Suricata version had to change from 4.0dev to 4.0.0-dev. 8 years ago
			`if HAVE_CARGO_VENDOR`
			`vendor:`
rustup: handle rustup for sudo and su If rustup is in use, and a user uses sudo or su for the make install, the install may fail with a "no default toolchain" error. To prevent this, detect at configure if rustup is being used, then set RUSTUP_HOME for all calls to cargo. 5 years ago			`CARGO_HOME="$(CARGO_HOME)" @rustup_home@ $(CARGO) vendor > /dev/null`
rust: hook rust into the build Rust is currently optional, use the --enable-rust configure argument to enable Rust. By default Rust will be built in release mode. If debug is enabled then it will be built in debug mode. On make dist, "cargo vendor" will be run to make a local copy of Rust dependencies for the distribution archive file. Add autoconf checks to test for the vendored source, and if it exists setup the build to use the vendored code instead of fetching it from the network. Also, as Cargo requires semantic versioning, the Suricata version had to change from 4.0dev to 4.0.0-dev. 8 years ago			`else`
			`vendor:`
rust: don't fail distcheck if cargo-vendor not found Allow distcheck to pass if cargo vendor is not found by not failing out. It is not required to successfully build a dist tarball, the Rust sources will just not be vendored in. Also don't fail out make dist if Python is not installed. A build will still be successful is Python is available on the end build system. 8 years ago			`endif`

			`# Can only include the headers if we have Python to generate them.`
			`if HAVE_PYTHON`
			`EXTRA_DIST += gen/c-headers`
			`gen/c-headers:`
python: use python path found during configure Also look for Python under more names. For example, on OpenBSD if you just install Python 2, you will only get a python2.7 executable. 8 years ago			`cd $(top_srcdir)/rust && $(HAVE_PYTHON) ./gen-c-headers.py`
rust: don't fail distcheck if cargo-vendor not found Allow distcheck to pass if cargo vendor is not found by not failing out. It is not required to successfully build a dist tarball, the Rust sources will just not be vendored in. Also don't fail out make dist if Python is not installed. A build will still be successful is Python is available on the end build system. 8 years ago			`else`
			`gen/c-headers:`
rust: hook rust into the build Rust is currently optional, use the --enable-rust configure argument to enable Rust. By default Rust will be built in release mode. If debug is enabled then it will be built in debug mode. On make dist, "cargo vendor" will be run to make a local copy of Rust dependencies for the distribution archive file. Add autoconf checks to test for the vendored source, and if it exists setup the build to use the vendored code instead of fetching it from the network. Also, as Cargo requires semantic versioning, the Suricata version had to change from 4.0dev to 4.0.0-dev. 8 years ago			`endif`