输出所选按钮值或名称(Output selected button value or name)

 对此有几个部分答案。 
 
 
 
 Windows构建是通过Linux机器上的MinGW交叉编译器完成的。 
 
 
 由于（至少）0.9.2，不再需要使用MinGW在Windows机器上构建Thrift编译器。 1）除了事实，你根本不需要这样做，因为下载页面上有预编译的EXE，有一个很好的Visual Studio项目来构建Windows Thrift编译器EXE。 该项目只有两个依赖项：Bison和Lexx / Yacc，它们也可以在其他地方作为预编译设置使用。 
 
 
 在任何一种情况下，MinGW仅用于构建编译器。 如果你想用MinGW构建库，我不确定它是否有效。 这种做事方式没有得到实施或支持，仅仅因为没有人需要它。 
 
 
 这让我们回到了这个问题，为什么你认为你“需要”这种方式。 
 
 
 1） 据我所知，autotools存在许多严重的问题，以及在Windows机器上在MinGW下构建Thrift所需的所有东西。 您将需要修补内容，从源代码构建一些内容，花费大量时间并使用文件系统执行一些奇怪的操作以使其正常工作。 至少在两年前我停止使用MinGW来制造Thrift的情况就是如此。 即使你让它工作，你仍然只能得到编译器（你可以在很短的时间内轻松下载），而不是库。 

There are several partial answers to this.
 
 
 
The Windows build is made by means of MinGW cross compiler on a Linux machine. 
 
 
Since (at least) 0.9.2 it is no longer necessary to use MinGW to build the Thrift compiler on a Windows machine.1) Aside from the fact, that you don't need to do that at all, because a precompiled EXE is available on the download pages, there is a nice Visual Studio project to build the Windows Thrift compiler EXE. The project has only two dependencies: Bison and Lexx/Yacc, which are both available elsewhere as precompiled Setups as well. 
 
 
In either case MinGW is only used to build the compiler. If you want to build the libraries with MinGW, I'm not sure if that even works. This way of doing things is not implemented or supported, simply because nobody needs it.
 
 
Which brings us back to the question, why you think you "need" it this way.
 
 
1)To my knowledge, numerous severe problems exist with the autotools and all the stuff needed to build Thrift under MinGW on a Windows machine. You will have to patch things, build some from source, spend a lot of time and do some strange things with your file system to make it work. At least that was the case when I stopped using MinGW to build Thrift about two years ago. And even if you get it to work, you still only get the compiler (which you could easily download in a fraction of that time), not the libraries.