Hi Chris,
Thrift mainly consists of two parts: the compiler-generated code and the
library for each language. Depending on the language that library either
consist a bunch of source files that you have to add to your project, or
there is some library module that can be built by means of the make step, if
it isn't already installed onto the machine in question.
To dive into Thrift, I recommend the tutorial (see website). Also what's
under the /test folder in the repository is worth a look and explains a lot
of basic stuff just by studying it.
Have fun,
JensG
Disclaimer: I personally don't use the C++ stuff that much, so please take
that part with a grain of salt.
-----Ursprüngliche Nachricht-----
From: Chris Seto
Sent: Tuesday, June 23, 2015 8:04 PM
To: [email protected]
Subject: Advice for a possibly unique Thrift build environment?
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
--
