thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Seto <>
Subject Re: Advice for a possibly unique Thrift build environment?
Date Tue, 23 Jun 2015 20:15:42 GMT
Hi Randy,

Thanks, this is exactly the information I needed. For clarification, it 
looks like I obviously need the directory: 
thrift-0.9.2\lib\cpp\src\thrift , though is there anything else that 
might be more obscure?

The second question I have is in regards to the config.h file. This file 
is included by thrift-0.9.2\lib\cpp\src\thrift\thrift-config.h, and it 
is not normally present in the source tree. It looks like it's probably 
a product of ./configure. What's the best way to get this file? Should I 
simply ./configure on my Linux target, then copy the file over and edit, 
or is there a better way?

Otherwise, the process seems fairly typical. The config file was the big 
catch when I tried to include boiler plate files off the bat.

Also, thanks Jens as well. I looked through the tutorials quite a bit, 
but the issue was that they don't talk a lot about including the Thrift 
library files into your project, only about using the IDL format.

Chris Seto
On 6/23/2015 12:51 PM, Randy Abernethy wrote:
> Hi Chris,
> I often build Thrift C++ apps on Windows without precompiled libs. The
> first time I did it I just added the obvious cpp files from the thrift cpp
> lib to my project, built, read through the linker errors, grepped around,
> added some more cpp files, and so on. It is pretty easy to pull together
> the necessary cpp source for a client, a bit more work for a server but
> certainly doable. You learn a lot in the process too. Once you have the
> boilerplate list of files you generally depend on it is pretty routine.
> Makes debugging easy too, no need to configure debug and release libs,
> never any problems with the IDE figuring out where the source is when you
> want to step into code, etc. I also found building some dependencies on
> windows rough, in particular libevent. It was much easier to just compile
> the bits of lib event I needed without trying to make the entire thing
> work.
> At the end of the day I use static libs most of the time but just want to
> let you know that compiling the Thrift sources into your executable
> directly is no big hardship on any platform.
> Best,
> Randy
> On Tue, Jun 23, 2015 at 11:04 AM, Chris Seto <> wrote:
>> Hi all,
>> I am a beginner to the Thrift framework, and I'm looking into using Thrift
>> on a project which is half embedded (actually C++ on embedded Linux) and
>> half C#. Obviously the C# side is standard affair, so I'm not worried about
>> it at all.
>> On the embedded side, I am running a little embedded Linux computer
>> running Angstrom Linux. While I can build either natively or on a desktop
>> Linux target, I actually have been cross compiling my application on my
>> Windows machine With the GCC-Linaro toolchain.
>> Obviously, I can run the thrift compiler on my Windows machine, so
>> generating the subs isn't a big deal.
>> I'm more wondering how to include the Thrift libraries in the project. I
>> do have an Ubuntu Linux machine which has Thrift "installed", but what
>> exactly is the Thrift installation doing, and what is the best way to
>> include Thrift into my existing C++ project? Is there a clean way that I
>> could compile Thrift libs on my Ubuntu machine, then link against them on
>> my Windows build environment? Similarly, would it be possible for me to
>> simply include the libs as source files in my existing C++ project?
>> Thanks
>> --

View raw message