You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@thrift.apache.org by Apache Wiki <wi...@apache.org> on 2008/07/01 01:46:22 UTC

[Thrift Wiki] Update of "ThriftInstallationWin32" by JustinLebar

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Thrift Wiki" for change notification.

The following page has been changed by JustinLebar:
http://wiki.apache.org/thrift/ThriftInstallationWin32

The comment on the change is:
Clarifying C++ libraries don't work under Windows

------------------------------------------------------------------------------
- The Thrift C++ runtime library does not currently work on Windows.  This means that you'll be able to make and run the Thrift compiler, but you ''won't'' be able to compile and run the Thrift messaging server.
+ The following instructions are for making the thrift ''compiler'' only.  The Thrift C++ runtime library does not currently work on Windows.  This means that you'll be able to compile Thrift [[ThriftIDL|IDL]] files to C++/Java/Python/etc., but you won't be able to compile and run the generated C++ code under Windows.
  
  == Basic requirements for win32 ==
  Thrift's compiler is written in C++ and designed to be portable, but there are some system requirements:
@@ -34, +34 @@

  	make
  }}}
  
- (You won't be able to make from the root Thrift directory--If you try to make from that directory, you'll get compile errors about PTHREAD_MUTEX_RECURSIVE_NP undeclared.  Making from compiler/cpp creates the Thrift compiler, while making from the root Thrift directory creates the Thrift server.)
+ (You won't be able to make from the root Thrift directory--If you try to make from that directory, you'll get compile errors about PTHREAD_MUTEX_RECURSIVE_NP undeclared.  Making from compiler/cpp creates the Thrift compiler, while making from the root Thrift directory creates, among other things, the Thrift C++ runtime libraries, which are known not to compile under Cygwin/Windows.)
  
  Some language packages must be installed manually using build tools
  better suited to those languages (at the time of this writing, this applies