Hi Fabio, hi Alexandre, On Monday, 24 January 2022, 20:18:34 CET, Fabio Estevam wrote: > Hi Christian, >
_______________________________________________________ Christian Eggers Software Engineer ARRI Arnold & Richter Cine Technik GmbH & Co. Betriebs KG Arriweg 17, 83071 Stephanskirchen www.arri.com +49 8036 3009-3118 [email protected] Get all the latest information from www.arri.com, Facebook, Twitter, Instagram and YouTube. Arnold & Richter Cine Technik GmbH & Co. Betriebs KG Sitz: München - Registergericht: Amtsgericht München - Handelsregisternummer: HRA 57918 Persönlich haftender Gesellschafter: Arnold & Richter Cine Technik GmbH Sitz: München - Registergericht: Amtsgericht München - Handelsregisternummer: HRB 54477 Geschäftsführer: Dr. Michael Neuhäuser; Stephan Schenk; Walter Trauninger; Markus Zeiler > On Mon, Jan 24, 2022 at 6:57 AM Christian Eggers <[email protected]> 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. ok, maybe my statement was a little bit opinion based. It is likely that the OE/Yocto maintainers have a different position to this. I remember that I've read an article (but cannot find it again) that custom build systems regularly causes headaches for distributors (because they usually use custom/no ways for setting compiler switches and installation directories which normally the distributor want to control). Well known systems like autotools (I don't fully understand them) or cmake (I use it) have a standardized interface for setting important switches. Additionally they provide common features like cross-compiling, platform specific stuff, removing build artifacts (clean), installation of generated files or out-of-tree builds. Doing the same in bare Makefiles is possible, but requires much hand-crafted code. Often Makefiles consist of a lot of repetitive code. You can use macros for this. After putting everything into macros, you will have reinvented either cmake or kbuild. > > > What about using CMake instead? > > I can do that if needed, but it is up to the rtc-tools maintainer, Alexandre. I am not involved into rtc-tools and also not much into OE/Yocto. So don't count too much on my opinion and choose the best solution yourself. regards Christia (having created hand-written Makefiles for 13 years)
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#160896): https://lists.openembedded.org/g/openembedded-core/message/160896 Mute This Topic: https://lists.openembedded.org/mt/88625470/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
