Hello! On Thu, Jul 13, 2023 at 03:08:19PM -0300, Fabiano Furtado Pessoa Coelho wrote:
> Hello... > > On Wed, Jul 12, 2023 at 9:37 PM Maxim Dounin wrote: > > > > Hello! > > > > On Wed, Jul 12, 2023 at 06:40:21PM -0300, Fabiano Furtado Pessoa Coelho > > wrote: > > > > > Hello... > > > > > > I have compiled NGINX 1.24.0 with "./configure ... --modules-path=<path> > > > ...". > > > > ... > > > /<path>/ngx_http_module1.so;", it works fine. > > > > The "--modules-path" configure option defines a directory where > > dynamic modules will be installed by "make install" and only used > > during installation. > > > > The "load_module" configuration directive, if used with relative > > paths, resolves such paths from "--prefix", much like most of the > > configuration directives. Note the example in the documentation > > (http://nginx.org/r/load_module): > > > > load_module modules/ngx_mail_module.so; > > > > This example assumes the default "--modules-path", so modules are > > installed into the "modules" directory under prefix. > > First of all, thanks for the help. > > Is it a good idea to modify the "load_module" directive to read the > "--modules-path" parameter, if defined by "./configure", to use a > custom relative path instead of default "--prefix" relative path? No, adding yet another option to resolve relative paths in configuration looks like a bad idea to me. Resolving these from prefix looks perfectly correct and expected. -- Maxim Dounin http://mdounin.ru/ _______________________________________________ nginx mailing list nginx@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx
