From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 9A0C145903; Wed, 4 Sep 2024 17:17:19 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 17AEF4275A; Wed, 4 Sep 2024 17:17:19 +0200 (CEST) Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.14]) by mails.dpdk.org (Postfix) with ESMTP id 968774025A for ; Wed, 4 Sep 2024 17:17:17 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1725463038; x=1756999038; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=zJV4jks9wye7H8je+tlONN3xoN7zOS0Nk5dLMFEJfMM=; b=mR7VCbe+ZYWL/kzIE8scarYbfe5pw2kJgIzji4JeeQ6jguS4A58hitlJ Tta57tE9+C5SFUSI+muUE12A88/gvkgLPtJpLIvvhMEok4aASlf6bIn9M 4gfFhBlCemRLrkTTdnBjjAG4cc1KTvFxBBqjHHeycP6LYhlqL8L3Hj72i /OpzU4BCBH1iHk20kuxIH5qHY8QW5pjir+yQdsujDPTUnv9sqEkh0bQA7 1sPikQJM5/7p+OrXZqKFVuPpfNacSoUztuU/UeiKxPfcQZJTUYdGSva3n 2HVjmy3WJUZnShHK0KR3H4gyucTt6wjpSKMqM4bxA935herJ+HPxgaOj1 Q==; X-CSE-ConnectionGUID: 37iJ+5h7TqGYIzbYGuLe5Q== X-CSE-MsgGUID: BmrnIGO+TOyOEmYtUtYVjQ== X-IronPort-AV: E=McAfee;i="6700,10204,11185"; a="24323721" X-IronPort-AV: E=Sophos;i="6.10,202,1719903600"; d="scan'208";a="24323721" Received: from fmviesa009.fm.intel.com ([10.60.135.149]) by fmvoesa108.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Sep 2024 08:17:16 -0700 X-CSE-ConnectionGUID: LTLmTTLCT8u9Yju6+e6hZA== X-CSE-MsgGUID: 4Nl8TfemTHCkYpMQA362MQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.10,202,1719903600"; d="scan'208";a="65338597" Received: from silpixa00401119.ir.intel.com ([10.55.129.167]) by fmviesa009.fm.intel.com with ESMTP; 04 Sep 2024 08:17:16 -0700 From: Anatoly Burakov To: dev@dpdk.org Cc: john.mcnamara@intel.com, bruce.richardson@intel.com Subject: [PATCH v1 0/1] Add DPDK build directory configuration script Date: Wed, 4 Sep 2024 16:17:13 +0100 Message-ID: X-Mailer: git-send-email 2.43.5 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Note: this patch depends upon Bruce's v3 patchset: https://patches.dpdk.org/project/dpdk/list/?series=32891 This patch is based on initial script for VSCode configuration: https://patches.dpdk.org/project/dpdk/patch/6a6b20c037cffcc5f68a341c4b4e4f21990ae991.1721997016.git.anatoly.burakov@intel.com/ This is basically a TUI frontend for Meson. It is by no means meant to be used as a replacement for using Meson proper, it is merely a shortcut for those who constantly deal with creating new Meson build directories but doesn't want to type out all components each time. It relies on dependency graphs from the above Bruce's patchset (v3 introduced support for optional dependencies, which this script requires) to work. It'll create a Meson build directory in the background, enabling all options, and then using both dependency graph and meson introspection to figure out what can be built, and what dependencies it has. With this script it is possible to produce very minimal builds - the script is not only able to track dependencies between components to enable them, but it can also (with a command line switch) specify which libraries we want to enable (omitting those not required by currently selected components). This can be useful for users who frequently reconfigure their tree with e.g. debug/release, shared/static etc. builds while keeping the reconfiguration time fairly small. We used to have a "setup.sh" script to "set up" DPDK. This is not that, but it's a good start. Anatoly Burakov (1): usertools: add DPDK build directory setup script usertools/dpdk-setup.py | 669 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 669 insertions(+) create mode 100755 usertools/dpdk-setup.py -- 2.43.5