From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id E9B2DA045E for ; Thu, 30 May 2019 17:40:53 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id E66C95680; Thu, 30 May 2019 17:40:52 +0200 (CEST) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 5CFA84CA6 for ; Thu, 30 May 2019 17:40:51 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 May 2019 08:40:50 -0700 X-ExtLoop1: 1 Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by fmsmga007.fm.intel.com with ESMTP; 30 May 2019 08:40:50 -0700 Received: from fmsmsx115.amr.corp.intel.com (10.18.116.19) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 30 May 2019 08:40:50 -0700 Received: from bgsmsx153.gar.corp.intel.com (10.224.23.4) by fmsmsx115.amr.corp.intel.com (10.18.116.19) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 30 May 2019 08:40:50 -0700 Received: from bgsmsx101.gar.corp.intel.com ([169.254.1.245]) by BGSMSX153.gar.corp.intel.com ([169.254.2.217]) with mapi id 14.03.0415.000; Thu, 30 May 2019 21:10:47 +0530 From: "Varghese, Vipin" To: Thomas Monjalon CC: "dev@dpdk.org" , "Kovacevic, Marko" , "Mcnamara, John" , "Padubidri, Sanjay A" Thread-Topic: [dpdk-dev] [PATCH v2] doc/testpmd: update compile steps for bpf examples Thread-Index: AQHVEW4O9/GvlxQwfkK3SKgUbN//pKaBoUAAgAI2bZA= Date: Thu, 30 May 2019 15:40:46 +0000 Message-ID: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D355F7A@BGSMSX101.gar.corp.intel.com> References: <20190507084112.35296-1-vipin.varghese@intel.com> <20190523134744.73755-1-vipin.varghese@intel.com> <9691966.DS2kSCyb6N@xps> In-Reply-To: <9691966.DS2kSCyb6N@xps> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMDYxZmQ5NjctM2VhYS00YjgyLWEwNzgtMGY1YmQzMGMzNzNlIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoicEdQVklHcXRCMWwrYUtqR3BXdHA4dXRycW82MWNiWTN6QVJxWW1uUWZsWHo2TlVNdW5yenF4cHowbHdER0JJRiJ9 dlp-product: dlpe-windows dlp-version: 11.2.0.6 dlp-reaction: no-action x-originating-ip: [10.223.10.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v2] doc/testpmd: update compile steps for bpf examples 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" HI Thomas, Snipped > > + > > + To built other BPF examples, the compiler requires additional comma= nd- > line options. >=20 > "To built" -> "To build" ok >=20 > I think this note is vague. Don't you think it may confuse user if we don= 't > explicit which kind of options are required? Ok, the `v1` content was `In order to build t2.c and t3.c; pass DPDK target= s include and library path as compiler options.`. But as user adds other li= brary functions are added to `examples/bpf' these may vary too. Hence should we state as, `To build other BPF examples, appropriate librari= es and dependencies is to be passed as command line options.`