please send it to oe-devel ml if you intend to propose it for meta-oe On Wed, Jan 26, 2022 at 5:54 AM Alexandre Belloni <alexandre.bell...@bootlin.com> wrote: > > 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 <cegg...@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.
thats fine, well written makefiles can do cross compilation just fine. > > 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 > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#160991): https://lists.openembedded.org/g/openembedded-core/message/160991 Mute This Topic: https://lists.openembedded.org/mt/88625470/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
