I'd suspect you'd have a hard time building it for other platforms, but once you got it to build, it'd work. It only uses the standard library and parquet-cpp.

I'd suspect you'd have a hard time building it for other platforms, but once you got it to build, it'd work. It only uses the standard library and parquet-cpp. From what I can tell, parquet-cpp has a documented build experience for both Windows and OS X. I may be overstating the difficulty of building it for Linux. I hadn't written C++ code in ages prior to starting this, so I'm sure I was tripping over things that others would sail past. I was also simultaneously trying to build a version of pyarrow that supported some bleeding edge features. However, I _definitely_ had an incorrect mental model of where the libraries were getting installed, which led to some wasted time and frustration. With time and some emotional distance, I'd like to take a stab at cleaning up the Linux build so that it can hook into travis-ci and codecov. I think once that happened, getting the OS X build to work shouldn't be too difficult. I don't have an OS X machine, though, so I'm not in a great position to test that. As for Windows... if I know very little about building C++ code the right way in Linux, I know nothing for Windows :( I do have a Windows machine, so I'm sure with enough goading I could be convinced to take a look at it. Feel free to open issues for an OS X and/or Windows build, although I can't guarantee a timely resolution to either of them!