You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@thrift.apache.org by Shane Gannon <sg...@hotmail.com> on 2010/01/02 22:26:40 UTC
RE: ThriftMsvcPatch - Make the C++ runtime library be compatible
with Windows and Visual Studio
Rush thanks for your reply. You have more than answered my questions.
I suppose my inquiry was a bit mislead. The C++ code generated by Thrift may be compilable on Windows - but it would need a reference to the Thrift C++ headers/libraries. Without this reference it will fail with errors like "error C2065: 'TProtocol' : undeclared identifier". After going over the documentation again I became worried that it was not compilable on Windows at all. Even with 591. You have happily removed this doubt.
About Cygwin you are correct. It is possible to use it to build the Thrift compiler. I have taken this approach and have been able to generated Java, C#, and C++ code from the .thrift files. But when I try to "make" the C++ library found in "thrift/lib/cpp" it gives me an error (error: `PTHREAD_MUTEX_RECURSIVE_NP' undeclared). So as far as I know, unless I'm making some simple mistake, you cannot build this library from Cygwin.
Like your tech support user I am also using Visual Studio 2008 and came across the need to carry out a conversion from 2005. For me this seems to have worked fine as well. But I'm still having a small issue building the msvc libraries. Its likely a mistake on my part but if you have any suggestions I would appreciate it. Initially when I ran configure.js I supplied the following arguments
cscript configure.js --with-boost-inc=C:\boost\boost_1_36_0 --with-boost-lib=C:\boost\boost_1_36_0\lib
but this produced errors when I built the project either in VS or with nmake. The errors stated that there were problems resolving zlib. I believe that you have documented this library as optional. But I am unsure as to how I can exclude it. So I decided to download and use it. But when I supply
--with-zlib=C:\zlib\ or --with-zlib-inc=C:\zlib\include --with-zlib-lib=C:\zlib\lib
I end up with the following cscript output
C:>cscript configure.js --with-boost-inc=C:\boost\boost_1_36_0 --with-boost-lib=C:\boost\boost_1_36_0\lib --with-zlib=C:\zlib\Check for boost version >= 1.36.0 succeeded!
Found Boost libraries for the configuration tuple {win32, shared, debug} :boost_date_time-vc71-mt-gd-1_36.libboost_system-vc71-mt-gd-1_36.libboost_thread-vc71-mt-gd-1_36.lib
Found Boost libraries for the configuration tuple {win32, shared, release} :boost_date_time-vc71-mt-1_36.libboost_system-vc71-mt-1_36.libboost_thread-vc71-mt-1_36.lib
Found Boost libraries for the configuration tuple {win32, static, debug} :libboost_date_time-vc71-mt-gd-1_36.liblibboost_system-vc71-mt-gd-1_36.liblibboost_thread-vc71-mt-gd-1_36.lib
Found Boost libraries for the configuration tuple {win32, static, release} :libboost_date_time-vc71-mt-1_36.liblibboost_system-vc71-mt-1_36.liblibboost_thread-vc71-mt-1_36.lib
ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, shared, debug}
ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, shared, release}
ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, static, debug}
ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, static, release}
Do you know what could be producing these errors? I think I've setup zlib correctly and am pointing at the right directory/directories. i.e. I download the binary version of zlib 1.2.3 and extracted it to C:\zlib\. Note: I also copied zlib1.dll to both System or System32 but this had no effect.
PS: I'm glad to help you increase the successful trials count. The patch is a sensible addition to Thrift and should make it more accessible to the general audience.
Kind regardsShane
> From: rush@manbert.com
> Subject: Re: ThriftMsvcPatch - Make the C++ runtime library be compatible with Windows and Visual Studio
> Date: Thu, 31 Dec 2009 13:18:36 -0800
> To: thrift-user@incubator.apache.org
>
> Hi Shane,
>
> What 591 does is to make the C++ runtime library buildable in Windows using Visual Studio. What it does NOT do is make the compiler buildable using the same mechanism.
>
> The C++ code that the Thrift compiler generates compiles just fine in Windows. It runs under Windows as long as you have a runtime library to support it. That's what my patch does for you, it makes the runtime libraries easy to build. You will need to run the Thrift compiler on some other platform (or maybe you can build it using the cygwin libraries in Windows, then run it there. I really don't know because we always run the compiler on a Mac platform, then use the generated code on Mac and Windows. And it might be that if you use Cygwin to be able to build the compiler, then you can also use Cygwin to build and use the libraries. Again, I don't know the details.) Once you have generated the C++ code from the compiler you can bring it into your Visual Studio projects and use it there.
>
> I have recently (just before Christmas) done some tech support for another C++ user who is using my patched code in Windows. He was using VS 2008, so had to convert all of the VS projects (they were created with VS 2005). His last email to me said that the conversion worked with no problems, that he had built the libraries under VS 2008, and his application was running without problems. As far as I know, he is the first user besides myself.
>
> I would certainly like to see my code become part of the standard Thrift code. I was waiting for the first release before I started to push for anything. It also seemed good to have a successful user or two. :-) I plan to add my patch to the 0.2 release code, and also to the head of the tree after David Reiss brings in the Facebook modifications, but I'm working on other things at my real job, so have to do that on the side. My employer would also like this code to become part of the distribution, just because it's a pain for us if we have to patch every release that we get.
>
> Does that answer your questions?
>
> Best regards,
> Rush
>
> On Dec 29, 2009, at 2:11 PM, Shane Gannon wrote:
>
> >
> > Hi
> > I've being evaluating Thrift for an upcoming project. A critical part of this evaluation is to determine if Thrift supports C++ on Windows. The Thrift wiki clearly states on its guide to ThriftUsageC++ "The first thing you need to know is that the C++ code generated by Thrift compiles only on Unix based systems".
> > During my research I came across the ThriftMsvcPatch - Make the C++ runtime library be compatible with Windows and Visual Studio (http://issues.apache.org/jira/browse/THRIFT-591).
> > This patch, as far as I understand, allows the Thrift C++ runtime library to be built in Windows with Visual Studio. Up until now I assumed that it also enabled the C++ code generated by Thrift to be executable on Windows. Hence it would make Thrift an ideal candidate. But upon re-reading the description I'm not so sure.
> > Does the msvc patch make Thrift C++ usable in Windows? As opposed to just making the runtime library buildable? Does it make the C++ code generated by Thrift compilable in Windows?
> > Or have I misunderstood completely? Is the C++ code generated by Thrift already runnable on Windows? i.e. It just can't be compiled on Windows.
> > Furthermore will this patch become part of the standard Thrift distribution?
> > PS: Currently my prototyping has only been with C# and Java. For what I've discovered so far I'm quite happy with Thrift. But my inexperience with C++ has caused me to delay on a C++ prototype. It may also be the cause of some mis-conceptions on my part as I'm literally jumping on the C++ fire with this evaluation.
> > RegardsShane Gannon
> > _________________________________________________________________
> > Windows 7: Simplify what you do everyday. Find the right PC for you.
> > http://windows.microsoft.com/shop
>
_________________________________________________________________
Windows 7: Simplify what you do everyday. Find the right PC for you.
http://windows.microsoft.com/shop
Re: ThriftMsvcPatch - Make the C++ runtime library be compatible with Windows and Visual Studio
Posted by Rush Manbert <ru...@manbert.com>.
Now I'm wondering whether the conversion of projects from VS 2005 to 2008 did something strange to the BuildAll and dummyLibthriftz projects that makes them think that they're real. They are both configured as Application projects, so would create exe files if they had any sources in them. The error message you provided really looks like VS is trying to do something real with them. So I guess there could be a problem if you tries to build the entire solution in that case. I can build the solution under VS 2005 with no errors, in all configurations. I have also successfully run the batch build after selecting all configurations of all projects. It just works under 2005. The master solution runs VS separately for each library, and does not build BuildAll. But if you run it in a configuration that wasn't configured, like Win32_Lib_Debug, then it does build dummyLibthriftz because it has to build something.
On the other hand, if you run nmake and use the Makefile, it only tries to build the configurations that were actually configured. In your case, that means DLL Debug and DLL Release because of the --link=shared. So nmake is really the "safest" build. Besides, if you can run "nmake all" you should be able to run "nmake check" which will actually use the libraries in executing programs, run the tests. etc.
Since I can run this stuff with no errors under VS 2005, I'm reduced to suspecting something strange from the conversion to 2008. In that case, using nmake is probably the only thing that would work.
To clarify, I can configure and build successfully without zlib using both the original configure.js and the modified version. The LNK1104 error:
> fatal error LNK1104: cannot open file 'UnknownLibName-not-configured-for_Win32_DLL_Debug.obj'
was because of a bug in the configure script. It was setting things up so that we would build libthriftz, but it wasn't writing the correct zlib filename into the zlib build property sheet file. And if you try to build the libthrift solution, that will try to build libthriftz, and it's going to use the "not configured" filename.
Oh, now the light bulb lights up. Okay, if you configure without zlib, then you open libthrift.sln and build the solution, the build of libthriftz fails with the errors:
C1083: Cannot open include file: 'zlib.h'. No such file or directory.
C1083: Cannot open source file: '.'. Permission denied.
You can build libthrift and libthriftnb, but you can't build libthriftz because it doesn't know a path to the zlib headers, nor does it know of a zlib link library to link against for the DLL configurations. But under VS 2005 you can build dummyLibthriftz.
As I mentioned before, there is another user who converted to VS 2008. I have emailed him and asked how he did the library builds, which might be a clue about why you're having trouble.
- Rush
On Jan 5, 2010, at 1:47 PM, Shane Gannon wrote:
>
> Rush I'm primarily using Visual Studio and the solution at \lib\cpp\msvc\libthrift to build the project by hand. I have also tried the Master Solution and nmake but not since I got your new configure.js.
> Tomorrow I'll exclude BuildAll and dummyLibthriftz from this solution and see if it removes those errors. I'll also delete the configGenerated directory and start over again with nmake. If I see any issues I'll email you with the zip.
> Currently I have no preference for including or excluding zlib in the project at the moment. But I'd be glad to assist you in figuring out the original zlib problem if you wish. Just let me know what you'd like me to do. You say that you can build the project, with and without zlib, and not get that fatal LNK1104 error with the original configure.js? Do you know why this now works?
> RegardsShane
>> From: rush@manbert.com
>> Subject: Re: ThriftMsvcPatch - Make the C++ runtime library be compatible with Windows and Visual Studio
>> Date: Tue, 5 Jan 2010 12:47:25 -0800
>> To: thrift-user@incubator.apache.org
>>
>> Hi Shane,
>>
>> There certainly seems to be something strange going on with your setup. I don't see these errors, but I do recognize the names.
>>
>> Down in thriftTop\lib\cpp\msvc\libthrift there is a libthrift.sln solution file. You can also see that there are folders for the projects that are in that solution. One project is called BuildAll and another is called dummyLibthriftz.
>>
>> But if you open libthrift.sln, you can see that neither of those projects does anything. All BuildAll does is depend on the library projects. IIRC, dummyLibthriftz is just there so that the higher level solution file at thriftTop\msvc\masterSolution\masterSolution.sln has a target name to build when we can't build libthriftz.
>>
>> Here is something you can try. Go to thriftTop\msvc and delete the entire configGenerated subdirectory. Then run your configure again. After it completes, cd to the newly created configGenerated directory and run "nmake all >all.txt" to capture stdout to a file. If you get an error, please zip the all.txt file and email it to me off list. I'll take a look and see if I can figure anything out. In fact, if you get an error, please zip up the configGenerated directory and send it along with the build transcript.
>>
>> I hadn't thought of this before. Are you building with nmake, or are you opening the masterSolution and building by hand?
>>
>> - Rush
>>
>> P.S. As an aside that may or may not mean anything, I have now cleanly configured and built using the zlib binary distribution, but also without using zlib at all, with both the original configure.js and the new version. If you want to ditch your use of zlib we could try to figure out why that didn't work for you.
>>
>> On Jan 5, 2010, at 11:53 AM, Shane Gannon wrote:
>>
>>>
>>> Rush/Michael
>>> Thank you for the modified configure.js. When I used this new file it removed the fatal error LNK1104 error. I'm now left with
>>> Error 1 general error c1010070: Failed to load and parse the manifest. The system cannot find the file specified. .\Win32\DLL_Debug\dummyLibthriftz.exe.intermediate.manifest dummyLibthriftzError 2 general error c10100b1: Failed to load file "..\DLL_Debug\BuildAll.exe". The system cannot find the path specified. mt.exe BuildAll
>>> Rush since you are not getting these errors I'll assume that it is specify to my setup and investigate a little further.
>>> RegardsShane
>>>> From: rush@manbert.com
>>>> Subject: Re: ThriftMsvcPatch - Make the C++ runtime library be compatible with Windows and Visual Studio
>>>> Date: Tue, 5 Jan 2010 08:05:30 -0800
>>>> To: thrift-user@incubator.apache.org
>>>>
>>>> Sure. Here it is.
>>>>
>>>> - Rush
>>>>
>>>
>>> _________________________________________________________________
>>> New Windows 7: Find the right PC for you. Learn more.
>>> http://windows.microsoft.com/shop
>>
>
> _________________________________________________________________
> New Windows 7: Find the right PC for you. Learn more.
> http://windows.microsoft.com/shop
RE: ThriftMsvcPatch - Make the C++ runtime library be compatible
with Windows and Visual Studio
Posted by Shane Gannon <sg...@hotmail.com>.
Rush I'm primarily using Visual Studio and the solution at \lib\cpp\msvc\libthrift to build the project by hand. I have also tried the Master Solution and nmake but not since I got your new configure.js.
Tomorrow I'll exclude BuildAll and dummyLibthriftz from this solution and see if it removes those errors. I'll also delete the configGenerated directory and start over again with nmake. If I see any issues I'll email you with the zip.
Currently I have no preference for including or excluding zlib in the project at the moment. But I'd be glad to assist you in figuring out the original zlib problem if you wish. Just let me know what you'd like me to do. You say that you can build the project, with and without zlib, and not get that fatal LNK1104 error with the original configure.js? Do you know why this now works?
RegardsShane
> From: rush@manbert.com
> Subject: Re: ThriftMsvcPatch - Make the C++ runtime library be compatible with Windows and Visual Studio
> Date: Tue, 5 Jan 2010 12:47:25 -0800
> To: thrift-user@incubator.apache.org
>
> Hi Shane,
>
> There certainly seems to be something strange going on with your setup. I don't see these errors, but I do recognize the names.
>
> Down in thriftTop\lib\cpp\msvc\libthrift there is a libthrift.sln solution file. You can also see that there are folders for the projects that are in that solution. One project is called BuildAll and another is called dummyLibthriftz.
>
> But if you open libthrift.sln, you can see that neither of those projects does anything. All BuildAll does is depend on the library projects. IIRC, dummyLibthriftz is just there so that the higher level solution file at thriftTop\msvc\masterSolution\masterSolution.sln has a target name to build when we can't build libthriftz.
>
> Here is something you can try. Go to thriftTop\msvc and delete the entire configGenerated subdirectory. Then run your configure again. After it completes, cd to the newly created configGenerated directory and run "nmake all >all.txt" to capture stdout to a file. If you get an error, please zip the all.txt file and email it to me off list. I'll take a look and see if I can figure anything out. In fact, if you get an error, please zip up the configGenerated directory and send it along with the build transcript.
>
> I hadn't thought of this before. Are you building with nmake, or are you opening the masterSolution and building by hand?
>
> - Rush
>
> P.S. As an aside that may or may not mean anything, I have now cleanly configured and built using the zlib binary distribution, but also without using zlib at all, with both the original configure.js and the new version. If you want to ditch your use of zlib we could try to figure out why that didn't work for you.
>
> On Jan 5, 2010, at 11:53 AM, Shane Gannon wrote:
>
> >
> > Rush/Michael
> > Thank you for the modified configure.js. When I used this new file it removed the fatal error LNK1104 error. I'm now left with
> > Error 1 general error c1010070: Failed to load and parse the manifest. The system cannot find the file specified. .\Win32\DLL_Debug\dummyLibthriftz.exe.intermediate.manifest dummyLibthriftzError 2 general error c10100b1: Failed to load file "..\DLL_Debug\BuildAll.exe". The system cannot find the path specified. mt.exe BuildAll
> > Rush since you are not getting these errors I'll assume that it is specify to my setup and investigate a little further.
> > RegardsShane
> >> From: rush@manbert.com
> >> Subject: Re: ThriftMsvcPatch - Make the C++ runtime library be compatible with Windows and Visual Studio
> >> Date: Tue, 5 Jan 2010 08:05:30 -0800
> >> To: thrift-user@incubator.apache.org
> >>
> >> Sure. Here it is.
> >>
> >> - Rush
> >>
> >
> > _________________________________________________________________
> > New Windows 7: Find the right PC for you. Learn more.
> > http://windows.microsoft.com/shop
>
_________________________________________________________________
New Windows 7: Find the right PC for you. Learn more.
http://windows.microsoft.com/shop
Re: ThriftMsvcPatch - Make the C++ runtime library be compatible with Windows and Visual Studio
Posted by Rush Manbert <ru...@manbert.com>.
Hi Shane,
There certainly seems to be something strange going on with your setup. I don't see these errors, but I do recognize the names.
Down in thriftTop\lib\cpp\msvc\libthrift there is a libthrift.sln solution file. You can also see that there are folders for the projects that are in that solution. One project is called BuildAll and another is called dummyLibthriftz.
But if you open libthrift.sln, you can see that neither of those projects does anything. All BuildAll does is depend on the library projects. IIRC, dummyLibthriftz is just there so that the higher level solution file at thriftTop\msvc\masterSolution\masterSolution.sln has a target name to build when we can't build libthriftz.
Here is something you can try. Go to thriftTop\msvc and delete the entire configGenerated subdirectory. Then run your configure again. After it completes, cd to the newly created configGenerated directory and run "nmake all >all.txt" to capture stdout to a file. If you get an error, please zip the all.txt file and email it to me off list. I'll take a look and see if I can figure anything out. In fact, if you get an error, please zip up the configGenerated directory and send it along with the build transcript.
I hadn't thought of this before. Are you building with nmake, or are you opening the masterSolution and building by hand?
- Rush
P.S. As an aside that may or may not mean anything, I have now cleanly configured and built using the zlib binary distribution, but also without using zlib at all, with both the original configure.js and the new version. If you want to ditch your use of zlib we could try to figure out why that didn't work for you.
On Jan 5, 2010, at 11:53 AM, Shane Gannon wrote:
>
> Rush/Michael
> Thank you for the modified configure.js. When I used this new file it removed the fatal error LNK1104 error. I'm now left with
> Error 1 general error c1010070: Failed to load and parse the manifest. The system cannot find the file specified. .\Win32\DLL_Debug\dummyLibthriftz.exe.intermediate.manifest dummyLibthriftzError 2 general error c10100b1: Failed to load file "..\DLL_Debug\BuildAll.exe". The system cannot find the path specified. mt.exe BuildAll
> Rush since you are not getting these errors I'll assume that it is specify to my setup and investigate a little further.
> RegardsShane
>> From: rush@manbert.com
>> Subject: Re: ThriftMsvcPatch - Make the C++ runtime library be compatible with Windows and Visual Studio
>> Date: Tue, 5 Jan 2010 08:05:30 -0800
>> To: thrift-user@incubator.apache.org
>>
>> Sure. Here it is.
>>
>> - Rush
>>
>
> _________________________________________________________________
> New Windows 7: Find the right PC for you. Learn more.
> http://windows.microsoft.com/shop
RE: ThriftMsvcPatch - Make the C++ runtime library be compatible
with Windows and Visual Studio
Posted by Shane Gannon <sg...@hotmail.com>.
Rush/Michael
Thank you for the modified configure.js. When I used this new file it removed the fatal error LNK1104 error. I'm now left with
Error 1 general error c1010070: Failed to load and parse the manifest. The system cannot find the file specified. .\Win32\DLL_Debug\dummyLibthriftz.exe.intermediate.manifest dummyLibthriftzError 2 general error c10100b1: Failed to load file "..\DLL_Debug\BuildAll.exe". The system cannot find the path specified. mt.exe BuildAll
Rush since you are not getting these errors I'll assume that it is specify to my setup and investigate a little further.
RegardsShane
> From: rush@manbert.com
> Subject: Re: ThriftMsvcPatch - Make the C++ runtime library be compatible with Windows and Visual Studio
> Date: Tue, 5 Jan 2010 08:05:30 -0800
> To: thrift-user@incubator.apache.org
>
> Sure. Here it is.
>
> - Rush
>
_________________________________________________________________
New Windows 7: Find the right PC for you. Learn more.
http://windows.microsoft.com/shop
Re: ThriftMsvcPatch - Make the C++ runtime library be compatible with Windows and Visual Studio
Posted by Rush Manbert <ru...@manbert.com>.
Sure. Here it is.
- Rush
RE: ThriftMsvcPatch - Make the C++ runtime library be compatible
with Windows and Visual Studio
Posted by Shane Gannon <sg...@hotmail.com>.
Hi Rush
This is annoying. Hotmail has blocked configure.js and won't let me download it (see http://windowslivehelp.com/solutions/cantattach/archive/2008/08/21/error-quot-to-protect-your-security-and-the-security-of-others-you-can-t-attach-a-file-with-this-extension.aspx). Could you zip this file and send it again?
Shane
> From: rush@manbert.com
> Subject: Re: ThriftMsvcPatch - Make the C++ runtime library be compatible with Windows and Visual Studio
> Date: Mon, 4 Jan 2010 17:59:01 -0800
> To: thrift-user@incubator.apache.org
>
> Hi Shane,
>
> Here is a modified version of configure.js. Please use it in place of the one that you have now and it should let you build all the thrift libraries.
>
> - Rush
>
_________________________________________________________________
Windows 7: Find the right PC for you. Learn more.
http://windows.microsoft.com/shop
Re: ThriftMsvcPatch - Make the C++ runtime library be compatible with Windows and Visual Studio
Posted by Rush Manbert <ru...@manbert.com>.
Hi Shane,
Here is a modified version of configure.js. Please use it in place of the one that you have now and it should let you build all the thrift libraries.
- Rush
Re: ThriftMsvcPatch - Make the C++ runtime library be compatible with Windows and Visual Studio
Posted by Rush Manbert <ru...@manbert.com>.
Okay, I downloaded the patched sources, then configured like you did and ran "nmake all". I have gotten the same LNK1104 error that you got. I'm looking at why and I'll be back to you. This is something that isn't configured correctly, most likely because of a bug in the script, because the wacked out filename is leftover from before the configure was run, and it should have changed.
- Rush
On Jan 4, 2010, at 3:29 PM, Shane Gannon wrote:
>
> Hey Rush
> The errors I'm getting after doing a re-build on the Visual Studio Solution found in C:\thrift-818530-patched\lib\cpp\msvc\libthrift are:
> Error 334 fatal error LNK1104: cannot open file 'thrift-Win32-d.lib' libthriftnb libthriftnbError 335 general error c1010070: Failed to load and parse the manifest. The system cannot find the file specified. .\Win32\DLL_Debug\dummyLibthriftz.exe.intermediate.manifest dummyLibthriftzError 338 fatal error C1083: Cannot open include file: 'zlib.h': No such file or directory c:\thrift-818530-patched\lib\cpp\src\transport\tzlibtransport.cpp 24 libthriftzError 339 fatal error C1083: Cannot open source file: '.': Permission denied c1xx libthriftzError 340 general error c10100b1: Failed to load file "..\DLL_Debug\BuildAll.exe". The system cannot find the path specified. mt.exe BuildAll
> I also got the last four errors when I did a normal build.
> The command
> cscript configure.js --with-boost-inc=C:\boost\boost_1_36_0 --with-boost-lib=C:\boost\boost_1_36_0\lib --with-zlib=C:\zlib\ --link=shared --with-zlib-lib-name-pattern[win32][shared][debug]=zdll.lib --with-zlib-lib-name-pattern[win32][shared][release]=zdll.lib
> resulted in a successful build. Thank you for the solution. When I first received the configure.js error I was tempted to build zlib for source. But in the end I assumed it would make no difference. Since you say the patch was tested based on the zlib source I'll take this approach in the future.
> After I successfully ran the configure.js script I build libthrift from Visual Studio again. But I ended up with the same errors. Figuring that it could no longer be a configuration issue I went back to the zlib documentation. Sure enough there was a set of instructions for using zlib in Visual Studio that I had missed before. When I added the zlib include and lib directories to the additional dependencies most my errors disappeared. But two new ones appeared.
> I was left with
> Error 2 general error c1010070: Failed to load and parse the manifest. The system cannot find the file specified. .\Win32\DLL_Debug\dummyLibthriftz.exe.intermediate.manifest dummyLibthriftzError 4 fatal error LNK1104: cannot open file 'UnknownLibName-not-configured-for_Win32_DLL_Debug.obj' libthriftz libthriftzError 5 general error c10100b1: Failed to load file "..\DLL_Debug\BuildAll.exe". The system cannot find the path specified. mt.exe BuildAll
> which seem to be more Visual Studio hiccups? Or is something actually missing?
> PS: Should I need to add these zlib additional dependencies at all?
> RegardsShane
>> From: rush@manbert.com
>> Subject: Re: ThriftMsvcPatch - Make the C++ runtime library be compatible with Windows and Visual Studio
>> Date: Mon, 4 Jan 2010 11:21:59 -0800
>> To: thrift-user@incubator.apache.org
>>
>> More replies inline.
>>
>> On Jan 4, 2010, at 10:41 AM, Rush Manbert wrote:
>>
>>> Hi Shane,
>>>
>>> Replies inline.
>>>
>>> On Jan 2, 2010, at 1:26 PM, Shane Gannon wrote:
>>>
>>>>
>>>> Rush thanks for your reply. You have more than answered my questions.
>>>> I suppose my inquiry was a bit mislead. The C++ code generated by Thrift may be compilable on Windows - but it would need a reference to the Thrift C++ headers/libraries. Without this reference it will fail with errors like "error C2065: 'TProtocol' : undeclared identifier". After going over the documentation again I became worried that it was not compilable on Windows at all. Even with 591. You have happily removed this doubt.
>>>> About Cygwin you are correct. It is possible to use it to build the Thrift compiler. I have taken this approach and have been able to generated Java, C#, and C++ code from the .thrift files. But when I try to "make" the C++ library found in "thrift/lib/cpp" it gives me an error (error: `PTHREAD_MUTEX_RECURSIVE_NP' undeclared). So as far as I know, unless I'm making some simple mistake, you cannot build this library from Cygwin.
>>>> Like your tech support user I am also using Visual Studio 2008 and came across the need to carry out a conversion from 2005. For me this seems to have worked fine as well. But I'm still having a small issue building the msvc libraries. Its likely a mistake on my part but if you have any suggestions I would appreciate it. Initially when I ran configure.js I supplied the following arguments
>>>> cscript configure.js --with-boost-inc=C:\boost\boost_1_36_0 --with-boost-lib=C:\boost\boost_1_36_0\lib
>>>> but this produced errors when I built the project either in VS or with nmake. The errors stated that there were problems resolving zlib. I believe that you have documented this library as optional.
>>>
>>> I would be interested to see what errors you are getting when you configure without zlib. By default, zlib is not used. It only comes into play if you specify one of the --with-zlib parameters.
>>
>> I'm still interested in this. Maybe more so now. (See below)
>>
>>>
>>>> But I am unsure as to how I can exclude it. So I decided to download and use it. But when I supply
>>>> --with-zlib=C:\zlib\ or --with-zlib-inc=C:\zlib\include --with-zlib-lib=C:\zlib\lib
>>>> I end up with the following cscript output
>>>> C:>cscript configure.js --with-boost-inc=C:\boost\boost_1_36_0 --with-boost-lib=C:\boost\boost_1_36_0\lib --with-zlib=C:\zlib\Check for boost version >= 1.36.0 succeeded!
>>>> Found Boost libraries for the configuration tuple {win32, shared, debug} :boost_date_time-vc71-mt-gd-1_36.libboost_system-vc71-mt-gd-1_36.libboost_thread-vc71-mt-gd-1_36.lib
>>>> Found Boost libraries for the configuration tuple {win32, shared, release} :boost_date_time-vc71-mt-1_36.libboost_system-vc71-mt-1_36.libboost_thread-vc71-mt-1_36.lib
>>>> Found Boost libraries for the configuration tuple {win32, static, debug} :libboost_date_time-vc71-mt-gd-1_36.liblibboost_system-vc71-mt-gd-1_36.liblibboost_thread-vc71-mt-gd-1_36.lib
>>>> Found Boost libraries for the configuration tuple {win32, static, release} :libboost_date_time-vc71-mt-1_36.liblibboost_system-vc71-mt-1_36.liblibboost_thread-vc71-mt-1_36.lib
>>>> ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, shared, debug}
>>>> ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, shared, release}
>>>> ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, static, debug}
>>>> ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, static, release}
>>>>
>>>> Do you know what could be producing these errors? I think I've setup zlib correctly and am pointing at the right directory/directories. i.e. I download the binary version of zlib 1.2.3 and extracted it to C:\zlib\. Note: I also copied zlib1.dll to both System or System32 but this had no effect.
>>>
>>> When I did this, I downloaded the source code package for zlib and built the libraries myself, and the configure.js script is set up to look for the zlib libraries with the following names:
>>>
>>> (win32, shared, debug): zlib1d.lib
>>> (win32, shared, release): zlib1.lib
>>> (win32, static, debug): zlibd.lib
>>> (win32, static, release): zlib.lib
>>>
>>> I would guess that the libraries in the binary distribution have some other naming scheme. The configure script already has some fancy regex stuff to handle the variations in naming for the Boost libraries. I might need to add the equivalent for zlib.
>>>
>>> So the question to you is this: What files do you see in your c:\zlib\lib directory?
>>
>> Oh, this sucks. I downloaded the binary distribution zip file from the zlib site. It has only one version of the library, which I'm guessing is the (win32, shared, release) version.
>>
>> I think that can be made to work if you run the configure script with these arguments in addition to what you had already:
>> --link=shared
>> --with-zlib-lib-name-pattern[win32][shared][debug]=zdll.lib
>> --with-zlib-lib-name-pattern[win32][shared][release]=zdll.lib
>>
>> This will limit the build to DLL only, and will link both the debug and release builds against the release version of zlib. I expect that will work.
>>
>> At runtime you will need to have zlib.dll in a directory that is on your path.
>>
>> If you want to try this, also add --debug to the configure command line options. It spits out a ton of stuff, but shows what's going on.
>>
>> Alternatively, we can try to figure out why your non-zlib build didn't seem to work.
>>
>>>
>>>> PS: I'm glad to help you increase the successful trials count. The patch is a sensible addition to Thrift and should make it more accessible to the general audience.
>>>> Kind regardsShane
>>>
>>> Cool. I'll help you any way that I can.
>>>
>>> - Rush
>>>
>>
>
> _________________________________________________________________
> New Windows 7: Find the right PC for you. Learn more.
> http://windows.microsoft.com/shop
RE: ThriftMsvcPatch - Make the C++ runtime library be compatible
with Windows and Visual Studio
Posted by Shane Gannon <sg...@hotmail.com>.
Hey Rush
The errors I'm getting after doing a re-build on the Visual Studio Solution found in C:\thrift-818530-patched\lib\cpp\msvc\libthrift are:
Error 334 fatal error LNK1104: cannot open file 'thrift-Win32-d.lib' libthriftnb libthriftnbError 335 general error c1010070: Failed to load and parse the manifest. The system cannot find the file specified. .\Win32\DLL_Debug\dummyLibthriftz.exe.intermediate.manifest dummyLibthriftzError 338 fatal error C1083: Cannot open include file: 'zlib.h': No such file or directory c:\thrift-818530-patched\lib\cpp\src\transport\tzlibtransport.cpp 24 libthriftzError 339 fatal error C1083: Cannot open source file: '.': Permission denied c1xx libthriftzError 340 general error c10100b1: Failed to load file "..\DLL_Debug\BuildAll.exe". The system cannot find the path specified. mt.exe BuildAll
I also got the last four errors when I did a normal build.
The command
cscript configure.js --with-boost-inc=C:\boost\boost_1_36_0 --with-boost-lib=C:\boost\boost_1_36_0\lib --with-zlib=C:\zlib\ --link=shared --with-zlib-lib-name-pattern[win32][shared][debug]=zdll.lib --with-zlib-lib-name-pattern[win32][shared][release]=zdll.lib
resulted in a successful build. Thank you for the solution. When I first received the configure.js error I was tempted to build zlib for source. But in the end I assumed it would make no difference. Since you say the patch was tested based on the zlib source I'll take this approach in the future.
After I successfully ran the configure.js script I build libthrift from Visual Studio again. But I ended up with the same errors. Figuring that it could no longer be a configuration issue I went back to the zlib documentation. Sure enough there was a set of instructions for using zlib in Visual Studio that I had missed before. When I added the zlib include and lib directories to the additional dependencies most my errors disappeared. But two new ones appeared.
I was left with
Error 2 general error c1010070: Failed to load and parse the manifest. The system cannot find the file specified. .\Win32\DLL_Debug\dummyLibthriftz.exe.intermediate.manifest dummyLibthriftzError 4 fatal error LNK1104: cannot open file 'UnknownLibName-not-configured-for_Win32_DLL_Debug.obj' libthriftz libthriftzError 5 general error c10100b1: Failed to load file "..\DLL_Debug\BuildAll.exe". The system cannot find the path specified. mt.exe BuildAll
which seem to be more Visual Studio hiccups? Or is something actually missing?
PS: Should I need to add these zlib additional dependencies at all?
RegardsShane
> From: rush@manbert.com
> Subject: Re: ThriftMsvcPatch - Make the C++ runtime library be compatible with Windows and Visual Studio
> Date: Mon, 4 Jan 2010 11:21:59 -0800
> To: thrift-user@incubator.apache.org
>
> More replies inline.
>
> On Jan 4, 2010, at 10:41 AM, Rush Manbert wrote:
>
> > Hi Shane,
> >
> > Replies inline.
> >
> > On Jan 2, 2010, at 1:26 PM, Shane Gannon wrote:
> >
> >>
> >> Rush thanks for your reply. You have more than answered my questions.
> >> I suppose my inquiry was a bit mislead. The C++ code generated by Thrift may be compilable on Windows - but it would need a reference to the Thrift C++ headers/libraries. Without this reference it will fail with errors like "error C2065: 'TProtocol' : undeclared identifier". After going over the documentation again I became worried that it was not compilable on Windows at all. Even with 591. You have happily removed this doubt.
> >> About Cygwin you are correct. It is possible to use it to build the Thrift compiler. I have taken this approach and have been able to generated Java, C#, and C++ code from the .thrift files. But when I try to "make" the C++ library found in "thrift/lib/cpp" it gives me an error (error: `PTHREAD_MUTEX_RECURSIVE_NP' undeclared). So as far as I know, unless I'm making some simple mistake, you cannot build this library from Cygwin.
> >> Like your tech support user I am also using Visual Studio 2008 and came across the need to carry out a conversion from 2005. For me this seems to have worked fine as well. But I'm still having a small issue building the msvc libraries. Its likely a mistake on my part but if you have any suggestions I would appreciate it. Initially when I ran configure.js I supplied the following arguments
> >> cscript configure.js --with-boost-inc=C:\boost\boost_1_36_0 --with-boost-lib=C:\boost\boost_1_36_0\lib
> >> but this produced errors when I built the project either in VS or with nmake. The errors stated that there were problems resolving zlib. I believe that you have documented this library as optional.
> >
> > I would be interested to see what errors you are getting when you configure without zlib. By default, zlib is not used. It only comes into play if you specify one of the --with-zlib parameters.
>
> I'm still interested in this. Maybe more so now. (See below)
>
> >
> >> But I am unsure as to how I can exclude it. So I decided to download and use it. But when I supply
> >> --with-zlib=C:\zlib\ or --with-zlib-inc=C:\zlib\include --with-zlib-lib=C:\zlib\lib
> >> I end up with the following cscript output
> >> C:>cscript configure.js --with-boost-inc=C:\boost\boost_1_36_0 --with-boost-lib=C:\boost\boost_1_36_0\lib --with-zlib=C:\zlib\Check for boost version >= 1.36.0 succeeded!
> >> Found Boost libraries for the configuration tuple {win32, shared, debug} :boost_date_time-vc71-mt-gd-1_36.libboost_system-vc71-mt-gd-1_36.libboost_thread-vc71-mt-gd-1_36.lib
> >> Found Boost libraries for the configuration tuple {win32, shared, release} :boost_date_time-vc71-mt-1_36.libboost_system-vc71-mt-1_36.libboost_thread-vc71-mt-1_36.lib
> >> Found Boost libraries for the configuration tuple {win32, static, debug} :libboost_date_time-vc71-mt-gd-1_36.liblibboost_system-vc71-mt-gd-1_36.liblibboost_thread-vc71-mt-gd-1_36.lib
> >> Found Boost libraries for the configuration tuple {win32, static, release} :libboost_date_time-vc71-mt-1_36.liblibboost_system-vc71-mt-1_36.liblibboost_thread-vc71-mt-1_36.lib
> >> ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, shared, debug}
> >> ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, shared, release}
> >> ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, static, debug}
> >> ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, static, release}
> >>
> >> Do you know what could be producing these errors? I think I've setup zlib correctly and am pointing at the right directory/directories. i.e. I download the binary version of zlib 1.2.3 and extracted it to C:\zlib\. Note: I also copied zlib1.dll to both System or System32 but this had no effect.
> >
> > When I did this, I downloaded the source code package for zlib and built the libraries myself, and the configure.js script is set up to look for the zlib libraries with the following names:
> >
> > (win32, shared, debug): zlib1d.lib
> > (win32, shared, release): zlib1.lib
> > (win32, static, debug): zlibd.lib
> > (win32, static, release): zlib.lib
> >
> > I would guess that the libraries in the binary distribution have some other naming scheme. The configure script already has some fancy regex stuff to handle the variations in naming for the Boost libraries. I might need to add the equivalent for zlib.
> >
> > So the question to you is this: What files do you see in your c:\zlib\lib directory?
>
> Oh, this sucks. I downloaded the binary distribution zip file from the zlib site. It has only one version of the library, which I'm guessing is the (win32, shared, release) version.
>
> I think that can be made to work if you run the configure script with these arguments in addition to what you had already:
> --link=shared
> --with-zlib-lib-name-pattern[win32][shared][debug]=zdll.lib
> --with-zlib-lib-name-pattern[win32][shared][release]=zdll.lib
>
> This will limit the build to DLL only, and will link both the debug and release builds against the release version of zlib. I expect that will work.
>
> At runtime you will need to have zlib.dll in a directory that is on your path.
>
> If you want to try this, also add --debug to the configure command line options. It spits out a ton of stuff, but shows what's going on.
>
> Alternatively, we can try to figure out why your non-zlib build didn't seem to work.
>
> >
> >> PS: I'm glad to help you increase the successful trials count. The patch is a sensible addition to Thrift and should make it more accessible to the general audience.
> >> Kind regardsShane
> >
> > Cool. I'll help you any way that I can.
> >
> > - Rush
> >
>
_________________________________________________________________
New Windows 7: Find the right PC for you. Learn more.
http://windows.microsoft.com/shop
Re: ThriftMsvcPatch - Make the C++ runtime library be compatible with Windows and Visual Studio
Posted by Rush Manbert <ru...@manbert.com>.
More replies inline.
On Jan 4, 2010, at 10:41 AM, Rush Manbert wrote:
> Hi Shane,
>
> Replies inline.
>
> On Jan 2, 2010, at 1:26 PM, Shane Gannon wrote:
>
>>
>> Rush thanks for your reply. You have more than answered my questions.
>> I suppose my inquiry was a bit mislead. The C++ code generated by Thrift may be compilable on Windows - but it would need a reference to the Thrift C++ headers/libraries. Without this reference it will fail with errors like "error C2065: 'TProtocol' : undeclared identifier". After going over the documentation again I became worried that it was not compilable on Windows at all. Even with 591. You have happily removed this doubt.
>> About Cygwin you are correct. It is possible to use it to build the Thrift compiler. I have taken this approach and have been able to generated Java, C#, and C++ code from the .thrift files. But when I try to "make" the C++ library found in "thrift/lib/cpp" it gives me an error (error: `PTHREAD_MUTEX_RECURSIVE_NP' undeclared). So as far as I know, unless I'm making some simple mistake, you cannot build this library from Cygwin.
>> Like your tech support user I am also using Visual Studio 2008 and came across the need to carry out a conversion from 2005. For me this seems to have worked fine as well. But I'm still having a small issue building the msvc libraries. Its likely a mistake on my part but if you have any suggestions I would appreciate it. Initially when I ran configure.js I supplied the following arguments
>> cscript configure.js --with-boost-inc=C:\boost\boost_1_36_0 --with-boost-lib=C:\boost\boost_1_36_0\lib
>> but this produced errors when I built the project either in VS or with nmake. The errors stated that there were problems resolving zlib. I believe that you have documented this library as optional.
>
> I would be interested to see what errors you are getting when you configure without zlib. By default, zlib is not used. It only comes into play if you specify one of the --with-zlib parameters.
I'm still interested in this. Maybe more so now. (See below)
>
>> But I am unsure as to how I can exclude it. So I decided to download and use it. But when I supply
>> --with-zlib=C:\zlib\ or --with-zlib-inc=C:\zlib\include --with-zlib-lib=C:\zlib\lib
>> I end up with the following cscript output
>> C:>cscript configure.js --with-boost-inc=C:\boost\boost_1_36_0 --with-boost-lib=C:\boost\boost_1_36_0\lib --with-zlib=C:\zlib\Check for boost version >= 1.36.0 succeeded!
>> Found Boost libraries for the configuration tuple {win32, shared, debug} :boost_date_time-vc71-mt-gd-1_36.libboost_system-vc71-mt-gd-1_36.libboost_thread-vc71-mt-gd-1_36.lib
>> Found Boost libraries for the configuration tuple {win32, shared, release} :boost_date_time-vc71-mt-1_36.libboost_system-vc71-mt-1_36.libboost_thread-vc71-mt-1_36.lib
>> Found Boost libraries for the configuration tuple {win32, static, debug} :libboost_date_time-vc71-mt-gd-1_36.liblibboost_system-vc71-mt-gd-1_36.liblibboost_thread-vc71-mt-gd-1_36.lib
>> Found Boost libraries for the configuration tuple {win32, static, release} :libboost_date_time-vc71-mt-1_36.liblibboost_system-vc71-mt-1_36.liblibboost_thread-vc71-mt-1_36.lib
>> ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, shared, debug}
>> ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, shared, release}
>> ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, static, debug}
>> ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, static, release}
>>
>> Do you know what could be producing these errors? I think I've setup zlib correctly and am pointing at the right directory/directories. i.e. I download the binary version of zlib 1.2.3 and extracted it to C:\zlib\. Note: I also copied zlib1.dll to both System or System32 but this had no effect.
>
> When I did this, I downloaded the source code package for zlib and built the libraries myself, and the configure.js script is set up to look for the zlib libraries with the following names:
>
> (win32, shared, debug): zlib1d.lib
> (win32, shared, release): zlib1.lib
> (win32, static, debug): zlibd.lib
> (win32, static, release): zlib.lib
>
> I would guess that the libraries in the binary distribution have some other naming scheme. The configure script already has some fancy regex stuff to handle the variations in naming for the Boost libraries. I might need to add the equivalent for zlib.
>
> So the question to you is this: What files do you see in your c:\zlib\lib directory?
Oh, this sucks. I downloaded the binary distribution zip file from the zlib site. It has only one version of the library, which I'm guessing is the (win32, shared, release) version.
I think that can be made to work if you run the configure script with these arguments in addition to what you had already:
--link=shared
--with-zlib-lib-name-pattern[win32][shared][debug]=zdll.lib
--with-zlib-lib-name-pattern[win32][shared][release]=zdll.lib
This will limit the build to DLL only, and will link both the debug and release builds against the release version of zlib. I expect that will work.
At runtime you will need to have zlib.dll in a directory that is on your path.
If you want to try this, also add --debug to the configure command line options. It spits out a ton of stuff, but shows what's going on.
Alternatively, we can try to figure out why your non-zlib build didn't seem to work.
>
>> PS: I'm glad to help you increase the successful trials count. The patch is a sensible addition to Thrift and should make it more accessible to the general audience.
>> Kind regardsShane
>
> Cool. I'll help you any way that I can.
>
> - Rush
>
Re: ThriftMsvcPatch - Make the C++ runtime library be compatible with Windows and Visual Studio
Posted by Rush Manbert <ru...@manbert.com>.
Hi Shane,
Replies inline.
On Jan 2, 2010, at 1:26 PM, Shane Gannon wrote:
>
> Rush thanks for your reply. You have more than answered my questions.
> I suppose my inquiry was a bit mislead. The C++ code generated by Thrift may be compilable on Windows - but it would need a reference to the Thrift C++ headers/libraries. Without this reference it will fail with errors like "error C2065: 'TProtocol' : undeclared identifier". After going over the documentation again I became worried that it was not compilable on Windows at all. Even with 591. You have happily removed this doubt.
> About Cygwin you are correct. It is possible to use it to build the Thrift compiler. I have taken this approach and have been able to generated Java, C#, and C++ code from the .thrift files. But when I try to "make" the C++ library found in "thrift/lib/cpp" it gives me an error (error: `PTHREAD_MUTEX_RECURSIVE_NP' undeclared). So as far as I know, unless I'm making some simple mistake, you cannot build this library from Cygwin.
> Like your tech support user I am also using Visual Studio 2008 and came across the need to carry out a conversion from 2005. For me this seems to have worked fine as well. But I'm still having a small issue building the msvc libraries. Its likely a mistake on my part but if you have any suggestions I would appreciate it. Initially when I ran configure.js I supplied the following arguments
> cscript configure.js --with-boost-inc=C:\boost\boost_1_36_0 --with-boost-lib=C:\boost\boost_1_36_0\lib
> but this produced errors when I built the project either in VS or with nmake. The errors stated that there were problems resolving zlib. I believe that you have documented this library as optional.
I would be interested to see what errors you are getting when you configure without zlib. By default, zlib is not used. It only comes into play if you specify one of the --with-zlib parameters.
> But I am unsure as to how I can exclude it. So I decided to download and use it. But when I supply
> --with-zlib=C:\zlib\ or --with-zlib-inc=C:\zlib\include --with-zlib-lib=C:\zlib\lib
> I end up with the following cscript output
> C:>cscript configure.js --with-boost-inc=C:\boost\boost_1_36_0 --with-boost-lib=C:\boost\boost_1_36_0\lib --with-zlib=C:\zlib\Check for boost version >= 1.36.0 succeeded!
> Found Boost libraries for the configuration tuple {win32, shared, debug} :boost_date_time-vc71-mt-gd-1_36.libboost_system-vc71-mt-gd-1_36.libboost_thread-vc71-mt-gd-1_36.lib
> Found Boost libraries for the configuration tuple {win32, shared, release} :boost_date_time-vc71-mt-1_36.libboost_system-vc71-mt-1_36.libboost_thread-vc71-mt-1_36.lib
> Found Boost libraries for the configuration tuple {win32, static, debug} :libboost_date_time-vc71-mt-gd-1_36.liblibboost_system-vc71-mt-gd-1_36.liblibboost_thread-vc71-mt-gd-1_36.lib
> Found Boost libraries for the configuration tuple {win32, static, release} :libboost_date_time-vc71-mt-1_36.liblibboost_system-vc71-mt-1_36.liblibboost_thread-vc71-mt-1_36.lib
> ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, shared, debug}
> ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, shared, release}
> ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, static, debug}
> ERROR: Could not find any required Zlib libraries for the configuration tuple {win32, static, release}
>
> Do you know what could be producing these errors? I think I've setup zlib correctly and am pointing at the right directory/directories. i.e. I download the binary version of zlib 1.2.3 and extracted it to C:\zlib\. Note: I also copied zlib1.dll to both System or System32 but this had no effect.
When I did this, I downloaded the source code package for zlib and built the libraries myself, and the configure.js script is set up to look for the zlib libraries with the following names:
(win32, shared, debug): zlib1d.lib
(win32, shared, release): zlib1.lib
(win32, static, debug): zlibd.lib
(win32, static, release): zlib.lib
I would guess that the libraries in the binary distribution have some other naming scheme. The configure script already has some fancy regex stuff to handle the variations in naming for the Boost libraries. I might need to add the equivalent for zlib.
So the question to you is this: What files do you see in your c:\zlib\lib directory?
> PS: I'm glad to help you increase the successful trials count. The patch is a sensible addition to Thrift and should make it more accessible to the general audience.
> Kind regardsShane
Cool. I'll help you any way that I can.
- Rush