You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Roger Meier (JIRA)" <ji...@apache.org> on 2011/03/07 22:20:59 UTC

[jira] Commented: (THRIFT-797) Converting to cmake from autotools

    [ https://issues.apache.org/jira/browse/THRIFT-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003617#comment-13003617 ] 

Roger Meier commented on THRIFT-797:
------------------------------------

Hey folks, is this an option?
Or close the issue and set it to *Won't fix* ?

> Converting to cmake from autotools
> ----------------------------------
>
>                 Key: THRIFT-797
>                 URL: https://issues.apache.org/jira/browse/THRIFT-797
>             Project: Thrift
>          Issue Type: Test
>          Components: Build Process
>         Environment: cmake
>            Reporter: Pierre-Alexandre St-Jean
>              Labels: autotools, build, cmake, compiler, management
>         Attachments: 0001-Make-thrift-compiler-and-cpp-part-compile-with-cmake.patch
>
>
> Replace automake by cmake
> This patch only has parts done ie: the compiler and cpp compiler part.
> This would affect all the project and is only a test. The advantages of cmake is that is is available easily on all platforms and generates makefiles for lots of systems. The only disavantage is that cmake would be a requirement even for non developers would want to build thrift. Also thrift would ease for the port on windows.
> Alternatives would be scons and waf. I am currently doing a test with waf build system too (advantage of waf is that it is standalone and can be packaged with the app)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira