From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 02C231B2AB for ; Wed, 9 Jan 2019 11:02:24 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9028724A70; Wed, 9 Jan 2019 05:02:23 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 09 Jan 2019 05:02:23 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=JZNjJ+z84phT8epAdunAqgVoQzTqt5pl/JX+8z4woVI=; b=YN0IQnvWdv/k kyEFwOASN3jwR3kNyFZXMdhvm8E/OWMOY7aZvq8umI6t/BprTyLUGe09ZBVfZDKc J9vpJGY0E3voL3Sqbwe2SRpKk8y/lVYcMJIapT5ivhChLkRiAD3kvPbk2XkN5pOt QSKq6sOjZT8fT/w0y7s1hyn7+9WOgSw= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=JZNjJ+z84phT8epAdunAqgVoQzTqt5pl/JX+8z4wo VI=; b=obGioqlCcSFPVplsa/fSHx857fVoFiKEgFo1q5KcbuiaoO8Kl1/Hi8aym YPZwWDLe8qer5rNOxwcCd6KUYMtPfR/MxdQduS+AkbiFp2BTYfOw5HmZijIYE0Bx hce0EMXfXBjUzvqDsGg3INnIZnbr7FezVsoY3EVvNnmPuz2pMD7yDL6jei51Vbex wpEE2I+ICUN7ZauDNHT2C8yJ1AwXmLI3h29tz84MIf5rORf1X2EHJN9p2hqCXAfZ jnOSyqqRaKkiGu/cHKpMsPLHRNq/zxrr11CZ1rdFs+miB0GMsJfLts3RLAG1RBMp zhgg7VQG7iBMhU9D2S3hXro5QnO8w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrfedugdduudculddtuddrgedtkedrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 578D0100E5; Wed, 9 Jan 2019 05:02:22 -0500 (EST) From: Thomas Monjalon To: Bruce Richardson Cc: yskoh@mellanox.com, shahafs@mellanox.com, dev@dpdk.org, ferruh.yigit@intel.com Date: Wed, 09 Jan 2019 11:02:21 +0100 Message-ID: <3313625.hlFx3BV45W@xps> In-Reply-To: <20190109093738.GB2940@bricha3-MOBL.ger.corp.intel.com> References: <20190109020524.3633-1-thomas@monjalon.net> <20190109020524.3633-2-thomas@monjalon.net> <20190109093738.GB2940@bricha3-MOBL.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 2/2] config: add static linkage of mlx dependency 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: , X-List-Received-Date: Wed, 09 Jan 2019 10:02:24 -0000 09/01/2019 10:37, Bruce Richardson: > On Wed, Jan 09, 2019 at 03:05:24AM +0100, Thomas Monjalon wrote: > > The libraries provided by rdma-core may be statically linked > > if enabling CONFIG_RTE_IBVERBS_LINK_STATIC in the make-based build. > > If CONFIG_RTE_BUILD_SHARED_LIB is disabled, > > the applications will embed the mlx PMDs with ibverbs and the mlx libraries. > > If CONFIG_RTE_BUILD_SHARED_LIB is enabled, > > the mlx PMDs will embed ibverbs and the mlx libraries. > > > > Support with meson may be added later. > > > > Signed-off-by: Thomas Monjalon > > --- > Just to clarify - if there is a shared library build, the idea is to > actually link in the dependent .a files directly into the .so, rather than > having the driver .so's track their dependency on the other .so files? What > is the prospective use-case for this, and can it cause problems? I thought > it was generally not advisable to be linking in static libraries into > shared libraries. Yes that's it. It is supposed to ease the packaging for some users, because there are less packages to install on the target host. For instance, VPP may be interested. If rdma-core is not linked by the application, I don't see any issue.