You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Neal Richardson (JIRA)" <ji...@apache.org> on 2019/06/18 22:44:00 UTC
[jira] [Commented] (ARROW-3758) [R] Build R library on Windows,
document build instructions for Windows developers
[ https://issues.apache.org/jira/browse/ARROW-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16867106#comment-16867106 ]
Neal Richardson commented on ARROW-3758:
----------------------------------------
Work in progress here: [https://github.com/apache/arrow/compare/master...nealrichardson:r-appveyor-part2]
I got the rtools appveyor environment reproduced and successfully built the 0.13 released C++ library: [https://ci.appveyor.com/project/nealrichardson/arrow/builds/25372598]. Still working on linking that with the R package in the next step.
Unfortunately, building current master branch of the C++ library fails: [https://ci.appveyor.com/project/nealrichardson/arrow/builds/25367079#L1177]
It's looking for {{codecvt}} and can't find it. I will ticket that separately.
> [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
> Fix For: 0.14.0
>
>
> 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)