On Thu, Jun 15, 2023 10:13:28 -, David Schwörer wrote:
> > $ sudo dnf repoquery -l python3-bout++ | grep info
> > # returns nothing
> >
> > Thanks again for all your replies. I'm going to spend some time
> > tinkering with the nest sources to see what I can do.
>
> They should be though in th
> $ sudo dnf repoquery -l python3-bout++ | grep info
> # returns nothing
>
> Thanks again for all your replies. I'm going to spend some time
> tinkering with the nest sources to see what I can do.
They should be though in the mpi packages:
$ sudo dnf repoquery -l python3-bout++-mpich | grep info
On Wed, Jun 14, 2023 12:59:40 -, David Schwörer wrote:
> > 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-in
> 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 setup.p
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 enabl
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 in
Hi Ankur,
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 enable packaging in fedora, but it also allowed to
just pip install the whole package, as BOUT++ is now
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 install in the
$MPI_SITEARCH locations, and then how do I get `pyprojec
On Mon, Jun 12, 2023 15:25:57 +0100, Ankur Sinha wrote:
> Quick addendum:
>
> Upstream has moved away from calling `setup.py` and now uses `pip`:
>
> https://github.com/nest/nest-simulator/blob/v3.4/pynest/CMakeLists.txt#L91
>
> Still not sure how to use the pyproject macros though.
No, that's
Quick addendum:
Upstream has moved away from calling `setup.py` and now uses `pip`:
https://github.com/nest/nest-simulator/blob/v3.4/pynest/CMakeLists.txt#L91
Still not sure how to use the pyproject macros though.
On Mon, Jun 12, 2023 15:04:54 +0100, Ankur Sinha wrote:
> Hi folks,
>
> I'm in t
Hi folks,
I'm in the process of updating the nest package to the latest release.
It uses cmake as its build system, but then the cmake calls `python
setup.py install` and so on to install the Python API. So, we strip that
bit out and call these commands ourselves in the right places in the
spec[1,
11 matches
Mail list logo
