From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] app/testpmd: link with virtio PMD when using shared libraries Date: Thu, 30 Nov 2017 14:16:46 +0100 Message-ID: <1923056.CMZaFarxgz@xps> References: <3208097.sCyqhKb3JL@xps> <20171130122147.1d10053f@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, echaudro@redhat.com, Jingjing Wu To: Timothy Redaelli Return-path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 680D828EE for ; Thu, 30 Nov 2017 14:16:48 +0100 (CET) In-Reply-To: <20171130122147.1d10053f@redhat.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 30/11/2017 12:21, Timothy Redaelli: > Just a little question: if testpmd loads the pmds dynamically using > dlopen, why in app/test-pmd/Makefile some PMD are linked at > build time? Some PMD have an API. That's why they need to be directly linked by the applications calling these driver-specific functions.