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 C860C4CC3 for ; Mon, 3 Sep 2018 03:09:02 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 61CCD21AE8; Sun, 2 Sep 2018 21:09:02 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 02 Sep 2018 21:09:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=daiDTVPb8sAATyfcucGQgVJ0vK +XkQnIszZVW275eSk=; b=DEK2S7YaNnecU5mokD4X6SMCBSrV8cTFzFuBpiLHdh cr9pj53jAVhM0zth/XART8yEhVoFUaUgyRokunBEq5i1hgEg+2EyvyL8Fk88x5DA sWTq4pg8CaRMz37+zAUqoXXqn3GbwiwI16Wv4V+N4mGcpBhagsB49mXFgVL8kLtP 4= 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-sender:x-me-sender:x-sasl-enc; s=fm3; bh=daiDTV Pb8sAATyfcucGQgVJ0vK+XkQnIszZVW275eSk=; b=hv1Wvs1mQ8HUZcTbDDkrjw 9WXkSoL6ZXVwLz8v2xK3Ujuu0H+on+auag8ElL8a6HL13BWQfjMtY84tO/MxuDly ADpCktBuHiG32kkc8cOnal9g+Q7Ze3ph4zHgOlCeFfb7AOuTinQ5zadYkmmlCq9E ibxgJDNADMfS1ZhqTC/2iQ5Z4Mx/hnyfJB7wGooovqzIzqkhX37uIPJ2IqkVI6nr qMTAQzxV8o61m2ruNy4citkvj0WemVlgKAEyzgzphVMzzwNKs5Hxn9PKhjSBtd70 hLPb1P+ze3Dhh+8hxqlfij4wVN2B/qKLO4xdkiXTwCwp6JuorduZyWhPhYgKv6fA == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 16F56E4122; Sun, 2 Sep 2018 21:09:01 -0400 (EDT) From: Thomas Monjalon To: Luca Boccassi Cc: dev@dpdk.org, bruce.richardson@intel.com, john.mcnamara@intel.com, marko.kovacevic@intel.com Date: Mon, 03 Sep 2018 03:09:00 +0200 Message-ID: <1581479.dLBctXLE49@xps> In-Reply-To: <20180831182055.30772-5-bluca@debian.org> References: <20180831182055.30772-1-bluca@debian.org> <20180831182055.30772-5-bluca@debian.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 4/4] build: generate API documentation with Meson 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: Mon, 03 Sep 2018 01:09:03 -0000 31/08/2018 20:20, Luca Boccassi: > Both a configuration-time "enable_docs" boolean option and an optional > 'ninja doc' target are available. Note that due to a Meson bug for now > the latter will only build, but not install the files. > > Signed-off-by: Luca Boccassi > --- > doc/api/generate_doxygen.sh | 10 ++++++++ > doc/api/meson.build | 51 +++++++++++++++++++++++++++++++++++++ > doc/build-sdk-meson.txt | 2 ++ > doc/meson.build | 4 +++ > meson.build | 3 +++ > meson_options.txt | 2 ++ > 6 files changed, 72 insertions(+) You use generate_doxygen.sh only with meson? Shouldn't we use the same in mk/rte.sdkdoc.mk?