Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Master cf rebase #45

Closed

Conversation

mingwandroid
Copy link
Contributor

No description provided.

mingwandroid and others added 30 commits June 20, 2018 10:13
This is an upstream recommendation:

https://cran.r-project.org/doc/manuals/r-release/R-admin.html#Using-ICU-for-collation

Unfortunately, this adds quite a bit to the binary size and r-stringi still links
to its own ICU (again upon their recommendation).
Also adds OpenBLAS and makes the Windows layout the same as Unix
so we can share packages that do not require compilation as noarch: generic
(as BUILD_PREFIX does not get considered for prefix replacement)
.. also workaround strong run_exports not being used in host and mingw-w64
toolchain being in the host section instead of the build section.
This is because R likes to add x64 to, for example, LOCAL_SOFT and
this means our libs and headers do not get found. Instead, since we
use MSYS2/mingw-w64 compilers and our libs are all in the sysroot
we can ensure the libs and headers get found provided we do not split
them into a different prefix to the prefix that contains the compilers
…S support

Would like to remove NLS since neither MRO nor offical R releases
use it.
… libiconv + bzip2 deps

We probably need to use -dead_strip_dylibs and -no_implicit_dylibs in the clang activate script,
but I tested with both those and still got overlinking, so it's probably a bug in ld64. Either
way I do not have time to fix this at present so instead I hack a Makefile.
This is so that the values baked into Makeconf work when users run install.packages()
Since R has an options(download.file.method) of curl (as well as libcurl)
@conda-forge-linter
Copy link

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

  • Jinja2 variable definitions are suggested to take a {%<one space>set<one space><variable name><one space>=<one space><expression><one space>%} form. See lines [2]

For recipe:

  • Jinja2 variable definitions are suggested to take a {%<one space>set<one space><variable name><one space>=<one space><expression><one space>%} form. See lines [2]

@conda-forge-linter
Copy link

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@jdblischak jdblischak mentioned this pull request Jun 20, 2018
6 tasks
@bgruening
Copy link
Contributor

@mingwandroid is working on a new iteration of this PR for 3.5.1

@bgruening bgruening closed this Aug 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants