From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [1/1] civetweb: new package
Date: Tue, 27 Aug 2013 21:15:57 +0200 [thread overview]
Message-ID: <20130827211557.1416d328@skate> (raw)
In-Reply-To: <CAG3-AMpi1X5xKO08bE+pfp5Or5qeYWbLiKt33aWBTpqVC4ToTg@mail.gmail.com>
Dear Thomas Davis,
On Tue, 27 Aug 2013 14:54:28 -0400, Thomas Davis wrote:
> I will make the suggested changes and retest and re-submit. To answer
> outstanding questions.
>
> 1. BR2_LARGEFILE is required by SQLITE3 which is a dependency in the
> LUA support.
Ok. This is something you could potentially address by passing
-DSQLITE_DISABLE_LFS to the Sqlite build when !BR2_LARGEFILE. See
package/sqlite/sqlite.mk in Buildroot. But ok, it's not mandatory to
support this use case for civetweb.
So, what I'd like to see is something like:
config BR2_PACKAGE_CIVETWEB_LUA_SUPPORT
bool "lua support"
# required by the bundled sqlite code
depends on BR2_LARGEFILE
comment
Enable Lua support in Civetweb. Note that this will use a
version of Lua and Sqlite bundled within the Civetweb
sources, and not the packages from Buildroot.
comment "lua support requires largefile support in toolchain"
depends on !BR2_LARGEFILE
> 2. DOCUMENT_ROOT is the path from with-in the chroot to the documents
> folder. This is a value written into a configuration file, not an
> actual directory something gets placed in. Normally it would have
> been automatically determined by PREFIX, but in the fake root
> situation it has to overridden so it works correctly inside the
> chroot. It is not an install path itself.
Right, discovered this after having a deeper look at civetweb. Then
please set it to /var/www, which is what we do for other web servers in
Buildroot.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-08-27 19:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 17:57 [Buildroot] [1/1] civetweb: new package Thomas Davis
2013-08-27 18:39 ` Thomas Petazzoni
2013-08-27 18:54 ` Thomas Davis
2013-08-27 19:15 ` Thomas Petazzoni [this message]
2013-08-27 19:28 ` Thomas Davis
2013-08-27 20:50 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2013-08-27 13:32 Thomas Davis
2013-08-27 14:27 ` Thomas De Schampheleire
2013-08-27 14:29 ` Thomas Petazzoni
2013-08-27 14:56 ` Thomas Davis
[not found] ` <CAG3-AMraW=os9fWHuukfn_poxQvwPGJ7OGshb3y66TYdCgSVFA@mail.gmail.com>
2013-08-27 15:43 ` Thomas Petazzoni
2013-08-27 20:12 ` Thomas De Schampheleire
2013-08-27 20:51 ` Thomas Petazzoni
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=20130827211557.1416d328@skate \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox