Manual aarch migration

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I've started rerendering the recipe as instructed in #56.

If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!

Here's a checklist to do before merging.

• Bump the build number if needed.

[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.

[hmaarrfk]

@conda-forge-admin please rerender

[hmaarrfk]

Please ensure that this change, jupyter -> jupyter_core didn't accidentally delete a feature of your package.

I see that jupyter is used in some tests.
https://github.com/SHTOOLS/SHTOOLS/blob/77ecaabbe90aee89ecc252317c8c6b4258e59bad/examples/notebooks/meson.build#L4

We are honestly pretty "light on tests" at conda-forge to favor ease of building.

Maybe you can just remove jupyter from a build time dependency altogether?

[hmaarrfk]

@conda-forge-admin please rerender

[MarkWieczorek]

Thanks for looking into this! For Jupyter: we actually don't run the tests that require jupyter. However, the meson-build system that we are using checks anyways to make sure that its installed and fails if it isn't. jupyter-core is fine, in fact I think that is what we use in our ci-tests.

[hmaarrfk]

I think you have some issues with your cross compilation. I'm quite bad at meson and just use the github search to find something to copy.

The fact the arch and ppc64le packages were failing on azure + cross compilation indicates that maybe your mac osx package is broken.

I'm not sure why windows is failing now that I moved pkg-config. You should investigate.

While travis is "fast" it is quite "unreliable" and will randomly fail at jobs. Given the build is fast, we can try emulation + azure. This will be my last "push" to this PR.

[hmaarrfk]

@conda-forge-admin please rerender

[hmaarrfk]

However, the meson-build system that we are using checks anyways to make sure that its installed and fails if it isn't.

That is unfortunate. Maybe this is something to consider for future work.

[MarkWieczorek]

@jan-janssen Would you mind taking a quick look at windows builds, since you were the one to get these working. Perhaps the solutions is make pkg-config a host dependency?

[jan-janssen]

Perhaps the solutions is make pkg-config a host dependency?

@MarkWieczorek This week is rather busy for me. If you have a concrete idea, I would suggest just testing it on a separate branch. My Windows expertise is also limited all I can do is trail and error.