Adding a module, config variables unknown
bjoern at pokerstrategy.com
Thu Aug 21 19:07:41 MSD 2008
it seems the absolute path was the problem.
My solution is this:
ln -s /home/myuser/data/development/workspace/ngx_mymodule/src/
I don't know why the absolute path doesn't work. The oddest thing is,
that everything gets compiled perfectly well and that the binary
contains strings containing 'ngx_mymodule', so it's in there.
I'm not sure, why the path is relevant after the compile process
succeeded... but it seems to be. Can anybody explain this to me, please?
Or am I just misinterpreting anything?
> sorry.. That was just the example...
> I used the absolute path of course...
> /home/myuser/data/development/workspace/ngx_accesskey/src/ to be exact.
> Unfortunately, that's not the problem.
> Valery Kholodkov wrote:
>> "Bjoern" <bjoern at pokerstrategy.com> wrote:
>>> Hi everybody,
>>> I have a problem adding a module.
>>> I've downloaded and extracted the nginx sources.
>>> Downloaded the sources of the module called "accesskey".
>>> Extracted the files to a folder let's call it
>>> cd ~/devel/nginx
>>> ./configure --add-module=~/devel/ngx_accesskey/src/
>> Tilde (~) is not going to be expanded here. Use full path.
More information about the nginx