From d1438a5c692ee6bf967cf6b16bf7b33d646a6ab5 Mon Sep 17 00:00:00 2001 From: Daniel Wagner Date: Tue, 8 Feb 2022 16:30:41 +0100 Subject: [PATCH] README: Mention meson subprojects update New meson users are not aware of this rather nifty update mechanism. Mention it in the README. While at it also mention the library dependency. Signed-off-by: Daniel Wagner --- README.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/README.md b/README.md index 2663869a..f8aa9a13 100644 --- a/README.md +++ b/README.md @@ -7,6 +7,8 @@ run following commands $ meson .build $ ninja -C .build +nvme-cli depends on zlib, json-c and libuuid. + To install, run: # meson install -C .build @@ -236,3 +238,15 @@ File: foo-plugin.c After that, you just need to implement the functions you defined in each ENTRY, then append the object file name to the meson.build "sources". + +## meson tips + +In case meson doesn't find libnvme header files (via pkg-config) it +will fallback using subprojects. meson checks out libnvme in +subprojects directory as git tree once and will not modify libnvme +unless explicitly told. That means the current branch is updated via +git, the subprojects/libnvme branch will not updated accordingly. So +either update it via normal git operations or + + $ meson subprojects update + -- 2.50.1