Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] lua-resty-http: new package
Date: Fri, 05 May 2017 16:34:56 +0200	[thread overview]
Message-ID: <87ziers773.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CANxTyt6gexW1NkVmi9xgN-A86eO_6A2L8dv_nFwCwLmEYfM=Pg@mail.gmail.com> (Danomi Manchego's message of "Fri, 5 May 2017 09:59:51 -0400")

>>>>> "Danomi" == Danomi Manchego <danomimanchego123@gmail.com> writes:

 >> We currently don't have any explicit handling of the nginx-lua
 >> module. You could conceptually do something with the 'nginx additional
 >> modules' (BR2_PACKAGE_NGINX_ADD_MODULES) option, but there's no
 >> guarantee that nginx builds after luajit.
 >> 
 >> I guess the proper solution would be to add an explicit nginx-lua
 >> module, similar to what we already have for nginx-dav-ext / nginx-naxsi
 >> / nginx-upload.

 > FWIW - that's what we did in our project - an "ngx_lua" package that
 > simply uses generic-package to download and untar the source, and an
 > addition to nginx.mk like this:

 > ifeq ($(BR2_PACKAGE_NGX_LUA),y)
 > NGINX_DEPENDENCIES += ngx_lua luainterpreter

ngx_lua (or nginx-lua to follow the naming convention) should probably
be responsible for pulling in luainterpreter, but OK.

> NGINX_CONF_OPTS += --add-module=$(NGX_LUA_DIR)
 > ifeq ($(BR2_PACKAGE_LUAJIT),y)
 > NGINX_CONF_ENV += LUAJIT_LIB=$(STAGING_DIR)/usr/lib
 > LUAJIT_INC=$(STAGING_DIR)/usr/include
 > endif
 > endif

 > But then we ended up not actually using ngx_lua at all.

Would you be interested in contributing (and maintaining) such a package
in BR?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2017-05-05 14:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04 22:02 [Buildroot] [git commit] lua-resty-http: new package semenak94 at mail.ru
2017-05-05 10:29 ` Peter Korsgaard
2017-05-05 13:59   ` Danomi Manchego
2017-05-05 14:34     ` Peter Korsgaard [this message]
2017-05-05 21:16       ` Danomi Manchego
  -- strict thread matches above, loose matches on Subject: below --
2017-05-04 20:23 Thomas Petazzoni
2017-05-04 21:02 ` Peter Korsgaard

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=87ziers773.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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