Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] norm: new package
Date: Tue, 15 Mar 2016 23:03:17 +0100	[thread overview]
Message-ID: <8737rr8km2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1457516142-7421-1-git-send-email-gustavo@zacarias.com.ar> (Gustavo Zacarias's message of "Wed, 9 Mar 2016 06:35:41 -0300")

>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:

 > Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
 > ---
 >  package/Config.in                           |  1 +
 >  package/norm/0001-fix-bigendian-build.patch | 17 ++++++++++
 >  package/norm/Config.in                      | 15 +++++++++
 >  package/norm/norm.hash                      |  2 ++
 >  package/norm/norm.mk                        | 50 +++++++++++++++++++++++++++++
 >  5 files changed, 85 insertions(+)
 >  create mode 100644 package/norm/0001-fix-bigendian-build.patch
 >  create mode 100644 package/norm/Config.in
 >  create mode 100644 package/norm/norm.hash
 >  create mode 100644 package/norm/norm.mk

 > diff --git a/package/Config.in b/package/Config.in
 > index 433e9a3..24be023 100644
 > --- a/package/Config.in
 > +++ b/package/Config.in
 > @@ -1153,6 +1153,7 @@ menu "Networking"
 >  	source "package/lksctp-tools/Config.in"
 >  	source "package/mongoose/Config.in"
 >  	source "package/neon/Config.in"
 > +	source "package/norm/Config.in"
 >  	source "package/nss-mdns/Config.in"
 >  	source "package/nss-pam-ldapd/Config.in"
 >  	source "package/omniorb/Config.in"

> +################################################################################
 > +#
 > +# norm
 > +#
 > +################################################################################
 > +
 > +NORM_VERSION = 1.5r6
 > +NORM_SITE = http://downloads.pf.itd.nrl.navy.mil/norm/archive
 > +NORM_SOURCE = src-norm-$(NORM_VERSION).tgz
 > +NORM_INSTALL_STAGING = YES
 > +NORM_LICENSE = NRL License
 > +NORM_LICENSE_FILES = LICENSE.TXT
 > +
 > +ifeq ($(BR2_PACKAGE_LIBNETFILTER_QUEUE),y)
 > +NORM_DEPENDENCIES += libnetfilter_queue
 > +endif
 > +
 > +define NORM_CONFIGURE_CMDS
 > +	(cd $(@D); \
 > +		$(TARGET_CONFIGURE_OPTS) \
 > +		./waf configure --prefix=/usr \

The package looks good - But waf is a python script, right? It got me
wondering if we should use our host-python or if we can rely on the
build host having all dependencies?

It seems like we have a mix:

package/glmark2/glmark2.mk:             $(HOST_DIR)/usr/bin/python2 ./waf configure $(GLMARK2_CONF_OPTS) \
package/glmark2/glmark2.mk:     cd $(@D) && $(TARGET_MAKE_ENV) $(HOST_DIR)/usr/bin/python2 ./waf
package/glmark2/glmark2.mk:     cd $(@D) && $(TARGET_MAKE_ENV) $(HOST_DIR)/usr/bin/python2 ./waf install --destdir=$(TARGET_DIR)
package/gstreamer1/gst1-imx/gst1-imx.mk:                $(HOST_DIR)/usr/bin/python2 ./waf configure $(GST1_IMX_CONF_OPTS)
package/gstreamer1/gst1-imx/gst1-imx.mk:                $(HOST_DIR)/usr/bin/python2 ./waf build -j $(PARALLEL_JOBS)
package/gstreamer1/gst1-imx/gst1-imx.mk:                $(HOST_DIR)/usr/bin/python2 ./waf --destdir=$(TARGET_DIR) \
package/jack2/jack2.mk:         $(HOST_DIR)/usr/bin/python2 ./waf configure \
package/jack2/jack2.mk: (cd $(@D); $(HOST_DIR)/usr/bin/python2 ./waf build -j $(PARALLEL_JOBS))
package/jack2/jack2.mk: (cd $(@D); $(HOST_DIR)/usr/bin/python2 ./waf --destdir=$(TARGET_DIR) \
package/jack2/jack2.mk: (cd $(@D); $(HOST_DIR)/usr/bin/python2 ./waf --destdir=$(STAGING_DIR) \
package/libimxvpuapi/libimxvpuapi.mk:   $(TARGET_CONFIGURE_OPTS) $(HOST_DIR)/usr/bin/python2 ./waf configure \
package/libimxvpuapi/libimxvpuapi.mk:   $(HOST_DIR)/usr/bin/python2 ./waf build -j $(PARALLEL_JOBS)
package/libimxvpuapi/libimxvpuapi.mk:   $(HOST_DIR)/usr/bin/python2 ./waf --destdir=$(STAGING_DIR) install
package/libimxvpuapi/libimxvpuapi.mk:   $(HOST_DIR)/usr/bin/python2 ./waf --destdir=$(TARGET_DIR) install
package/samba4/samba4.mk:               ./buildtools/bin/waf configure \

E.G. everything else than samba4 uses host-python2.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2016-03-15 22:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09  9:35 [Buildroot] [PATCH 1/2] norm: new package Gustavo Zacarias
2016-03-09  9:35 ` [Buildroot] [PATCH 2/2] zeromq: add norm support Gustavo Zacarias
2016-03-20 22:09   ` Thomas Petazzoni
2016-03-15 22:03 ` Peter Korsgaard [this message]
2016-03-15 22:14   ` [Buildroot] [PATCH 1/2] norm: new package Gustavo Zacarias
2016-03-15 22:19     ` Peter Korsgaard
2016-03-15 22:22       ` Gustavo Zacarias
2016-03-15 22:33         ` Peter Korsgaard
2016-03-15 22:39           ` Gustavo Zacarias
2016-03-20 22:01 ` 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=8737rr8km2.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