From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [1/1] civetweb: new package
Date: Tue, 27 Aug 2013 22:50:53 +0200 [thread overview]
Message-ID: <20130827225053.45a6b76d@skate> (raw)
In-Reply-To: <CAG3-AMq4Y-+gVWQ_062FjeLh_=HxuvXDqRzCdWEEjOP+WUCBuQ@mail.gmail.com>
Dear Thomas Davis,
On Tue, 27 Aug 2013 15:28:49 -0400, Thomas Davis wrote:
> Thanks once again for the reply and the detailed examination. I will
> see about having a non large file option in the civetweb build and
> test that separately before continuing. I will also add the comment
> about LUA and sqlite3 not coming from buildroot and move the document
> directory as well.
As I said, support non-large file builds is really not mandatory. You
can submit your package without supporting non-large file builds for
the moment, and if you're interested, you can send later a followup
patch to make this possible. But we have plenty of packages that don't
support non-large file builds in Buildroot, so it's not really a
problem to have another one.
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 20:50 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
2013-08-27 19:28 ` Thomas Davis
2013-08-27 20:50 ` Thomas Petazzoni [this message]
-- 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=20130827225053.45a6b76d@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