easiest way for C++ on Windows is probably https://issues.apache.org/jira/browse/THRIFT-757 with cygwin

https://issues.apache.org/jira/browse/THRIFT-591 needs some more work ....

Am 13.11.2010 00:48, schrieb Dheeraj Goswami:
Hi Roger,
Can you please guide me here, I am kind of stuck. Can you give some idea what is our best way to move forward for Windows?

Thanks a lot for your guidance. Please help!!

thanks,
--dheeraj

--- On *Fri, 11/12/10, Dheeraj Goswami /<[email protected]>/* wrote:


    From: Dheeraj Goswami <[email protected]>
    Subject: RE: Question about future of thrift on Windows
    To: [email protected]
    Date: Friday, November 12, 2010, 8:02 AM

    Hi roger,

    The issue is that we have our base code that uses thrift api is in
    c++, that is how it works on mac-osx.   That is the reason we
    generate the code in cpp. Is there a way to deal with this issue
    and can csharp be still used?



    Thanks

    dheeraj



    -----Original Message-----

    From: <[email protected]
    </mc/[email protected]>>

    Sent: Friday, November 12, 2010 12:29 AM

    To: [email protected] </mc/[email protected]>

    Subject: Re: Question about future of thrift on Windows



    Today we have a thrift-compiler and csharp library for windows.

    Why do you not use the c# library?



    -Roger



    Quoting Dheeraj Goswami <[email protected]
    </mc/[email protected]>>:



    > Hello All,We are using thrift 0.5.0 and we need to use on Mac OSX

    > and Windows platform. So far we have been managing from the patch

    > given by Rush Manbert (thanks to Rush) for older version of thrift.

    > Now there are no patches available for 0.5.0

    > Can somebody please given me what is the plan and long term
    strategy

    > for using thrift onWindows? Any better solutions, documents,

    > guidelines?

    >

    > thanks,

    >

    > --dheeraj







    ----------------------------------------------------------------

    This message was sent using IMP, the Internet Messaging Program.



Reply via email to