I haven't tracked it down yet.

I received an off-line reply from James King suggesting that I might be
missing a "make install," which binds the output generators together.  I am
doing a "make install" in compiler/cpp.  Looking at where (I think) the
generators live, that seems like it should be sufficient, but still no joy.

I do see t_py_generator.cc getting compiled and linked into the executable,
and it does create the gen-py directory and __init__.py file, so something's
there.  My next step is to make some time to dive in and start debugging to
figure out what piece I'm missing, and then figure out how to get the build
step to put it in the right place.  (My configuration is complicated by the
fact that I'm trying to generate all of this for checkin as a hermetic
build, so I can't install things in a MinGW system directory like
C:\msys\1.0.)

I'll try to report back once I get things working, in case it's useful for
others.  This is my first exposure to Thrift, and I'm liking what I see in
general, but the situation on Windows (including lack of C++ runtime) is a
disappointment.  I'd really love to see something like Rush Manbert's patch
made a supported part of the package:

https://issues.apache.org/jira/browse/THRIFT-591

Thanks,

        --SK


On Tue, Apr 13, 2010 at 8:48 AM, Jonathan Ellis <[email protected]> wrote:

> Did you ever figure out what was going on here?
>
> I have heard of people building thrift successfully using mingw, but I
> have not done it myself.
>
> On Fri, Apr 9, 2010 at 12:26 PM, Steven Knight <[email protected]> wrote:
> > Has anyone else seen this behavior?  I've built the thrift compiler on
> > Windows according to the instructions on the wiki (using MinGW, not
> cygwin):
> >
> > http://wiki.apache.org/thrift/ThriftInstallationWin32
> >
> > The same .thrift file that generates a full tree of Python modules in
> gen-py
> > on Mac and Linux generates a __init__.py and nothing else when I run it
> on
> > Windows.
> >
> > Before I dive into the guts trying to debug this, are there known
> pitfalls
> > here, or something obvious I may be overlooking?
> >
> > Thanks,
> >
> >        --SK
> >
>

Reply via email to