suricata/rust/Makefile.am

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

if HAVE_RUST

EXTRA_DIST +=	Cargo.lock

if HAVE_CARGO_VENDOR
EXTRA_DIST +=	vendor
endif

if HAVE_RUST_VENDOR
FROZEN = --frozen
endif

if !DEBUG
RELEASE = --release
endif

RUST_FEATURES =

if HAVE_LUA
RUST_FEATURES +=	lua
endif

if HAVE_RUST_EXTERNAL
RUST_FEATURES +=	experimental
endif

all-local:
if HAVE_PYTHON
	cd $(top_srcdir)/rust && \
		$(HAVE_PYTHON) ./gen-c-headers.py && \
		CARGO_TARGET_DIR=$(abs_builddir)/target \
		CARGO_HOME=$(CARGO_HOME) $(CARGO) build $(RELEASE) $(FROZEN) \
			--features "$(RUST_FEATURES)"
else
	cd $(top_srcdir)/rust && CARGO_TARGET_DIR=$(abs_builddir)/target \
		CARGO_HOME=$(CARGO_HOME) $(CARGO) build $(RELEASE) $(FROZEN) \
			--features "$(RUST_FEATURES)"
endif

clean-local:
	cd $(top_srcdir)/rust && CARGO_TARGET_DIR=$(abs_builddir)/target \
		CARGO_HOME=$(CARGO_HOME) $(CARGO) clean

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

check:
	cd $(top_srcdir)/rust && CARGO_TARGET_DIR=$(abs_builddir)/target \
		CARGO_HOME=$(CARGO_HOME) $(CARGO) test

Cargo.lock: Cargo.toml
	CARGO_HOME=$(CARGO_HOME) $(CARGO) generate-lockfile

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

else # HAVE_RUST

all-local clean-local check vendor:

endif # HAVE_RUST

# 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: 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			`EXTRA_DIST = Cargo.toml \`
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
			`if HAVE_RUST`
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
			`EXTRA_DIST += Cargo.lock`

			`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: --enable-rust-strict to turn warnings into errors 8 years ago			`RUST_FEATURES =`
rust: lua wrapper Rust wrapper for working with lua state. 8 years ago
			`if HAVE_LUA`
rust: --enable-rust-strict to turn warnings into errors 8 years ago			`RUST_FEATURES += lua`
rust: lua wrapper Rust wrapper for working with lua state. 8 years ago			`endif`

Autotools: add switch to build experimental Rust parsers 8 years ago			`if HAVE_RUST_EXTERNAL`
rust: --enable-rust-strict to turn warnings into errors 8 years ago			`RUST_FEATURES += experimental`
Autotools: add switch to build experimental Rust parsers 8 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			`all-local:`
rust: generate headers as part of build 8 years ago			`if HAVE_PYTHON`
rust: make distcheck fixes 8 years ago			`cd $(top_srcdir)/rust && \`
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			`$(HAVE_PYTHON) ./gen-c-headers.py && \`
rust: make distcheck fixes 8 years ago			`CARGO_TARGET_DIR=$(abs_builddir)/target \`
rust: save cargo and CARGO_HOME to variables During configure, substitute the path of cargo, as well as the value of CARGO_HOME as variables. This fixes the case where a user might do: make sudo make install Which will cause the cargo bits to be rebuilt, including re-downloading external crates. By saving these to variables we can be sure that the same values are used during make install as were used during make which prevents the Rust artifacts from being rebuild during "sudo make install". 8 years ago			`CARGO_HOME=$(CARGO_HOME) $(CARGO) build $(RELEASE) $(FROZEN) \`
rust: --enable-rust-strict to turn warnings into errors 8 years ago			`--features "$(RUST_FEATURES)"`
rust: generate headers as part of build 8 years ago			`else`
			`cd $(top_srcdir)/rust && CARGO_TARGET_DIR=$(abs_builddir)/target \`
rust: save cargo and CARGO_HOME to variables During configure, substitute the path of cargo, as well as the value of CARGO_HOME as variables. This fixes the case where a user might do: make sudo make install Which will cause the cargo bits to be rebuilt, including re-downloading external crates. By saving these to variables we can be sure that the same values are used during make install as were used during make which prevents the Rust artifacts from being rebuild during "sudo make install". 8 years ago			`CARGO_HOME=$(CARGO_HOME) $(CARGO) build $(RELEASE) $(FROZEN) \`
rust: --enable-rust-strict to turn warnings into errors 8 years ago			`--features "$(RUST_FEATURES)"`
rust: generate headers as part of build 8 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:`
			`cd $(top_srcdir)/rust && CARGO_TARGET_DIR=$(abs_builddir)/target \`
rust: save cargo and CARGO_HOME to variables During configure, substitute the path of cargo, as well as the value of CARGO_HOME as variables. This fixes the case where a user might do: make sudo make install Which will cause the cargo bits to be rebuilt, including re-downloading external crates. By saving these to variables we can be sure that the same values are used during make install as were used during make which prevents the Rust artifacts from being rebuild during "sudo make install". 8 years ago			`CARGO_HOME=$(CARGO_HOME) $(CARGO) clean`
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
			`distclean-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:`
			`cd $(top_srcdir)/rust && CARGO_TARGET_DIR=$(abs_builddir)/target \`
rust: save cargo and CARGO_HOME to variables During configure, substitute the path of cargo, as well as the value of CARGO_HOME as variables. This fixes the case where a user might do: make sudo make install Which will cause the cargo bits to be rebuilt, including re-downloading external crates. By saving these to variables we can be sure that the same values are used during make install as were used during make which prevents the Rust artifacts from being rebuild during "sudo make install". 8 years ago			`CARGO_HOME=$(CARGO_HOME) $(CARGO) test`
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`
rust: make distcheck fixes 8 years ago			`CARGO_HOME=$(CARGO_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:`
rust: save cargo and CARGO_HOME to variables During configure, substitute the path of cargo, as well as the value of CARGO_HOME as variables. This fixes the case where a user might do: make sudo make install Which will cause the cargo bits to be rebuilt, including re-downloading external crates. By saving these to variables we can be sure that the same values are used during make install as were used during make which prevents the Rust artifacts from being rebuild during "sudo make install". 8 years ago			`CARGO_HOME=$(CARGO_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`

			`else # HAVE_RUST`

			`all-local clean-local check vendor:`

			`endif # HAVE_RUST`

			`# 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`