From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Richard Weinberger <richard@nod.at>
Cc: David Oberhollenzer <david.oberhollenzer@sigma-star.at>,
linux-mtd@lists.infradead.org, computersforpeace@gmail.com,
gustavo@zacarias.com.ar, otavio@debian.org,
riku.voipio@linaro.org, pascal.bleser@opensuse.org,
mpluskal@suse.com, David Woodhouse <dwmw2@infradead.org>
Subject: Re: mtd-utils: Swtich to autotools based build system
Date: Thu, 28 Jul 2016 23:18:59 +0200 [thread overview]
Message-ID: <20160728231859.5d9f0a6a@free-electrons.com> (raw)
In-Reply-To: <579A737A.6090308@nod.at>
Hello,
On Thu, 28 Jul 2016 23:04:58 +0200, Richard Weinberger wrote:
> Let's ask also package maintainers for their opinion.
> They have to (cross)build and package mtd-utils. :-)
I haven't tested David patches yet, but what I can say is that moving
to autotools is definitely a very, very wise move.
Non-standard hand-written Makefiles are really a pain.
I'll try to give it a test in terms of Buildroot packaging, and report
back.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-28 21:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 15:02 mtd-utils: Swtich to autotools based build system David Oberhollenzer
2016-07-25 15:02 ` [PATCH 1/5] Change build system to autotools David Oberhollenzer
2016-07-25 15:02 ` [PATCH 2/5] Integrate tests into autotools build system David Oberhollenzer
2016-07-25 15:02 ` [PATCH 3/5] Fix paths in .gitignore and add autotools generated files David Oberhollenzer
2016-07-25 15:02 ` [PATCH 4/5] Unify version string printing David Oberhollenzer
2016-07-25 15:02 ` [PATCH 5/5] Integrate/update make_a_release script David Oberhollenzer
2016-07-28 21:04 ` mtd-utils: Swtich to autotools based build system Richard Weinberger
2016-07-28 21:18 ` Thomas Petazzoni [this message]
2016-07-29 9:19 ` Martin Pluskal
2016-08-01 12:14 ` Riku Voipio
2016-08-01 13:05 ` Otavio Salvador
2016-08-01 14:55 ` David Oberhollenzer
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=20160728231859.5d9f0a6a@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=david.oberhollenzer@sigma-star.at \
--cc=dwmw2@infradead.org \
--cc=gustavo@zacarias.com.ar \
--cc=linux-mtd@lists.infradead.org \
--cc=mpluskal@suse.com \
--cc=otavio@debian.org \
--cc=pascal.bleser@opensuse.org \
--cc=richard@nod.at \
--cc=riku.voipio@linaro.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox