From: Borislav Petkov <bp@amd64.org> To: Ingo Molnar <mingo@kernel.org>, Arnaldo Carvalho de Melo <acme@infradead.org>, Michal Marek <mmarek@suse.cz>, Sam Ravnborg <sam@ravnborg.org> Cc: LKML <linux-kernel@vger.kernel.org>, Borislav Petkov <borislav.petkov@amd.com> Subject: [PATCH v5 5/5] tools: Connect to the kernel build system Date: Wed, 11 Apr 2012 18:36:18 +0200 [thread overview] Message-ID: <1334162178-17152-6-git-send-email-bp@amd64.org> (raw) In-Reply-To: <1334162178-17152-1-git-send-email-bp@amd64.org> From: Borislav Petkov <borislav.petkov@amd.com> Now you can do $ make tools/<toolname> from the toplevel kernel directory and have the respective tool built. If you want to build and install it, do $ make tools/<toolname>_install $ make tools/<toolname>_clean should clean the respective tool directories. If you want to clean all in tools, simply do $ make tools/clean Also, if you want to get what the possible targets are, simply calling $ make tools/ should give you the short help. $ make tools/install installs all tools, of course. Doh. Cc: Sam Ravnborg <sam@ravnborg.org> Signed-off-by: Borislav Petkov <borislav.petkov@amd.com> --- Makefile | 7 +++++++ tools/Makefile | 10 ++++++++++ 2 files changed, 17 insertions(+) diff --git a/Makefile b/Makefile index 0df3d003a079..f7f738117128 100644 --- a/Makefile +++ b/Makefile @@ -1468,6 +1468,13 @@ kernelrelease: kernelversion: @echo $(KERNELVERSION) +# Clear a bunch of variables before executing the submake +tools/: FORCE + $(Q)$(MAKE) LDFLAGS= MAKEFLAGS= -C $(src)/tools/ + +tools/%: FORCE + $(Q)$(MAKE) LDFLAGS= MAKEFLAGS= -C $(src)/tools/ $* + # Single targets # --------------------------------------------------------------------------- # Single targets are compatible with: diff --git a/tools/Makefile b/tools/Makefile index f87c0ec63e6c..3ae43947a171 100644 --- a/tools/Makefile +++ b/tools/Makefile @@ -14,6 +14,16 @@ help: @echo ' vm - misc vm tools' @echo ' x86_energy_perf_policy - Intel energy policy tool' @echo '' + @echo 'You can do:' + @echo ' $$ make -C tools/<tool>_install' + @echo '' + @echo ' from the kernel command line to build and install one of' + @echo ' the tools above' + @echo '' + @echo ' $$ make tools/install' + @echo '' + @echo ' installs all tools.' + @echo '' @echo 'Cleaning targets:' @echo '' @echo ' all of the above with the "_clean" string appended cleans' -- 1.7.9.3.362.g71319
next prev parent reply other threads:[~2012-04-11 16:36 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-11 16:36 [PATCH v5 0/5] tools: Add a toplevel Makefile Borislav Petkov 2012-04-11 16:36 ` [PATCH v5 1/5] tools: Add Makefile.include Borislav Petkov 2012-04-13 18:14 ` [tip:perf/core] " tip-bot for Borislav Petkov 2012-04-11 16:36 ` [PATCH v5 2/5] tools: Cleanup EXTRA_WARNINGS Borislav Petkov 2012-04-13 18:15 ` [tip:perf/core] " tip-bot for Borislav Petkov 2012-04-11 16:36 ` [PATCH v5 3/5] tools: Add a toplevel Makefile Borislav Petkov 2012-04-13 18:16 ` [tip:perf/core] " tip-bot for Borislav Petkov 2012-04-11 16:36 ` [PATCH v5 4/5] tools: Add a help target Borislav Petkov 2012-04-13 18:17 ` [tip:perf/core] " tip-bot for Borislav Petkov 2012-04-11 16:36 ` Borislav Petkov [this message] 2012-04-11 18:04 ` [PATCH v5 5/5] tools: Connect to the kernel build system Arnaldo Carvalho de Melo 2012-04-11 18:08 ` Arnaldo Carvalho de Melo 2012-04-11 18:19 ` David Ahern 2012-04-11 19:45 ` Borislav Petkov 2012-04-11 19:52 ` Arnaldo Carvalho de Melo 2012-04-12 15:22 ` Borislav Petkov 2012-04-12 15:57 ` Sam Ravnborg 2012-04-12 18:33 ` Arnaldo Carvalho de Melo 2012-04-12 19:16 ` Sam Ravnborg 2012-04-12 19:31 ` Arnaldo Carvalho de Melo 2012-04-12 21:17 ` Alex Riesen 2012-04-13 10:45 ` Borislav Petkov 2012-04-11 19:47 ` Borislav Petkov 2012-04-13 18:18 ` [tip:perf/core] " tip-bot for Borislav Petkov 2012-04-14 6:35 ` Alex Riesen
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=1334162178-17152-6-git-send-email-bp@amd64.org \ --to=bp@amd64.org \ --cc=acme@infradead.org \ --cc=borislav.petkov@amd.com \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@kernel.org \ --cc=mmarek@suse.cz \ --cc=sam@ravnborg.org \ --subject='Re: [PATCH v5 5/5] tools: Connect to the kernel build system' \ /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
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.