Timberland nvme-cli/libnvme upstream merge - dbus dependency.
Daniel Wagner
dwagner at suse.de
Mon Feb 6 02:03:43 PST 2023
On Fri, Feb 03, 2023 at 10:30:13AM -0700, Keith Busch wrote:
> I'm just trying to build this right now on an embedded system, and my goodness,
> it is fucking painful. It's a bare-bones busybox enviroment with no internet
> connection. Just getting meson on there was unpleasant, and now the build just
> gives up with the failed dependencies.
I am sorry to causing pain. Let's see what how I can help you to make it less
hurt.
Is there a reason why you want to build it directly in a busybox environment and
not using a cross build?
I agree Meson itself is pretty anyoying in this scenario, though it should be
possible to use the alternative implementation. Meson is a specification with
more than one implementation. muon and samurai are written in plain C99 and only
use a compiler to work. Though I haven't tested this in a while. Let me give it
a quick test. I suppose it makes sense to add these to our CI build.
About the dependencies: There are only two non-optional dependencies:
libnvme: json-c
nvme-cli: json-c and zlib
and on closer inspection, I think we could ditch zlib as we only use the crc32
function from there. I'm preparing a PR for this.
I can look into making json-c optional again if you really don't want the JSON
related functionallity.
https://github.com/annacrombie/muon
https://github.com/michaelforney/samurai
More information about the Linux-nvme
mailing list