Okay. I'll try to bring that branch back to life in the next few days. It was integrated with a lot of other changes to simplify the build.
Don't forget: autoconf isn't required to build from a release tarball. --David On 08/26/2010 04:17 PM, Todd Lipcon wrote: > On Thu, Aug 26, 2010 at 4:12 PM, David Reiss <[email protected] > <mailto:[email protected]>> wrote: > > Roger, you misunderstood that patch. It just lets you run configure > and make > to build the code generator and java/python/etc. libraries without > having to > build the C++ runtime library. > > Also, I think I have a patch lying around to make the code generator > not rely > on boost. > > > Not relying on boost would be a great start! That's probably the biggest > obstacle - autoconf, etc, is annoying but boost is just the worst. > > -Todd > > > On 08/26/2010 04:03 PM, Todd Lipcon wrote: > > On Thu, Aug 26, 2010 at 3:58 PM, Roger Meier > <[email protected] <mailto:[email protected]>>wrote: > > > >> Yes, that's an important issue! > >> > >> what do you think about a compiler that only needs C as described in > >> https://issues.apache.org/jira/browse/THRIFT-506 > >> > >> compile that one for different platforms and make it available > for each > >> version on the download web site? > >> > >> That gets rid of the boost dependency, but we're still forced to > push out > > built binaries for a bunch of platforms, which is kind of a pain > compared to > > Java. > > > > However, porting over all our existing generators will take some > time, for > > sure. > > > > -Todd > > > >> > >> Am 26.08.2010 23:56, schrieb Todd Lipcon: > >> > >> On Thu, Aug 26, 2010 at 1:54 PM, Bjorn Borud<[email protected] > <mailto:[email protected]>> wrote: > >>> > >>> > >>> > >>>> on the project I currently work on we have a (ANTLR-based) > parser for > >>>> the Thrift IDL language in order to generate code for a proprietary > >>>> serialization library. > >>>> > >>>> it struck me that perhaps we could use this parser the > implement the > >>>> Thrift compiler in Java instead. this would mean that the thrift > >>>> compiler itself could be built as a platform independent > artifact -- > >>>> which should make it a lot more elegant to write Maven plugins for > >>>> Thrift. it would also eliminate the need (for us) to maintain > Thrift > >>>> compiler binaries for all platforms and versions of the compiler. > >>>> > >>>> currently the parser lacks some minor features, but this could > easily be > >>>> rectified. the real job is to add the code generation for various > >>>> languages. > >>>> > >>>> if anyone is interested in this, I am going to talk to some people > >>>> tomorrow to get formal approval for open sourcing it. > >>>> > >>>> > >>>> > >>>> > >>> I'm interested - in my experience, the C++ compiler has been one > of the > >>> major barriers of Thrift adoption, since it's often a pain to > get running > >>> on > >>> OSX, Windows, etc. A java code generator would be so much easier > to get up > >>> and going, easier to add "plugin" support, and easier for a larger > >>> community > >>> of developers to contribute to. > >>> > >>> -Todd > >>> > >>> > >> > >> > > > > > > > > > -- > Todd Lipcon > Software Engineer, Cloudera
