From: David Hunt <david.hunt@intel.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, david.hunt@intel.com, john.mcnamara@intel.com
Subject: [dpdk-dev] [PATCH] doc/power: add info on jansson conditional build
Date: Thu, 1 Nov 2018 16:55:49 +0000 [thread overview]
Message-ID: <20181101165549.17497-1-david.hunt@intel.com> (raw)
Add more info to the docs on how to set environmental variable to
correctly build the vm_power_manager sample app in a cross compile
or multilib environment by setting PKG_CONFIG_LIBDIR.
Signed-off-by: David Hunt <david.hunt@intel.com>
---
.../sample_app_ug/vm_power_management.rst | 24 +++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/doc/guides/sample_app_ug/vm_power_management.rst b/doc/guides/sample_app_ug/vm_power_management.rst
index 1ad4f1490..b5280d727 100644
--- a/doc/guides/sample_app_ug/vm_power_management.rst
+++ b/doc/guides/sample_app_ug/vm_power_management.rst
@@ -657,6 +657,30 @@ 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
--
2.17.1
next reply other threads:[~2018-11-01 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 16:55 David Hunt [this message]
2018-11-16 15:47 ` [dpdk-dev] [PATCH v2] " David Hunt
2018-11-16 15:52 ` Kovacevic, Marko
2018-11-19 0:25 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181101165549.17497-1-david.hunt@intel.com \
--to=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).