From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Christian Eggers <ceggers@arri.de>,
openembedded-core@lists.openembedded.org,
Otavio Salvador <otavio.salvador@ossystems.com.br>,
Heiko Schocher <hs@denx.de>, Fabio Estevam <festevam@denx.de>
Subject: Re: [OE-core] [PATCH meta-oe] rtc-tool: Add a recipe
Date: Wed, 26 Jan 2022 14:54:53 +0100 [thread overview]
Message-ID: <YfFSrTW5oTe+5zCe@piout.net> (raw)
In-Reply-To: <CAOMZO5CGeRP5Kdv4LjUz5aBEK--da=OR03O6WLVEcRX9XpbA5Q@mail.gmail.com>
Hello Fabio,
On 24/01/2022 16:18:34-0300, Fabio Estevam wrote:
> Hi Christian,
>
> On Mon, Jan 24, 2022 at 6:57 AM Christian Eggers <ceggers@arri.de> wrote:
> >
> > Hi Fabio,
> >
> > from my experience, custom build systems (including "bare" Makefiles)
> > are often hard to integrate/maintain for distributors.
>
> rtc-tools is a straightforward package and I have sent the Makefile
> patch upstream.
>
> Not sure why it can be hard to integrate or maintain it.
>
> > What about using CMake instead?
>
> I can do that if needed, but it is up to the rtc-tools maintainer, Alexandre.
>
> Alexandre, any advice?
>
My plan is to probably go for the Makefile. I don't think it will cause
any issue and this doesn't care about portability to other systems as
the tool is Linux only.
I'm just checking with buildroot whether they prefer having all the
binaries installed with a single target or if rtc-range has to be
separated out.
rtc-range is supposed to be a debugging tool. I'd also separate it in a
different package.
Note that there is a daemon that should be coming up (well when I will
have time) with the goal of monitoring both battery status and clock
drift.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-01-26 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 15:03 [PATCH meta-oe] rtc-tool: Add a recipe Fabio Estevam
2022-01-24 9:57 ` [OE-core] " Christian Eggers
2022-01-24 19:18 ` Fabio Estevam
2022-01-24 19:47 ` Christian Eggers
2022-01-26 13:54 ` Alexandre Belloni [this message]
2022-01-26 18:15 ` Khem Raj
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=YfFSrTW5oTe+5zCe@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=ceggers@arri.de \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=hs@denx.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
/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.