From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id D94ADA04BF; Thu, 3 Sep 2020 17:38:27 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id C05031C295; Thu, 3 Sep 2020 17:29:57 +0200 (CEST) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id AA4C11C23D for ; Thu, 3 Sep 2020 17:29:55 +0200 (CEST) IronPort-SDR: AQBypO46CWUvbdf02Z5Sqk55EreeOGIjjIFmvLL8aGB7mQSTCF9uZFYrMILCKAAI1z3mymMSWg B5t1ZSoRwCLQ== X-IronPort-AV: E=McAfee;i="6000,8403,9733"; a="221808810" X-IronPort-AV: E=Sophos;i="5.76,387,1592895600"; d="scan'208";a="221808810" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Sep 2020 08:29:55 -0700 IronPort-SDR: GA2EqJJmv200RRu/CC1iN9gcc2kNGYlh+FiN3DNm1WX8gD6c4pxF9qX0WnL6+q3XrWiQzDaF8k UEDRoeelKduA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.76,387,1592895600"; d="scan'208";a="302244302" Received: from silpixa00399953.ir.intel.com (HELO silpixa00399953.ger.corp.intel.com) ([10.237.222.53]) by orsmga006.jf.intel.com with ESMTP; 03 Sep 2020 08:29:53 -0700 From: Ciara Power To: dev@dpdk.org Cc: Ciara Power , Thomas Monjalon , John McNamara , Marko Kovacevic Date: Thu, 3 Sep 2020 16:27:17 +0100 Message-Id: <20200903152717.42095-38-ciara.power@intel.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20200903152717.42095-1-ciara.power@intel.com> References: <20200807123009.21266-1-ciara.power@intel.com> <20200903152717.42095-1-ciara.power@intel.com> Subject: [dpdk-dev] [PATCH v3 37/37] doc: update quick build doc to remove make references X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Make is no longer supported for compiling DPDK, references are now removed in the documentation. Signed-off-by: Ciara Power Reviewed-by: Kevin Laatz --- doc/build-sdk-quick.txt | 55 ++++++++++++++++------------------------- 1 file changed, 21 insertions(+), 34 deletions(-) diff --git a/doc/build-sdk-quick.txt b/doc/build-sdk-quick.txt index bcfa7d6fe1..423104094e 100644 --- a/doc/build-sdk-quick.txt +++ b/doc/build-sdk-quick.txt @@ -1,34 +1,21 @@ -Basic build - make defconfig && make - or - make config T=x86_64-native-linux-gcc && make -Build commands - config get configuration from target template (T=) - defconfig auto-select target template based on arch, OS, etc. - all same as build (default rule) - build build in a configured directory - clean remove files but keep configuration - install T= configure, build and install a target in DESTDIR - install install optionally staged in DESTDIR - examples build examples for given targets (T=) - examples_clean clean examples for given targets (T=) - test compile tests and run basic unit tests - test-* run specific subset of unit tests - tags|etags|gtags generate tags database for given targets (T=) - cscope generate cscope database for given targets (T=) -Build variables - EXTRA_CPPFLAGS preprocessor options - EXTRA_CFLAGS compiler options - EXTRA_LDFLAGS linker options - EXTRA_LDLIBS linker library options - RTE_KERNELDIR linux headers path - RTE_DEVEL_BUILD stricter options (default: y in git tree) - CROSS toolchain prefix - V verbose - D debug dependencies - O build directory (default: build/ - install T= default: ./) - DESTDIR staging install directory (default: empty) - prefix root install directory (default: /usr/local) - T target template - used with config or install - format: - templates in config/defconfig_* +For many platforms, compiling and installing DPDK should work using the +following set of commands:: + + meson build + cd build + ninja + ninja install + +This will compile DPDK in the ``build`` subdirectory, and then install the +resulting libraries, drivers and header files onto the system - generally +in /usr/local. A package-config file, ``libdpdk.pc``, for DPDK will also +be installed to allow ease of compiling and linking with applications. + +After installation, to use DPDK, the necessary CFLAG and LDFLAG variables +can be got from pkg-config:: + + pkg-config --cflags libdpdk + pkg-config --libs libdpdk + +More detail on each of these steps can be got from the +"Installing DPDK Using the meson build system" section of the programming guides. -- 2.17.1