Add pyside2ads and qtadvanceddocking recipe

[n-elie]

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.
• 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-linter]

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

[conda-forge-linter]

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/pyside2ads, recipes/qtadvanceddocking) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/qtadvanceddocking:

• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

[conda-forge-linter]

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/pyside2ads, recipes/qtadvanceddocking) and found it was in an excellent condition.

[conda-forge-linter]

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/pyside2ads, recipes/qtadvanceddocking) and found some lint.

Here's what I've got...

For recipes/qtadvanceddocking:

• The source section contained an unexpected subsection name. missing_dso_whitelist is not a valid subsection name.

[conda-forge-linter]

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/pyside2ads, recipes/qtadvanceddocking) and found it was in an excellent condition.

[n-elie]

@conda-forge-admin, please restart ci

[n-elie]

@conda-forge-admin, please restart ci

[n-elie]

@conda-forge/help-python-c All requested changes have been made, could you please have a look again?

[carterbox]

clang is not our default compiler toolchain for linux. This is why the compiler directive is not installing libcxx for you.

Is there a reason that this project cannot compile with gcc on linux? Your addition of clangdev is adding extra dependencies that are not being used by the build or at runtime.

[carterbox]

stddef.h is not unique to clang it shouldn't require clangdev to be installed. Do you have a link to the spefic log output where this error occurred?

[n-elie]

@conda-forge/help-python-c Could you please review again? This PR was not accepted because of clangdev dependency but I don't know how to compile without this

[carterbox]

Build is broken. Please fix.

[carterbox]

In that recipe, the run_exports from clangdev are ignored.

https://github.com/conda-forge/qtmolecularnetwork-feedstock/blob/9c25b7f1b2f880255d23b0d90ff2622edebabd65/recipe/meta.yaml#L65

[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/pyside2ads, recipes/qtadvanceddocking) and found it was in an excellent condition.