Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Trent Piepho <tpiepho@impinj.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] rauc: select host-squashfs as a host dependency
Date: Wed, 29 Nov 2017 21:30:10 +0000	[thread overview]
Message-ID: <1511991010.9792.41.camel@impinj.com> (raw)
In-Reply-To: <20171129210644.C2457803E2@busybox.osuosl.org>

On Wed, 2017-11-29 at 22:11 +0100, Thomas Petazzoni wrote:
> 
> +	select BR2_PACKAGE_HOST_SQUASHFS # run-time dependency
>  	help
>  	  RAUC is the Robust Auto-Update Controller developed by
>  	  Pengutronix. Enable this option to build the rauc
> diff --git a/package/rauc/rauc.mk b/package/rauc/rauc.mk
> index 479a583..67ef155 100644
> --- a/package/rauc/rauc.mk
> +++ b/package/rauc/rauc.mk
> @@ -29,7 +29,7 @@ ifeq ($(BR2_PACKAGE_SYSTEMD),y)
>  RAUC_DEPENDENCIES += systemd
>  endif
>  
> -HOST_RAUC_DEPENDENCIES = host-pkgconf host-openssl host-libglib2
> +HOST_RAUC_DEPENDENCIES = host-pkgconf host-openssl host-libglib2 host-squashfs

Would it work to not include the build dependency on host-sqaushfs? 
Since squashfs is a command invoked at run time, rauc doesn't actually
need to be present when building.  Minimize the dependency info, allow
greater parallelism if packages were built in parallel, etc.  Or
perhaps it's easier to always match the config dep with a build dep
even if the latter isn't necessary in some cases?

  reply	other threads:[~2017-11-29 21:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 21:11 [Buildroot] [git commit] rauc: select host-squashfs as a host dependency Thomas Petazzoni
2017-11-29 21:30 ` Trent Piepho [this message]
2017-11-29 21:50   ` 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=1511991010.9792.41.camel@impinj.com \
    --to=tpiepho@impinj.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