yes, as soon as we have reached full CMake build autotools can be removed.
However, I guess we need a few months to get it up and running.
So autoconf and CMake will be there for a while.
We will prepare a pull request, during the next two weeks.
-roger
Quoting Henrique Mendonça <hmendo...@gmail.com>:
Hey guys,
I think Roger also meant to only have one build system. Probably only
having both while we port everything to cmake, but only one will be
officially supported at a time.
Not sure how much work is involved for the non-C libraries, wasn't facebook
also using cmake? can we get anything from there?
+1
Henrique
On 25 November 2014 at 21:25, Sergei Nikulov <sergey.niku...@gmail.com>
wrote:
2014-11-24 23:36 GMT+03:00 Roger Meier <ro...@bufferoverflow.ch>:
> Hi all
>
> The Apache Thrift compiler is optionally using CMake already and we had
> very good experience by using CMake also for the cpp library to get it up
> and running on Linux-ARM, Linux-x86, Windows CE and Windows.
>
> I like to propose CMake as an additional build system for Apache Thrift.
>
> Goal: Extend Apache Thrift's *make cross* approach to the build system.
>
> Due to growing field of operating system support, a proper executable
> and library detection mechanism running on as much platforms as possible
> becomes required. The other aspect is simplify the release process and
> package generation process.
>
> As nice side benefit of CMake is the generation of development
environment
> specific solution files(VisualStudio, Eclipse, Xcode, etc. ).
> => No solution files within source tree.
>
> see https://issues.apache.org/jira/browse/THRIFT-2850
>
> What are your thoughts?
>
+1
Look forward to see it in Apache thrift mainline.
The main problem I see is to keep both build systems (autotools & cmake) in
sync.
>
> all the best!
> -roger
>
>
--
Best Regards,
Sergei Nikulov
