Added rocksdict as a package

[thewchan]

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-webservices]

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

[github-actions]

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

[thewchan]

@conda-forge/help-python-c @conda-forge/help-rust I added libclang to build and that made it work for win build, but maybe I need to point to it in some path variable in linux and osx build? Any pointers appreciated here

[xhochy]

I have seen this requirement before, but there one needed to put libclang into host.

[github-actions]

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

I Failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory.

[github-actions]

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/rocksdict/meta.yaml, recipes/example-v1/recipe.yaml, recipes/example/meta.yaml) and found some lint.

Here's what I've got...

For recipes/example-v1/recipe.yaml:

This is a v1 recipe and not yet lintable. We are working on it!

For recipes/example/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.

[thewchan]

I have seen this requirement before, but there one needed to put libclang into host.

Thanks @xhochy I'll try that

[xhochy]

Can you instead add a conda_build_config.yaml with

c_compiler:
  - clang
cxx_compiler:
  - clangxx

If that works, it's probably the more sustainable approach.

Suggested change

	- clangdev
	- clangxx

[thewchan]

let me try that thanks @xhochy

[thewchan]

@xhochy no luck; should I add clangdev back to build? Should I leave conda_build_config with clang in or out?

[thewchan]

Hmmm actually the error is something else

  - nothing provides requested clang_linux-64 13.*
  - nothing provides requested clangxx_linux-64 13.*

[thewchan]

https://conda-forge.org/news/2024/04/30/clang-everywhere/ maybe I need to specify compiler version like it says here?

[beckermr]

@conda-forge-admin relint

[github-actions]

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

[beckermr]

@conda-forge-admin relint

[thewchan]

okay, now it's still complaining about not able to find clang, so I think we might have to go with the clangdev in build solution. What do you think @xhochy ?

[xhochy]

okay, now it's still complaining about not able to find clang, so I think we might have to go with the clangdev in build solution. What do you think @xhochy ?

Yes, seems like the way forward. I would have liked to avoid it but it seems that is sadly not as straight-forward as hoped.

[thewchan]

@xhochy @conda-forge/staged-recipes @conda-forge/help-python this is ready to be reviewed again!

[github-actions]

To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks!