You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `NGX_OBJS` name was taken from the nginx buildsystem, but it is an
internal detail there, so the name wasn't really meaningful. Now that
we have `NGINX_SOURCE_DIR`, there's a benefit in more consistent naming.
Technically, not a breaking change, as we haven't had a release with the
old variable name.
Copy file name to clipboardExpand all lines: README.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -78,12 +78,12 @@ For example (all examples plus linux specific):
78
78
### Build with external NGINX source tree
79
79
80
80
If you require a customized NGINX configuration, you can build a module against an existing pre-configured source tree.
81
-
To do that, you need to set the `NGX_OBJS` variable to an _absolute_ path of the NGINX build directory (`--builddir`, defaults to the `objs` in the source directory).
81
+
To do that, you need to set the `NGINX_BUILD_DIR` variable to an _absolute_ path of the NGINX build directory (`--builddir`, defaults to the `objs` in the source directory).
82
82
Only the `./configure` step of the NGINX build is mandatory because bindings don't depend on any of the artifacts generated by `make`.
0 commit comments