From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH 2/3] doc: how to build
Date: Fri, 17 May 2013 17:20:31 +0200 [thread overview]
Message-ID: <201305171720.31669.thomas.monjalon@6wind.com> (raw)
In-Reply-To: <5195F303.2080004-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
17/05/2013 11:06, Olivier MATZ :
> On 05/07/2013 05:17 PM, Thomas Monjalon wrote:
> > +Build options
> > + T target template (install default: *) - used with config or install
> > + O output directory (default: build/) - cannot be used with install
> > + V verbose
> > + D debug dependencies
> > + CROSS toolchain prefix
> > + EXTRA_CPPFLAGS preprocessor options
> > + EXTRA_CFLAGS compiler options
> > + EXTRA_LDFLAGS linker options
>
> What do you think of replacing "Build options" by "Build variables" ?
OK
> I think it is not obvious that we have to use V=1 for instance for
> a verbose build.
Is it sufficient to change to "Build variables" ?
I could add "(level number, default: 0)" but, in fact, there is only 2 levels:
empty or any value in V/D variables.
> > +Build targets
> > + format: <arch-machine-execenv-toolchain>
> > + templates in config/defconfig_*:
> > + # make showconfigs
>
> About the "build targets", I suggest to include it in the help of T
> variable. What do you think ?
It is a whole subject described on several lines.
I think it's clearer to have a dedicated section.
--
Thomas
next prev parent reply other threads:[~2013-05-17 15:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 15:17 [PATCH 0/3] make help Thomas Monjalon
[not found] ` <cover.1367939814.git.thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-05-07 15:17 ` [PATCH 1/3] mk: rule showconfigs for configs listing Thomas Monjalon
[not found] ` <43533094849ffdacde83cad14c59364caa39d595.1367939814.git.thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-05-17 9:05 ` Olivier MATZ
[not found] ` <5195F2F2.60107-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-05-17 14:53 ` Thomas Monjalon
2013-05-07 15:17 ` [PATCH 2/3] doc: how to build Thomas Monjalon
[not found] ` <fa5bbf77e53cbef7f33b49b1e8b01e960d0ce4c1.1367939814.git.thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-05-17 9:06 ` Olivier MATZ
[not found] ` <5195F303.2080004-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-05-17 15:20 ` Thomas Monjalon [this message]
2013-05-07 15:17 ` [PATCH 3/3] mk: rule help Thomas Monjalon
[not found] ` <f54b18b23b958789d69e7d5d1376cec813093f9d.1367939814.git.thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-05-17 9:06 ` Olivier MATZ
[not found] ` <5195F309.1080101-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-05-17 15:27 ` Thomas Monjalon
2013-05-28 22:15 ` [PATCH v2 0/3] make help Thomas Monjalon
[not found] ` <cover.1369779070.git.thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-05-28 22:15 ` [PATCH v2 1/3] doc: how to build Thomas Monjalon
2013-05-28 22:15 ` [PATCH v2 2/3] mk: rule showconfigs for configs listing Thomas Monjalon
2013-05-28 22:15 ` [PATCH v2 3/3] mk: rule help Thomas Monjalon
2013-05-30 14:55 ` [PATCH v2 0/3] make help Olivier MATZ
[not found] ` <51A76848.6010902-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-05-30 22:02 ` Thomas Monjalon
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=201305171720.31669.thomas.monjalon@6wind.com \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@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.