assignUser commented on issue #43546:
URL: https://github.com/apache/arrow/issues/43546#issuecomment-2266298449
> but the issue is: R packages are meant to follow the R configuration when
compiling
It does, for the R package part. Using R makevars for the libarrow build
would just cause issues.
> Yes, I guess one can set standard env. vars for the build system if needed
As you said yourself you can influence the flags for the bundled build. The
bundled build and pre-compiled binaries are a convenience feature only, we
could also just add libarrow as a system dependency (e.g. like GDAL for
geospatial packages). We have spent a lot of time and effort to make it easy
to install the package, even for users without experience with compiling
complex C++ projects.
If you want to compile libarrow in a special way to suit your needs you can
either use the env. vars or you can build it locally and build the R package
against that version with no problem, the easiest way to do this is to have
libarrow in your pkg-config path. See also
https://arrow.apache.org/docs/r/articles/developers/install_details.html#finding-libarrow-on-the-system
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
