Compile valgrind wrapper

[jaimergp]

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.

Relevant refs upstream:

• Build the native extension during packaging CodSpeedHQ/pytest-codspeed#56
• Build the native extension during packaging CodSpeedHQ/pytest-codspeed#57
• https://github.com/CodSpeedHQ/pytest-codspeed/releases/tag/v3.1.0

[jaimergp]

@conda-forge-admin, please rerender

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

[jaimergp]

This is ready now @xhochy @kenodegard, thanks! Oops wait, this was noarch but the linter didn't bark at me when I added the compiler. "arching" it now.

[jaimergp]

@conda-forge-admin, please rerender

[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 (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

• ❌ Non noarch packages should have python requirement without any version constraints.

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

[jaimergp]

@conda-forge-admin, please rerender

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

[xhochy]

Is this only visible with an import test? Couldn't we also execute something what did break in your job directly?

[jaimergp]

We'd need to create a pytest test file and run it. Not against it, but the import test looked simpler.

[jaimergp]

@conda-forge-admin, please rerender

[xhochy]

We probably need something here like we do for aiohttp: Build a noarch package for all platforms, but also have an arch-specific one for linux.

[jaimergp]

Upstream only publishes linux wheels now, though. I'm not even sure this works outside Linux environments.

[xhochy]

Let's merge and see whether someone requests osx support.

[art049]

Hey just discovered this repo.

As you mentionned, we just switched to prebuilt wheels in pytest-codspeed [v3.1.0]9https://github.com/CodSpeedHQ/pytest-codspeed/releases/tag/v3.1.0).

Upstream only publishes linux wheels now, though. I'm not even sure this works outside Linux environments.

It works outside linux environment however the instrumentation capabilities are not enabled.