[
https://issues.apache.org/jira/browse/THRIFT-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861327#comment-15861327
]
Gonzalo Aguilar commented on THRIFT-4037:
-----------------------------------------
If I can comment on this. I must say that autoconf is able to do everything
CMake is able to do but also it gives nice argument like syntax to enable an
disable options.
It's fully integrated on the main linux developments and it can compile cross
chains. We are compiling with autoconf everything. This is, at least, x86,
x86_64, arm, arm64v8, mips. So cross compiling is not a problem.
The good thing also is that you can generate the full compilation system and
package it with the code. Only few cases you need to do an autogen.sh, in that
case you can also do it.
Ok maybe is not the best tool on windows. But I have a friend that has also Mac
Os and it's working perfectly. I suppose that windows guys can use mingw.
For the editor support Eclipse supports autotools since long time ago.
Configure, and build is fully integrated on the project.
> [CMake] As a developer, I want to 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)
