[
https://issues.apache.org/jira/browse/ARROW-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes McKinney resolved ARROW-3758.
---------------------------------
Resolution: Fixed
Issue resolved by pull request 4622
[https://github.com/apache/arrow/pull/4622]
> [R] Build R library on Windows, document build instructions for Windows
> developers
> ----------------------------------------------------------------------------------
>
> Key: ARROW-3758
> URL: https://issues.apache.org/jira/browse/ARROW-3758
> Project: Apache Arrow
> Issue Type: Improvement
> Components: R
> Reporter: Wes McKinney
> Assignee: Neal Richardson
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.14.0
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> The status quo for building the R package with the C++ library is a bit
> special (see procedure
> [here|https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-UpdatingCRANpackages])
> and requires that compilation happen with a specific toolchain for R. There
> is no guidance on how to get a successful build locally on Windows, and it's
> not covered by our CI so we are vulnerable to regression.
> Goal for this ticket: recreate the environment from
> [https://github.com/r-windows/rtools-backports] in our Appveyor so that we
> can build and test R with C++ in continuous integration. Side effect of
> bringing the {{PKGBUILD}} configuration that the r-windows setup uses into
> our source control for easier release management. This should also get us
> closer to, perhaps arriving at, reproducible build steps for local Windows
> developers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
