Thanks Miro - that size pointer was helpful. Indeed, the only thing in the wheel are 3
metadata files.
Things seem to be OK up to this point in the upstream hatchling build:
https://github.com/dmlc/xgboost/blob/43897b829680d241491abe1ecd46b2ba9d33...
... that temporary directory is populated with all the python files in what looks like a
good format, but the generated wheel is essentially empty. Is there any way to see
what's happening inside that hatchling.build.build_wheel call I wonder?
In related news, a setup.py based build works correctly. Perhaps it would be simpler to
just give up on the upstream python build bits? (already having to patch them a fair bit
since they don't supported versioned soname on libxgboost).
Thanks for all the insights.
cheers.
--
Nathan