From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] gloox: new package
Date: Mon, 18 May 2020 07:19:40 +0200 [thread overview]
Message-ID: <20200518071940.04c47501@windsurf.home> (raw)
In-Reply-To: <87mu652623.fsf@tarshish>
Hello,
On Mon, 18 May 2020 07:57:56 +0300
Baruch Siach <baruch@tkos.co.il> wrote:
> > +GLOOX_CXXFLAGS = $(TARGET_CXXFLAGS)
> > +
> > +ifeq ($(BR2_TOOLCHAIN_HAS_GCC_BUG_85180),y)
> > +GLOOX_CXXFLAGS += -O0
> > +endif
> > +
> > +GLOOX_CONF_ENV = CXXFLAGS="$(GLOOX_CXXFLAGS)"
> > +
> > +ifeq ($(BR2_TOOLCHAIN_HAS_LIBATOMIC),y)
> > +GLOOX_CONF_ENV += LIBS=-latomic
> > +endif
> > +
> > +GLOOX_INSTALL_STAGING = YES
This is usually closer to the top of the file, next the
license/autoreconf variables.
> > +ifeq ($(BR2_PACKAGE_ZLIB),y)
> > +GLOOX_DEPENDENCIES += zlib
> > +endif
> > +
> > +HOST_GLOOX_CONF_ENV += CXXFLAGS="$(HOST_CXXFLAGS)"
This is this needed.
> > +
> > +GLOOX_CONF_OPTS = \
> > + --with-pic \
Please indent with one tab. Also --with-pic should probably only be
added when BR2_STATIC_LIBS is false.
> > + --with-zlib \
>
> This should be conditional on BR2_PACKAGE_ZLIB.
>
> > + --with-libidn=no \
Please use --without-libidn
> > + --enable-getaddrinfo \
> > + --with-gnutls=no \
>
> It would be nice to add conditional support for GnuTLS.
And please use --with-gnutls / --without-gnutls
>
> > + --with-openssl=yes
>
> This should be conditional on OpenSSL. You also need to add it to
> DEPENDENCIES to make sure it builds before gloox.
And use --with-openssl / --without-openssl, instead of
--with-openssl=yes / --with-openssl=no.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-05-18 5:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 20:08 [Buildroot] [PATCH 1/1] gloox: new package Yair Ben-Avraham
2020-05-18 4:57 ` Baruch Siach
2020-05-18 5:19 ` Thomas Petazzoni [this message]
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=20200518071940.04c47501@windsurf.home \
--to=thomas.petazzoni@bootlin.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