[
https://issues.apache.org/jira/browse/THRIFT-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505021#comment-14505021
]
James E. King, III commented on THRIFT-2850:
--------------------------------------------
I would suggest, that since cmake's integration with libraries like boost have
global settings (BOOST_USE_MULTITHREADED, BOOST_USE_STATIC_LIBS,
BOOST_USE_DEBUG_RUNTIME are examples) that we should not allow a single cmake
project to attempt to build both static and shared outputs, just as a single
project does not attempt to build debug and release outputs. Instead, there
should be only one link style and one output style per cmake configuration. If
someone wants to make Debug shared, and release static, that should be two
separate build directories.
> CMake for Apache Thrift
> -----------------------
>
> Key: THRIFT-2850
> URL: https://issues.apache.org/jira/browse/THRIFT-2850
> Project: Thrift
> Issue Type: Improvement
> Components: Build Process
> Environment: all platforms
> Reporter: Roger Meier
> Assignee: Roger Meier
> Labels: cmake, travis
> Attachments: 0001-THRIFT-2850-CMake-for-Apache-Thrift.patch
>
>
> Goal: Extend Apache Thrift's *make cross* approach to the build system.
> Due to growing the 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.
> We are already building Apache Thrift with CMake for Linux-ARM, Linux-x86,
> Windows CE and Windows.
> We are in preparation phase for a pull request here:
> https://github.com/siemens/thrift/commits/cmake-master
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
