Re: [Evolution-hackers] Switching from Autotools to CMake for core evolution products
- From: Owen Taylor <otaylor redhat com>
- To: Michael Catanzaro <mcatanzaro gnome org>, Milan Crha <mcrha redhat com>, desktop-devel-list gnome org
- Cc: distributor-list gnome org, evolution-hackers gnome org
- Subject: Re: [Evolution-hackers] Switching from Autotools to CMake for core evolution products
- Date: Mon, 10 Oct 2016 12:57:20 -0400
On Mon, 2016-10-10 at 11:37 -0500, Michael Catanzaro wrote:
On Mon, 2016-10-10 at 11:51 -0400, Owen Taylor wrote:
To get them building again from HEAD again, what you can do is add
a
compatibility configure script as described in:
I don't want to add compatibility configure scripts to GNOME modules
that switch to CMake or Meson. Continuous should just learn how to
build such modules properly, like JHBuild does.
I agree about whatever we switch GNOME over to en-masse, but for
scattered projects, I'm less sure, and I'm particularly less sure about
CMake, where there seems to be a certain lack of uniformity.
Can you propose what the necessary change would be to:
https://people.gnome.org/~walters/build-api/build-api.md
?
The compatibility
configure scripts can live in the Continuous git repository in the
meantime, for as long as they're needed.
I don't think gnome-continuous should be considered to be some sort
dark corner where things should be shoved that only the "gnome-
continuous maintainers" have to worry about. *All* GNOME maintainers
should consider themselves the maintainers of their module in gnome-
continuous.
- Owen
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]