Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Geoffrey Ragot <geoffreyragot@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Nginx package
Date: Sat, 26 Dec 2015 17:58:04 +0100	[thread overview]
Message-ID: <567EC71C.8070608@gmail.com> (raw)
In-Reply-To: <20151226154209.488813de@free-electrons.com>


Ok.
I will try the second way, it seems to be more straightforward if it works.

Thks for help.

Regards,
Geoffrey Ragot


On 12/26/2015 03:42 PM, Thomas Petazzoni wrote:
> 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

      parent reply	other threads:[~2015-12-26 16:58 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
2015-12-26 15:46       ` Danomi Manchego
2015-12-26 16:58       ` Geoffrey Ragot [this message]

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=567EC71C.8070608@gmail.com \
    --to=geoffreyragot@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox