From: "André Draszik" <git@andred.net>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking][PATCH 2/2 v2] ncp: add v1.2.4
Date: Fri, 18 Nov 2016 10:09:04 +0000 [thread overview]
Message-ID: <1479463744.27546.7.camel@andred.net> (raw)
In-Reply-To: <CAMKF1sqxxyjaYL2EJXD_KzGGMYuB5ohWvye9ba-YrJ6e0pU1Gg@mail.gmail.com>
On Thu, 2016-11-17 at 09:10 -0800, Khem Raj wrote:
> On Thu, Nov 17, 2016 at 3:59 AM, André Draszik <git@andred.net> wrote:
> > On Wed, 2016-11-16 at 09:28 -0800, Khem Raj wrote:
> > >
> > > On 11/16/16 1:02 AM, André Draszik wrote:
> > > > Signed-off-by: André Draszik <git@andred.net>
> > > > ---
> > > > meta-networking/recipes-support/ncp/ncp_1.2.4.bb | 32
> > > > ++++++++++++++++++++++++
> > > > 1 file changed, 32 insertions(+)
> > > > create mode 100644 meta-networking/recipes-support/ncp/ncp_1.2.4.bb
> > > >
> > > > diff --git a/meta-networking/recipes-support/ncp/ncp_1.2.4.bb
> > > > b/meta-
> > > > networking/recipes-support/ncp/ncp_1.2.4.bb
> > > > new file mode 100644
> > > > index 0000000..7bbaaad
> > > > --- /dev/null
> > > > +++ b/meta-networking/recipes-support/ncp/ncp_1.2.4.bb
> > > > @@ -0,0 +1,32 @@
> > > > +SUMMARY = "a fast file copy tool for LANs"
> > > > +DESCRIPTION = "ncp is a utility for copying files in a LAN. It has
> > > > absolutely no \
> > > > +security or integrity checking, no throttling, no features, except
> > > > \
> > > > +one: you don't have to type the coordinates of your peer."
> > > > +HOMEPAGE = "http://www.fefe.de/ncp"
> > > > +LICENSE = "GPLv2"
> > > > +LIC_FILES_CHKSUM = "file://${COREBASE}/meta/files/common-
> > > > licenses/GPL-
> > > > 2.0;md5=801f80980d171dd6425610833a22dbe6"
> > > > +DEPENDS = "libowfat"
> > > > +
> > > > +SRC_URI = "https://dl.fefe.de/${BP}.tar.bz2"
> > > > +SRC_URI[md5sum] = "421c4855bd3148b7d0a4342942b4bf13"
> > > > +SRC_URI[sha256sum] =
> > > > "6cfa72edd5f7717bf7a4a93ccc74c4abd89892360e2e0bb095a73c24b9359b88"
> > > > +
> > > > +EXTRA_OEMAKE = "\
> > > > + DIET= \
> > > > + DEBUG=nostrip \
> > > > + CC='${CC}' CFLAGS='${CFLAGS} -I${STAGING_INCDIR}/libowfat'
> > > > LDFLAGS='${LDFLAGS}' \
> > > > +"
> > >
> > > Is setting CC etc. on make cmdline really needed ?
> >
> > Yes, the Makefile sets CC CFLAGS LDFLAGS excplicitly, so make doesn't
> > inherit them from the environment variables, because OE doesn't pass the
> > -e
> > make flag anymore. https://www.gnu.org/software/make/manual/html_node/En
> > viro
> > nment.html#Environment
> >
> > > may be just adding the -I flags to CPPFLAGS is enough ?
> >
> > It doesn't respect CPPFLAGS, but an alternative would be:
> >
> > EXTRA_OEMAKE = "\
> > DIET= \
> > DEBUG=nostrip \
> > -e \
> > "
> > CFLAGS_append = " -I${STAGING_INCDIR}/libowfat"
>
> Thats seems better.
I am not sure I agree. This means one could accidentally override make
variables. Being explicit as in the original version is more deterministic.
Otherwise somebody would have to audit each recipe's makefile once a
variable is added or removed from the bitbake environment. That doesn't
scale. It would appear that the -e flag was removed from EXTRA_OEMAKE in rev
aeb653861a0ec39ea7a014c0622980edcbf653fa for a similar reason... Even the
make manual recommends against using -e.
Andre'
next prev parent reply other threads:[~2016-11-18 10:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 15:43 [meta-networking][PATCH 0/2] ncp - a fast file copy tool for LANs André Draszik
2016-11-15 15:43 ` [meta-networking][PATCH 1/2] libowfat: add v0.31 André Draszik
2016-11-15 15:43 ` [meta-networking][PATCH 2/2] ncp: add v1.2.4 André Draszik
2016-11-16 9:02 ` [meta-networking][PATCH 2/2 v2] " André Draszik
2016-11-16 17:28 ` Khem Raj
2016-11-17 11:59 ` André Draszik
2016-11-17 17:10 ` Khem Raj
2016-11-18 10:09 ` André Draszik [this message]
2016-11-18 17:33 ` Khem Raj
2016-11-18 10:10 ` [meta-networking][PATCH 2/2 v3] " André Draszik
2016-11-15 17:19 ` [meta-networking][PATCH 0/2] ncp - a fast file copy tool for LANs André Draszik
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=1479463744.27546.7.camel@andred.net \
--to=git@andred.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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