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

Hudson commented on THRIFT-2571:
--------------------------------

FAILURE: Integrated in Thrift #1262 (See 
[https://builds.apache.org/job/Thrift/1262/])
THRIFT-2571 Simplify cross compilation using CMake (roger: rev 
311f7157a2dc5285b027cbf0bc517e9e741de687)
* compiler/cpp/src/thriftl.ll
* compiler/cpp/README.md
* compiler/cpp/CMakeLists.txt


> Simplify cross compilation using CMake
> --------------------------------------
>
>                 Key: THRIFT-2571
>                 URL: https://issues.apache.org/jira/browse/THRIFT-2571
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Compiler (General)
>    Affects Versions: 1.0
>            Reporter: Pascal Bach
>            Assignee: Henrique Mendonça
>            Priority: Minor
>             Fix For: 0.9.2
>
>
> Using CMake would simplify cross compilation.
> The for example the same build script can be used to build:
> - Native for Linux using GCC
> - Native for Windows using Visual Studio
> - Cross compile for ARM on Linux
> - Cross compile for Windows form Linux using mingw32
> It also makes it easy to generate project files for Eclipse or Visual Studio.
> h2. Some examples:
> {code:title=Create an eclipse project|borderStyle=solid}
> mkdir build_ec && cd build_ec
> cmake -G "Eclipse CDT4 - Unix Makefiles" ../compiler/cpp
> make
> {code} 
> Now open the folder build_ec using eclipse.
> {code:title=Create a Visual Studio project (Windows only)|borderStyle=solid}
> mkdir build_vs && cd build_vs
> cmake -G "Visual Studio 12" ../compiler/cpp
> {code} 
> Now open the folder build_vs using Visual Studio.
> {code:title=Cross compile using mingw32|borderStyle=solid}
> mkdir build_mingw32 && cd build_mingw32
> cmake -DCMAKE_TOOLCHAIN_FILE=../contrib/mingw32-toolchain.cmake 
> ../compiler/cpp
> make
> {code} 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to