Mailing-List: contact dev-help@thrift.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@thrift.apache.org
Date: Fri, 10 Feb 2017 18:49:41 +0000 (UTC)
From: "James E. King, III (JIRA)" <jira@apache.org>
To: dev@thrift.apache.org
Message-ID: <JIRA.13036641.1484937423000.50684.1486752581709@Atlassian.JIRA>
In-Reply-To: <JIRA.13036641.1484937423000@Atlassian.JIRA>
References: <JIRA.13036641.1484937423000@Atlassian.JIRA> <JIRA.13036641.1484937423918@jira-lw-us.apache.org>
Subject: [jira] [Updated] (THRIFT-4037) [CMake] Use a single build system
 for thrift to make development easier
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 10 Feb 2017 18:49:49 -0000


     [ https://issues.apache.org/jira/browse/THRIFT-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James E. King, III updated THRIFT-4037:
---------------------------------------
    Summary: [CMake] Use a single build system for thrift to make development easier  (was: [CMake] As a developer, I want to use a single build system for thrift to make development easier)

> [CMake] Use a single build system for thrift to make development easier
> -----------------------------------------------------------------------
>
>                 Key: THRIFT-4037
>                 URL: https://issues.apache.org/jira/browse/THRIFT-4037
>             Project: Thrift
>          Issue Type: Epic
>          Components: Build Process
>    Affects Versions: 0.10.0
>         Environment: All
>            Reporter: James E. King, III
>            Assignee: James E. King, III
>            Priority: Critical
>
> h1. Background
> The thrift project currently carries two build systems.  The original build system is based on autoconf and is used to build a complete deliverable including extensive cross-language testing.
> The other build system was introduced a few years ago, with roots tracing back to THRIFT-797.  CMake allows thrift to build natively on multiple platforms - unix and windows.  Autoconf is no longer under active development with the last release in 2012, and it does not allow for native windows builds using native tools that are used by a majority of consumers.
> Maintaining two build systems for a project incurs a lot of overhead.  Every change that touches the build system needs to be done twice, in two completely different ways.  We need twice as many CI jobs to verify that all of the builds are working, whereas with a single cmake build environment we could likely use a single CI build job per platform that does everything using the docker image on linux and appveyor on windows.
> h1. Proposal
> We should officially deprecate autoconf in favor of cmake, and continue (more aggressively) the effort to make the cmake build environment as functional as the autoconf build environment.  During this transition, folks will be required to make changes to both build systems (which are proven out mostly through the Travis CI build jobs; only CMake is used on AppVeyor).
> h1. Acceptance Criteria
> # autoconf build environment is removed


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)