From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Robert Marko <robimarko@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/mhz: add new package
Date: Mon, 31 Jul 2023 14:49:56 +0200 [thread overview]
Message-ID: <20230731144956.09d56866@windsurf> (raw)
In-Reply-To: <20230731122022.1686951-1-robimarko@gmail.com>
Hello Robert,
On Mon, 31 Jul 2023 14:20:22 +0200
Robert Marko <robimarko@gmail.com> wrote:
> mhz is a tool to mathematically calculate the real running CPU frequency
> and as such has proved as invaluable tool for developing CPUFreq and
> similar features in the kernel.
>
> Its source finally got a license recently so it can be packaged.
>
> Signed-off-by: Robert Marko <robimarko@gmail.com>
> ---
> Changes in v2:
> * Use the Makefile from source and override CC and CFLAGS
> ---
> package/Config.in | 1 +
> package/mhz/Config.in | 6 ++++++
> package/mhz/mhz.hash | 2 ++
> package/mhz/mhz.mk | 21 +++++++++++++++++++++
> 4 files changed, 30 insertions(+)
> create mode 100644 package/mhz/Config.in
> create mode 100644 package/mhz/mhz.hash
> create mode 100644 package/mhz/mhz.mk
On top of what Baruch said, you also need to add an entry in the
DEVELOPERS file.
> +define MHZ_INSTALL_TARGET_CMDS
> + $(INSTALL) $(@D)/mhz $(TARGET_DIR)/usr/bin/mhz
$(INSTALL) -D -m0755 $(@D)/mhz $(TARGET_DIR)/usr/bin/mhz
is preferred here.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-07-31 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 12:20 [Buildroot] [PATCH v2] package/mhz: add new package Robert Marko
2023-07-31 12:24 ` Baruch Siach via buildroot
2023-07-31 12:51 ` Thomas Petazzoni via buildroot
2023-07-31 12:49 ` Thomas Petazzoni via buildroot [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=20230731144956.09d56866@windsurf \
--to=buildroot@buildroot.org \
--cc=robimarko@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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.