Use run_exports

[isuruf]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[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 (recipe) and found it was in an excellent condition.

[jakirkham]

Thanks Isuru! 🙏

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• travis: passed
• azure: failed

Thus the PR was not passing and not merged.

[jakirkham]

Weird the builds got all the way to the end, but failed. Not clear why. Trying to restart the failed builds

[isuruf]

@conda-forge-admin, rerender

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

Commits were made to this PR after the automerge label was added. For security reasons, I have disabled automerge by removing the automerge label. Please add the automerge label again (or ask a maintainer to do so) if you'd like to enable automerge again!

[JanuszL]

Will that change fix the recent problem introduced by the rhash lib so name change:

cmake: error while loading shared libraries: librhash.so.0: cannot open shared object file: No such file or directory
```?

[jakirkham]

Will that change fix the recent problem introduced by the rhash lib so name change:

cmake: error while loading shared libraries: librhash.so.0: cannot open shared object file: No such file or directory
```?

^ @jschueller does this sound familiar?

[jschueller]

no