From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] procrank_linux: new package
Date: Tue, 23 Feb 2016 21:26:47 +0100 [thread overview]
Message-ID: <56CCC087.9060506@mind.be> (raw)
In-Reply-To: <1456242888-23322-1-git-send-email-gustavo.zacarias@free-electrons.com>
On 02/23/16 16:54, gustavo.zacarias at free-electrons.com wrote:
> From: Gustavo Zacarias <gustavo.zacarias@free-electrons.com>
>
> Signed-off-by: Gustavo Zacarias <gustavo.zacarias@free-electrons.com>
> ---
> package/Config.in | 3 +++
> package/procrank_linux/Config.in | 7 +++++++
> package/procrank_linux/procrank_linux.mk | 21 +++++++++++++++++++++
You forgot to add a hash file.
> 3 files changed, 31 insertions(+)
> create mode 100644 package/procrank_linux/Config.in
> create mode 100644 package/procrank_linux/procrank_linux.mk
>
> diff --git a/package/Config.in b/package/Config.in
> index 00132df..c1be419 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -1595,6 +1595,9 @@ endif
> source "package/powerpc-utils/Config.in"
> if BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
> source "package/procps-ng/Config.in"
> +endif
> + source "package/procrank_linux/Config.in"
> +if BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
> source "package/psmisc/Config.in"
> endif
> source "package/pwgen/Config.in"
> diff --git a/package/procrank_linux/Config.in b/package/procrank_linux/Config.in
> new file mode 100644
> index 0000000..59d462b
> --- /dev/null
> +++ b/package/procrank_linux/Config.in
> @@ -0,0 +1,7 @@
> +config BR2_PACKAGE_PROCRANK_LINUX
> + bool "procrank_linux"
> + help
> + procrank is a tool commonly used by Android platform
> + developers to find out how much memory is really being used.
> +
> + https://github.com/csimmonds/procrank_linux
> diff --git a/package/procrank_linux/procrank_linux.mk b/package/procrank_linux/procrank_linux.mk
> new file mode 100644
> index 0000000..7e74319
> --- /dev/null
> +++ b/package/procrank_linux/procrank_linux.mk
> @@ -0,0 +1,21 @@
> +################################################################################
> +#
> +# procrank_linux
> +#
> +################################################################################
> +
> +PROCRANK_LINUX_VERSION = 21c30ab4514a5b15ac6e813e21bee0d3d714cb08
> +PROCRANK_LINUX_SITE = $(call github,csimmonds,procrank_linux,$(PROCRANK_LINUX_VERSION))
> +PROCRANK_LINUX_LICENSE = Apache-2.0
> +PROCRANK_LINUX_LICENSE_FILES = NOTICE
Check. There's a Makefile licensed GPLv2+ but I guess that's not relevant.
> +
> +define PROCRANK_LINUX_BUILD_CMDS
> + $(TARGET_MAKE_ENV) $(MAKE) -C $(@D) CROSS_COMPILE="$(TARGET_CROSS)"
What a horrible Makefile... There is no way to pass CFLAGS and LDFLAGS.
Fortunately, with the toolchain wrapper, this shouldn't be a problem anymore.
Well, except for LDFLAGS. This _is_ going to be a problem on e.g. Blackfin FLAT.
I guess a patch adding CFLAGS and LDFLAGS to the Makefiles would be upstreamable?
Regards,
Arnout
> +endef
> +
> +define PROCRANK_LINUX_INSTALL_TARGET_CMDS
> + $(INSTALL) -m 0755 -D $(@D)/procrank \
> + $(TARGET_DIR)/usr/bin/procrank
> +endef
> +
> +$(eval $(generic-package))
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-02-23 20:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 15:54 [Buildroot] [PATCH] procrank_linux: new package gustavo.zacarias at free-electrons.com
2016-02-23 20:26 ` Arnout Vandecappelle [this message]
2016-02-23 20:36 ` Gustavo Zacarias
2016-02-23 21:06 ` Thomas Petazzoni
2016-02-23 21:35 ` Arnout Vandecappelle
2016-03-06 15:13 ` Thomas Petazzoni
2016-03-06 15:13 ` 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=56CCC087.9060506@mind.be \
--to=arnout@mind.be \
--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 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.