From 8dea11bac682456cc1e3c861c9415b1082e4f829 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stanislav=20Angelovi=C4=8D?= Date: Tue, 9 Jul 2019 18:29:58 +0200 Subject: [PATCH] Add note on solving potential getent-related Yocto errors --- docs/using-sdbus-c++.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/using-sdbus-c++.md b/docs/using-sdbus-c++.md index a9fb778..0368e2f 100644 --- a/docs/using-sdbus-c++.md +++ b/docs/using-sdbus-c++.md @@ -106,6 +106,8 @@ There are two recipes: * One for sdbus-c++ itself. It detects whether systemd feature is turned on in the poky linux configuration. If so, it simply depends on systemd and makes use of libsystemd shared library available in the target system. Otherwise it automatically downloads and builds libsystemd static library and makes it an opaque part of sdbus-c++ shared library. The recipe also supports ptest. * One for sdbus-c++ native tools, namely sdbus-c++ code generator to generate C++ adaptor and proxy binding classes. +Tip: If you get `ERROR: Program or command 'getent' not found or not executable` when building sdbus-c++ in Yocto, please make sure you've added `getent` to `HOSTTOOLS`. For example, you can add `HOSTTOOLS_NONFATAL += "getent"` into your local.conf file. + Header files and namespaces ---------------------------