Yes, Shaun, you have to do some tweeks to make cygwin work, but it is definitely possible. I personally found some helpful hints here: http://www.thrift.pl/Thrift-tutorial-installation.html - try it out! If you get errors from .configure, maybe you need to re-build it (the stepps are described at the link above)
-Anait ________________________________________ From: Shaun Wilde [[email protected]] Sent: Tuesday, May 24, 2011 2:46 PM To: [email protected] Subject: RE: Using Thrift on Windows Hi Anait Perhaps, but can anyone tell me that I can use these makefiles and cygwin to make 32 and 64 bit libraries that I can use with windows applications. I see there are some patches available that would make the Thrift compilable without cygwin i.e. windows compiler, which makes me wonder. I did try the cygwin route but encountered errors at ./configure - it started complaining about '\r' at line 16 - but the files are unchanged. Shaun PS - please try to send all messages via the UG as this one appears to have come direct > From: [email protected] > To: [email protected] > Date: Tue, 24 May 2011 07:33:34 -0700 > Subject: RE: Using Thrift on Windows > > Hi Shawn, > The advantage of using cygwin is that you can use Makefile to compile and > build the cpp stuff, so then it boils down to just specifying the correct > compiler and linker options in it. If you have never worked with makefiles, > it might sound complicated at first, but beleive me, after just a couple of > hours of any makefile tutorial online, you'll become a 'makefile pro' ;-) > ________________________________________ > From: Shaun Wilde [[email protected]] > Sent: Monday, May 23, 2011 4:35 PM > To: [email protected] > Subject: RE: Using Thrift on Windows > > Hi AnaitI have the windows exe that can be used to make the stubs from the > .thrift files and I can build the csharp assembly.My problem is with the cpp > stuff for windows, I am assuming that there is a library(static?)that I need > to link to from my application (actually a COM object) and due to the > requirements of .NET on 32 and 64 bit platforms I need to make 32 and 64 bit > versions of that library to linkin with the 32/64 bit version of the COM > object.Will I be able to compile windows compatible libraries in both 32 and > 64 bit using cygwin? > I am not against using cygwin but I'd like for people to use my open source > project without having to go through same build issues (I find complicated > builds that are common amongst open source projects only reduce adoption)Shaun > > From: [email protected] > > To: [email protected] > > Date: Mon, 23 May 2011 09:19:55 -0700 > > Subject: RE: Using Thrift on Windows > > > > > > Hi Shawn, > > I was able to build and compile thrift on Windows using cygwin and patched > > tar ball. I was also able to run thrift service with C++ client and Java > > server. Then I was able to create an all java Thrift service application on > > my Windows XP 32 bit machine, using NetBeans developement environment. It > > all works very well - no problems so far. But as I understand you don't > > want to use cygwin, right? > > > > -Ana > > ________________________________________ > > From: Shaun Wilde [[email protected]] > > Sent: Monday, May 23, 2011 3:54 AM > > To: [email protected] > > Subject: Using Thrift on Windows > > > > Hi > > I am looking at using thrift on an opensource project to replace the > > current WCF/WWSAPI mechanism. However before I invest significant effort > > into getting it all to compile using tools I have not used before, I'd like > > to know whether you, the community, think it is possible. > > Opencover is a .NET codecoverage tool that will need a C++ client (32 and > > 64 bit) to communicate with a C# server to deliver its results. > > Will thrift be able to meet my needs? > > I have downloaded the thrift compiler but there appears to be no other > > binaries (I assume I will have to build them). Does thrift support > > compilation on windows and does it support 32 and 64 bit? > > Is it possible to build thrift without mingw/cygwin? I see a couple of > > patches that seem to indicate that it may be possible; should I apply them > > against the svn head or will they work over the tarball I have downloaded? > > I'd rather not have to download load of utilities and tools unnecessarily > > only to find what I want to do is not possible. > > Has anyone done this and are prepared to share the binaries? I am confused > > as to why the compiler is downloadable (and runs) but nothing else. > > Any help appreciated. > > Shaun > >
