From: "Nicolas Ménégale" <nicolas.menegale@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] cppcms: new package
Date: Thu, 1 Aug 2013 10:16:11 +0200 (CEST) [thread overview]
Message-ID: <146708706.4277516.1375344971763.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <20130731190437.6757ad8e@skate>
Hi Thomas,
Thanks a lot for the investigation and the rework.
I'll add these functionalities to cppcms in the future, now that we have a clean basis.
Thanks,
Nicolas.
----- Mail original -----
> De: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>
> ?: "Nicolas M?n?gale" <nicolas.menegale@openwide.fr>
> Cc: buildroot at busybox.net
> Envoy?: Mercredi 31 Juillet 2013 19:04:37
> Objet: Re: [Buildroot] [PATCH 1/1] cppcms: new package
>
> Dear Nicolas M?n?gale,
>
> On Thu, 11 Jul 2013 13:42:48 +0200 (CEST), Nicolas M?n?gale wrote:
> > Signed-off-by: Nicolas M?n?gale <nicolas.menegale@openwide.fr>
> > ---
> > v2: iconv/icu related modifications
> > The user can now choose if he want's to build cppcms using icu for
> > having
> > advanced localization features or using iconv.
> > Also in the case that the user uses iconv, if the toolchains
> > already integrate
> > it, iconv won't be compiled.
> > Sorry for the long time it took me to do this modification.
> > CppCMS is a C++ web framework. The cppcms.mk also copy into the
> > host after
> > staging install two scripts needed when you compile an application
> > using the
> > web framework (cppcms_tmpl_cc).
> > As discussed on IRC it's not worth creating an host-cppcms package
> > for one
> > script.
> > ---
> > package/Config.in | 1 +
> > package/cppcms/Config.in | 30 ++++++++++++++++++++++++++++++
> > package/cppcms/cppcms.mk | 24 ++++++++++++++++++++++++
> > 3 files changed, 55 insertions(+)
> > create mode 100644 package/cppcms/Config.in
> > create mode 100644 package/cppcms/cppcms.mk
>
> I've applied this, but I had to do a bit of tuning, because this
> package doesn't build with uClibc, as it uses <monetary.h> functions,
> that don't exist in uClibc. I've added a glibc dependency, and
> removed
> the wchar dependency. Notice that my attempts to build with uClibc
> also
> allowed to discovered that the package should have depended on thread
> support.
>
> Moreover, the package apparently offers optional zlib support,
> optional
> gcrypt support, optional OpenSSL support. It'd be good to support
> that
> in the future.
>
> 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-01 8:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1889525175.688461.1373542455505.JavaMail.root@openwide.fr>
2013-07-11 11:42 ` [Buildroot] [PATCH 1/1] cppcms: new package Nicolas Ménégale
2013-07-24 14:51 ` Nicolas Ménégale
2013-07-31 17:04 ` Thomas Petazzoni
2013-08-01 8:16 ` Nicolas Ménégale [this message]
2013-04-24 15:35 nmenegale
2013-05-13 14:42 ` Nicolas Menegale
2013-05-13 15:21 ` Samuel Martin
2013-05-13 15:46 ` Thomas Petazzoni
2013-05-13 16:13 ` Samuel Martin
2013-05-21 9:58 ` Nicolas Menegale
2013-05-21 10:01 ` Nicolas Menegale
2013-05-21 10:04 ` Nicolas Menegale
2013-05-28 13:04 ` Nicolas Menegale
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=146708706.4277516.1375344971763.JavaMail.root@openwide.fr \
--to=nicolas.menegale@openwide.fr \
--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