> On Tue, Jun 13, 2023 08:31:49 -, David Schwörer wrote:
> That's interesting. So it builds the cpython as part of the cmake build
> and then simply installs it in the required directory.
>
> How does it generate the dist-info metadata, though? That's the bit
> where nest uses `python
On Mon, Jun 12, 2023 21:07:05 +0200, Miro Hrončok wrote:
> On 12. 06. 23 16:04, Ankur Sinha wrote:
> > However, I can't figure out how I would replicate the build using the
> > `pyproject` macros. I guess `pyproject_wheel` usage is straightforward
> > (?), but how do I get `pyproject_install` to
On Tue, Jun 13, 2023 08:31:49 -, David Schwörer wrote:
> Hi Ankur,
Hi David,
Thanks for your reply.
> Not sure whether that helps, but BOUT++ (requires MPI) switched to a
> custom back end [1] when it switched to cmake [2] from configure +
> calling setup.py. The main motivation was to
