From 29058550643267a554e0368806dece63b047c5cb Mon Sep 17 00:00:00 2001 From: Luca Boccassi Date: Mon, 19 Nov 2018 12:59:01 +0000 Subject: New upstream version 18.11-rc4 Change-Id: I861e1a2f7df210f57f44f1ad56b9ef789a4675e3 Signed-off-by: Luca Boccassi --- doc/guides/sample_app_ug/vm_power_management.rst | 25 ++++++++++++++++++++++++ 1 file changed, 25 insertions(+) (limited to 'doc/guides/sample_app_ug/vm_power_management.rst') diff --git a/doc/guides/sample_app_ug/vm_power_management.rst b/doc/guides/sample_app_ug/vm_power_management.rst index 1ad4f149..5be9f24d 100644 --- a/doc/guides/sample_app_ug/vm_power_management.rst +++ b/doc/guides/sample_app_ug/vm_power_management.rst @@ -657,6 +657,31 @@ To build just the ``guest_vm_power_manager`` application using ``make``: The resulting binary will be ${RTE_SDK}/build/examples/guest_cli +.. Note:: + This sample application conditionally links in the Jansson JSON + library, so if you are using a multilib or cross compile environment you + may need to set the ``PKG_CONFIG_LIBDIR`` environmental variable to point to + the relevant pkgconfig folder so that the correct library is linked in. + + For example, if you are building for a 32-bit target, you could find the + correct directory using the following ``find`` command: + + .. code-block:: console + + # find /usr -type d -name pkgconfig + /usr/lib/i386-linux-gnu/pkgconfig + /usr/lib/x86_64-linux-gnu/pkgconfig + + Then use: + + .. code-block:: console + + export PKG_CONFIG_LIBDIR=/usr/lib/i386-linux-gnu/pkgconfig + + You then use the make command as normal, which should find the 32-bit + version of the library, if it installed. If not, the application will + be built without the JSON interface functionality. + To build just the ``vm_power_manager`` application using ``meson/ninja``: .. code-block:: console -- cgit 1.2.3-korg