[ 
https://issues.apache.org/jira/browse/THRIFT-3013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15832913#comment-15832913
 ] 

Jens Geyer edited comment on THRIFT-3013 at 1/21/17 10:07 AM:
--------------------------------------------------------------

{quote}
Also FWIW I actually appreciate how simple it is to build the compiler... for 
the most part I use Thrift with [other languages], and never with C++ so it is 
really nice to be able to build with [...]
{quote}

... the existing Thrift Compiler Visual Studio Project file. We're not 
interested in the C++ libs here either, because we do not use them, so that 
simply doesn't matter to us. 

But the Thrift Compiler does. Right now I only need WinFlexBison in addition to 
Visual Studio, plus I have to copy & rename one single header file by hand to 
build it. When removing the compiler VCPROJ and add boost dependencies, we will 
need to a) install cmake and b) install boost. In essence, that would be a step 
backwards for those people who do not develop software with C++. If that is 
what the community says is the way to go, well, so be it. But as outlined 
elsewhere, I'm personally not that much excited about adding more complexity to 
my workflow.


was (Author: jensg):
{quote}
Also FWIW I actually appreciate how simple it is to build the compiler... for 
the most part I use Thrift with Java, JS, and PHP, and never with C++ so it is 
really nice to be able to build with [...]
{quote}

... the existing Thrift Compiler Visual Studio Project file. We're not 
interested in the C++ libs here, because we do not use them, so that simply 
doesn't matter to us. 

But the Thrift Compiler does. Right now I only need WinFlexBison in addition to 
Visual Studio, plus I have to copy & rename one single header file by hand to 
build it. When removing the compiler VCPROJ and add boost dependencies, we will 
need to a) install cmake and b) install boost. In essence, that would be a step 
backwards for those people who do not develop software with C++. If that is 
what the community says is the way to go, well, so be it. But as outlined 
elsewhere, I'm personally not that much excited about adding more complexity to 
my workflow.

> make thrift compiler accept a list of input files
> -------------------------------------------------
>
>                 Key: THRIFT-3013
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3013
>             Project: Thrift
>          Issue Type: New Feature
>          Components: Compiler (General)
>    Affects Versions: 0.9.2
>            Reporter: Xiaoshuang LU
>            Assignee: Roger Meier
>         Attachments: THRIFT-3013.v4.patch
>
>
> At present, customers could only specify one input file to thrift compiler.  
> There are maybe two approaches to support multiple input files.
> Approach 1: Improve the option parser in compiler/cpp/src/main.cc.  Maybe we 
> can borrow code from GUN's getopt_long.
> Approach 2: Offer users a maven plugin which can help them to iterate through 
> a list of input files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to