All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Stephen Warren
	<swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [cbootimage-configs PATCH] Build using Makefiles, add separate bct/img targets
Date: Fri, 04 Oct 2013 13:33:48 -0600	[thread overview]
Message-ID: <524F181C.8010502@wwwdotorg.org> (raw)
In-Reply-To: <1380827425-9816-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

On 10/03/2013 01:10 PM, Stephen Warren wrote:
> From: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> 
> In some situations, one may only need BCT binaries and not flashable
> image binaries. Hence, it's useful to allow BCTs and flashable image
> to be built separately, rather than always building both together.
> 
> While re-writing the build system, convert from shell-scripts to
> Makefiles. Now, one can "make", "make bcts", or "make images", all with
> appropriate dependency checking.
> 
> Many Avionic Design boards use a carrier/module design, with the carrier
> and module files stored in separate directories. Use symlinks to handle
> this, rather than complicating the build system with support for files
> from other directories.

Applied.

      parent reply	other threads:[~2013-10-04 19:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-03 19:10 [cbootimage-configs PATCH] Build using Makefiles, add separate bct/img targets Stephen Warren
     [not found] ` <1380827425-9816-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-10-04 19:33   ` Stephen Warren [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=524F181C.8010502@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.