add r-cpprouting

[cmkobel]

Generated using https://github.com/bgruening/conda_r_skeleton_helper

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[conda-forge-admin]

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 (recipes/r-cpprouting/meta.yaml) and found some lint.

Here's what I've got...

For recipes/r-cpprouting/meta.yaml:

• ❌ This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12356938860. Examine the logs at this URL for more detail.}

[github-actions]

Hi! This is the staged-recipes linter and I found some lint.

It looks like some changes were made outside the recipes/ directory. To ensure everything runs smoothly, please make sure that recipes are only added to the recipes/ directory and no other files are changed.

If these changes are intentional (and you aren't submitting a recipe), please add a maintenance label to the PR.

File-specific lints and/or hints:

• recipes/example-v1/README.md:

  • lints:
    • Please put your recipe in its own directory in the recipes/ directory as recipe/<name of feedstock>/<your recipe file>.yaml.

• recipes/example-v1/recipe.yaml:

  • lints:
    • Do not edit or delete example recipes in recipes/example/ or recipe/example-v1/.

• recipes/example/meta.yaml:

  • lints:
    • Do not edit or delete example recipes in recipes/example/ or recipe/example-v1/.

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

[conda-forge-admin]

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 (recipes/r-cpprouting/meta.yaml) and found it was in an excellent condition.

[conda-forge-admin]

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 (recipes/r-cpprouting/meta.yaml) and found some lint.

Here's what I've got...

For recipes/r-cpprouting/meta.yaml:

• ❌ This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12392774848. Examine the logs at this URL for more detail.}

[conda-forge-admin]

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 (recipes/r-cpprouting/meta.yaml) and found it was in an excellent condition.

[cmkobel]

Hello, I used @bgruening's script for generating this recipe.

I'm adding this package to conda-forge because I eventually want to add r-distillR to bioconda, but it depends on this package.

As you can probably figure out I'm not experienced with troubleshooting OS specific issues for building recipes, but I keep getting D:/bld/r-cpprouting_1734524565570/_h_env/lib/R/bin/x64/Rscript.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory after a few minutes of building on windows. Does anyone know how to fix this issue?

Best, Carl.