All of 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 13:14:31 +0100	[thread overview]
Message-ID: <567E84A7.70302@gmail.com> (raw)
In-Reply-To: <20151226105836.26a19543@free-electrons.com>


Hello,

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.


On 12/26/2015 10:58 AM, Thomas Petazzoni wrote:
> Hello,
>
> On Sat, 26 Dec 2015 10:27:58 +0100, Geoffrey Ragot wrote:
>
>> I have a question related to packages dependencies.
>>
>> I have a case where i want to compile nginx with some additionnal
>> modules (luajit).
>> I can define modules paths in the nginx config, but i don't find a way
>> to say buildroot to compile these additional modules before nginx,
>> otherwise than modifying nginx dependencies.
> Well, look at nginx.mk, there are plenty of examples:
>
> ifeq ($(BR2_PACKAGE_NGINX_HTTP_SPDY_MODULE),y)
> NGINX_DEPENDENCIES += zlib
> NGINX_CONF_OPTS += --with-http_spdy_module
> endif
>
> If BR2_PACKAGE_NGINX_HTTP_SPDY_MODULE is enabled, then zlib is
> guaranteed to be built before nginx, and the option
> --with-http_spdy_module will be passed to the nginx configure script.
>
> Best regards,
>
> Thomas

  reply	other threads:[~2015-12-26 12:14 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 [this message]
2015-12-26 14:42     ` Thomas Petazzoni
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=567E84A7.70302@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 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.