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 E8019A0536; Tue, 4 Feb 2020 23:34:11 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 553E21C210; Tue, 4 Feb 2020 23:34:11 +0100 (CET) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 52F621C1C4 for ; Tue, 4 Feb 2020 23:34:10 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D7D05220E2; Tue, 4 Feb 2020 17:34:09 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 04 Feb 2020 17:34:09 -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=SBzextUY9O4X2LAYd1eD3CA+wLt0aU+8dyJkJVV6+Hg=; b=l/ulSKqcUfeV WOznnX0PeKx2Qlft309CM/QUAIwhydnjFYGZqKt3HbqmfOtEU2rfFBayYRhGQiCG tlWtDhIS0mT+1yTa+X/xmG7AvCSLqIfoQpZgByA03aqzT+zMJO6z4wRLMbaDfnSh bm/Ul3gfV6x7PvST3UDuPuKttqiLjjI= 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=SBzextUY9O4X2LAYd1eD3CA+wLt0aU+8dyJkJVV6+ Hg=; b=V2zkkHLODrbkWPTNN76TEreUbFh2kmgQRjCbH8CAsgJfl8zBuzT+Gwuhk PScUT+wbEnSXxc0P2aI1xaAvR4RI5fRwWTAI7I324+xcp5n1C+r433QYxd+kwTnU Dr2s6FJ9NxjDBgH3jHTbvCGnHzlbHzF7Eo8FjB5RREdAJI4m6uR8L5HoeBFZyY21 mnrO7nftQdP5FOA/p9hRQ9+PgVnMmZfQ47SJzDt4MPl/5FUjqmJXMOUY/p13dRYs 2DiWImoUv+61MAFka9QvNcxfyQgvMW6rYkGlXqc2FxHdlM3U6UOGIV5vFnVIfIHq GMozf/dKS8JiWqiigqMLV32Lf3ZCg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrgeelgdduheekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuff homhgrihhnpeguphgukhdrohhrghenucfkphepjeejrddufeegrddvtdefrddukeegnecu vehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrg hssehmohhnjhgrlhhonhdrnhgvth 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 A01C03280059; Tue, 4 Feb 2020 17:34:08 -0500 (EST) From: Thomas Monjalon To: Dmitry Kozlyuk Cc: dev@dpdk.org, Harini Ramakrishnan , Omar Cardona , Pallavi Kadam , Ranjit Menon , John McNamara , Marko Kovacevic , Tal Shnaiderman Date: Tue, 04 Feb 2020 23:34:07 +0100 Message-ID: <2467193.BddDVKsqQX@xps> In-Reply-To: <20200131030744.19596-7-dmitry.kozliuk@gmail.com> References: <20200131030744.19596-1-dmitry.kozliuk@gmail.com> <20200131030744.19596-7-dmitry.kozliuk@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 6/6] doc: guide for Windows build using MinGW-w64 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" 31/01/2020 04:07, Dmitry Kozlyuk: > Instructions for different toolchains presented as options on the > corresponging steps of the guide, so that common parts may be reused. > > Signed-off-by: Dmitry Kozlyuk [...] > --- a/doc/guides/windows_gsg/build_dpdk.rst > +++ b/doc/guides/windows_gsg/build_dpdk.rst > -The DPDK and its applications require the Clang-LLVM C compiler > -and Microsoft MSVC linker. > +Building the DPDK and its applications requires one of the following > +environments: > + > +* The Clang-LLVM C compiler and Microsoft MSVC linker. > +* The MinGW-w64 toolchain (either native or cross). [...] > +Option 1. Native Build on Windows > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > -Specifying the compiler might be required to complete the meson command. > +When using Clang-LLVM, specifying the compiler might be required to complete > +the meson command: [...] > +When using MinGW-w64, it is sufficient to have toolchain executables in PATH: [...] > +Option 2. Cross-Compile with MinGW-w64 > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I think having the choice between GCC and Clang for Windows is very cool. When starting the Windows port, I asked the fundamental question of the supported compilers. The answer was MinGW adds "non-standard" DLLs: https://mails.dpdk.org/archives/dev/2019-January/124236.html Now the question is to know which one is the easiest to use? If I understand well, MinGW brings the missing parts we are trying to add in the DPDK repository for compliance with POSIX libraries.