Hi Chris -- to follow up to your question also, we intend for contributors to build from source using the CMake configuration directly. We have found that conda is the easiest and most reliable way to manage the dependencies for C++ and Python contributors across all platforms. If you follow the Python contribution guide and something doesn't work please let us know so we can work with you to fix.
Wes On Sat, Aug 31, 2019, 9:18 AM Uwe L. Korn <uw...@xhochy.com> wrote: > Hello Chris, > > as a contributor, it is often simpler to use conda to construct a local > development environment as outlined in > https://arrow.apache.org/docs/developers/python.html#using-conda > This is the typical environment most contributors work in. Even when not > using conda as a package/environment manager elsewhere, I would recommend > to use it to setup your Arrow build environment as this is the way most > developers do. Thus it will be easier to help you and this is the setup we > (try to) maintain best. > > Cheers > Uwe > > On Sat, Aug 31, 2019, at 3:48 PM, Chris Teoh wrote: > > Does this approach fit with potentially a contributor's workflow? I was > > looking into contributing though I'm unsure if I am doing it right. > > > > On Sat, 31 Aug 2019 at 22:22, Jeroen Ooms <jeroeno...@gmail.com> wrote: > > > > > On Sat, Aug 31, 2019 at 4:48 AM Chris Teoh <chris.t...@gmail.com> > wrote: > > > > > > > > That being said, is there an easier way by using a Docker container I > > > could > > > > use to build this in? > > > > > > An easy way to install arrow on MacOS is using homebrew. To get a > > > precompiled version of the latest release: > > > > > > brew install apache-arrow > > > > > > Or to build the master branch from source: > > > > > > brew install apache-arrow --HEAD > > > > > > If you want to customize the configuration use "brew edit > > > apache-arrow" before building from source. > > > > > > > > > -- > > Chris > > >
