chore(config) better support NGX_WASM_CARGO=0 #386
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The existing NGX_WASM_CARGO=0 variable already allows skipping the Cargo step for building ngx-wasm-rs during
./configure
, but it didn't set the defines needed for each VM configuration.This commit adds the defines when NGX_WASM_CARGO=0 is used, allowing the user to build ngx-wasm-rs separately if wanted, passing its header and library locations via NGX_BUILD_CC_OPTS and NGX_BUILD_LD_OPTS, or via
--cc-opts
and--ld-opts
flags in the nginxconfigure
script.Includes tests and documentation.
(Nevermind the branch name, the approach taken changed halfway through 😆 )