Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] dropbear: add extra build customization options
Date: Wed, 4 Feb 2015 16:40:05 +0100	[thread overview]
Message-ID: <20150204164005.71f80cb4@free-electrons.com> (raw)
In-Reply-To: <54D23C3E.20300@je-eigen-domein.nl>

Dear Floris Bos,

On Wed, 04 Feb 2015 16:35:26 +0100, Floris Bos wrote:

> Dropbear's SSH client is called dbclient.
> The extra "ssh" convenience symlink is something non-standard the 
> buildroot package made up.
> One cannot pass a $(DROPBEAR_TARGET_BINS) containing "ssh" to the 
> $(MAKE) call, as upstream dropbear has no clue how to make "ssh"

Ok, but then you can still have two separate variables for the
TARGET_BINS and the PROGRAMS, but not have duplication between the
server+client, and server only cases.

Or even:

DROPBEAR_TARGET_BINS = dropbearkey dropbearconvert scp

ifeq ($(BR2_PACKAGE_DROPBEAR_CLIENT),y)
DROPBEAR_TARGET_BINS += dbclient ssh
endif

...
	# Here some comment to explain why we filter out ssh
	$(MAKE) MULTI=1 SCPPROGRESS=1 \
		PROGRAMS=$(filter-out ssh,$(DROPBEAR_TARGET_BINS))
...

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2015-02-04 15:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11 15:43 [Buildroot] [PATCH 1/1] dropbear: add extra build customization options Floris Bos
2014-09-11 15:43 ` [Buildroot] [PATCH 1/1] sqlite: add option to disable fsync Floris Bos
2014-09-11 21:53   ` Thomas Petazzoni
2014-09-13 21:51   ` Peter Korsgaard
2015-02-03 14:04 ` [Buildroot] [PATCH 1/1] dropbear: add extra build customization options Thomas Petazzoni
2015-02-03 17:53   ` Floris Bos
2015-02-03 19:30     ` Thomas Petazzoni
2015-02-04 15:35   ` Floris Bos
2015-02-04 15:40     ` 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=20150204164005.71f80cb4@free-electrons.com \
    --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