thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jeeyoung kim <jeeyou...@gmail.com>
Subject Re: Recommended way to incorporate thrift to the build system.
Date Fri, 03 Jun 2011 21:11:08 GMT
More update on my side.

I was looking at a CMake module that does very similar thing - mainly, CMake
module that compiles Google Protobuf.

http://cmake.org/gitweb?p=cmake.git;a=blob_plain;f=Modules/FindProtobuf.cmake;hb=HEAD

<http://cmake.org/gitweb?p=cmake.git;a=blob_plain;f=Modules/FindProtobuf.cmake;hb=HEAD>it
creates a new target, with its own input target (*.proto files) and output
targets (*.cc and *.h files).

I think one the major different (with respect to build system) between
protobuf and thrift is that with protobuf, you can predict what the output
files are going to be for the compiled protobuf files (x.proto generates
x.pb.cc and x.pb.h), but with thrift, you cannot know it unless you read the
actual *.thrift file, because each services generate its own file.

On Thu, Jun 2, 2011 at 11:27 AM, jeeyoung kim <jeeyoungk@gmail.com> wrote:

> Hey guys.
>
> I was wondering what is the recommended way to incorporate thrift into to
> the build system. Right now, for the build system @ work, we just compile
> the *.thrift file, and commit them in the source repository. This works, but
> it doesn't feel very comfortable committing automatically generated files.
>
> For other builds @ work, we're using CMake to compile the c++ project. Any
> solution that uses make / cmake / some other build system would be
> appreciated. thanks.
>
> -Jee
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message