Add nsight-compute recipe

[adibbley]

xref: #21382

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

[jakirkham]

Thanks Alex! 🙏

Had a couple questions below

[bdice]

Small request for testing the executable, otherwise please apply @jakirkham's suggestions.

[vyasr]

FWIW this could probably be generalized using something like

set +e
rm -rf nsight-compute/*/target/*x86
set -e

The set would only be needed if a nonzero exit code is problematic.

[adibbley]

IMO when it comes to removing things from the build I would rather keep this specific, so if something gets added we aren't removing it without knowing.

[bdice]

LGTM once open conversations are resolved.

[jakirkham]

Thanks Alex! 🙏

Maybe we can try adding wrapper scripts to call the .exes (as below). This is a strategy we have used for similar situations in the past (though it is always possible the code below needs additional tweaks)

[jakirkham]

Suggesting dropping the missing_dso_whitelist portion since this may already be addressed by dependencies since added. Even if not, would be good if we can solve this with adding dependencies instead to gain some confidence that this will work in a user's environment

[jakirkham]

Thanks Alex! 🙏

Think we need to add these dependencies based on the linking errors in CI. Though we may need more. Will need to look at CI based on the results after adding these

[jakirkham]

Thanks all! 🙏

Let's get this one out. We can follow up on anything else in the feedstock 🙂