Skip to content

Conversation

@martin-belanger
Copy link

@martin-belanger martin-belanger commented Jan 8, 2026

Now that nvme-cli and libnvme live in the same GitHub repository, meson builds both by default. When building the PyPI package, however, we only want to build libnvme and the Python bindings, not the nvme executable.

@igaw - I think this will fix the PyPI issue. This adds "-Dnvme=disabled -Dlibnvme=enabled -Dpython=enabled" to the meson setup options. If there are other options you would like to set (maybe --prefix, --sysconfdir, --buildtype, etc.) please feel free to update accordingly.

Now that nvme-cli and libnvme live in the same GitHub repository,
meson builds both by default. When building the PyPI package,
however, we only want to build libnvme and the Python bindings,
not the nvme executable.

Signed-off-by: Martin Belanger <[email protected]>
@igaw
Copy link
Collaborator

igaw commented Jan 9, 2026

Let's see if does the trick :)

@igaw igaw merged commit 75697ab into linux-nvme:master Jan 9, 2026
20 checks passed
@igaw
Copy link
Collaborator

igaw commented Jan 9, 2026

 pip install \
  --index-url https://test.pypi.org/simple/ \
  --extra-index-url https://pypi.org/simple/ \
  libnvme==2.16.dev2176

meson-python: error: Could not map installation path to an equivalent wheel directory: '{prefix}/etc/nvme/discovery.conf'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants