From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Nginx package
Date: Sat, 26 Dec 2015 15:42:09 +0100 [thread overview]
Message-ID: <20151226154209.488813de@free-electrons.com> (raw)
In-Reply-To: <567E84A7.70302@gmail.com>
Geoffrey,
On Sat, 26 Dec 2015 13:14:31 +0100, Geoffrey Ragot wrote:
> the pb is that luajit (in the context) is not a builtin module of nginx.
> It has to be built in a directory and nginx has to be compiled with
> "--add-module <path_to_luajit>".
>
> The nginx package has an option to specify "--add-module" arguments but
> in this case, the dependency is not clearly mentionned in nginx.mk.
> I have to care about build luajit before nginx to ensure that
> <path_to_luajit> contains required files.
I see two options here:
(1) If you really need to have the source of the Nginx Lua module
extracted before building nginx in order to use the --add-module
option, then you will have to create a package like nginx-lua,
that only downloads/extracts the module source code (and does not
build/install it). Then you change the nginx package to depend on
this nginx-lua package, and you pass --add-module=$(NGINX_LUA_DIR).
(2) If however, it is possible to build nginx-lua after nginx, then
you can do a better and more traditional packaging. Even though
they document --add-module as being the way of building nginx-lua,
all it seems to do during nginx configure is calling the "config"
script from nginx-lua, and then the "config.make" script. So I am
pretty sure it is possible to build nginx-lua after nginx.
If it is possible, (2) would be preferred.
Note that this is clearly not a trivial package to create.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-26 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 9:27 [Buildroot] Nginx package Geoffrey Ragot
2015-12-26 9:58 ` Thomas Petazzoni
2015-12-26 12:14 ` Geoffrey Ragot
2015-12-26 14:42 ` Thomas Petazzoni [this message]
2015-12-26 15:46 ` Danomi Manchego
2015-12-26 16:58 ` Geoffrey Ragot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151226154209.488813de@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.