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 9CCC7458E8; Mon, 2 Sep 2024 14:17:53 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 68ABC40651; Mon, 2 Sep 2024 14:17:53 +0200 (CEST) Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.18]) by mails.dpdk.org (Postfix) with ESMTP id AEB45402E6 for ; Mon, 2 Sep 2024 14:17:51 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1725279472; x=1756815472; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=nemVjPceT99XFjCblIJXD1lwWMeywsrVdCoHkvE+6TI=; b=Jc8r8tpTjw+BUFIZlDGXJSmFMhrLObjYkanV2RlMbWTIKKppBCs/IOS6 bEceIcJshx/UMeFcjrVSLES973OZtuhfyWobX4LXw8ExJYbwIMWY22L1W Wf+uT+5vuBHo3HRdokQJFbmnCXG9gHSF8oyAhX5gv3NR3b9BglXW0BC3h UEdQDOTz2sQ+H/kEYUj1FieHRdpIa54sHZOqqq018s/407v9c9uOcXaPU GJgtYE0Sg8anKnKxm62H5mic9qz3CH3PILjORk77JAwYMqc6DEz6azcB5 22Eg4cPEmRCpkNyY/IfBnUUdCQi00jMjpZQiBRFfP35u27dBOzk0Q9sM2 g==; X-CSE-ConnectionGUID: AOOZaogiSBaDMn+XkDEIng== X-CSE-MsgGUID: X2IeDarLSbaBJcksHRbIQA== X-IronPort-AV: E=McAfee;i="6700,10204,11182"; a="23990037" X-IronPort-AV: E=Sophos;i="6.10,195,1719903600"; d="scan'208";a="23990037" Received: from orviesa006.jf.intel.com ([10.64.159.146]) by orvoesa110.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Sep 2024 05:17:51 -0700 X-CSE-ConnectionGUID: PXi+tjguR9uAqBX6DHGcAQ== X-CSE-MsgGUID: LbciqY6URUK2VP+L0bGapg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.10,195,1719903600"; d="scan'208";a="64950046" Received: from silpixa00401119.ir.intel.com ([10.55.129.167]) by orviesa006.jf.intel.com with ESMTP; 02 Sep 2024 05:17:50 -0700 From: Anatoly Burakov To: dev@dpdk.org Cc: john.mcnamara@intel.com, bruce.richardson@intel.com Subject: [PATCH v1 0/1] Add Visual Studio Code configuration script Date: Mon, 2 Sep 2024 13:17:47 +0100 Message-ID: X-Mailer: git-send-email 2.43.5 In-Reply-To: References: 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 Lots of developers (myself included) uses Visual Studio Code as their primary IDE for DPDK development. I have been successfully using various incarnations of this script internally to quickly set up my development trees whenever I need a new configuration, so this script is being shared in hopes that it will be useful both to new developers starting with DPDK, and to seasoned DPDK developers who are already or may want to start using Visual Studio Code. It makes starting working on DPDK in Visual Studio Code so much easier! ** NOTE: While code analysis configuration is now populated from Meson and should pick up platform- or OS-specifc configuration, I have no way to test the code analysis configuration on anything but Linux/x86. ** NOTE 2: this is not for *Visual Studio* the Windows IDE, this is for *Visual Studio Code* the cross-platform code editor. Specifically, main target audience for this script is people who either run DPDK directly on their Linux machine, or who use Remote SSH functionality to connect to a remote Linux machine and set up VSCode build there. While the script should in theory work with any OS/platform supported by DPDK, it was not tested under anything but Linux/x86. (if you're unaware of what is Remote SSH, I highly suggest checking it out [1]) Philosophy behind this script is as follows: - Any build directory created will automatically add itself to VSCode configuration - Launch configuration is created using `which gdb`, so by default non-root users will have to do additional system configuration for things to work. This is now documented in a new section called "Integration with IDE's". - All of the interactive stuff has now been taken out and is planned to be included in a separate set of scripts, so this script now concerns itself only with adding build/launch targets to user's configuration and not much else Please feel free to make any suggestions! [1] https://code.visualstudio.com/docs/remote/ssh Anatoly Burakov (1): buildtools: add VSCode configuration generator app/meson.build | 14 +- buildtools/gen-vscode-conf.py | 570 ++++++++++++++++++++ buildtools/meson.build | 5 + devtools/test-meson-builds.sh | 3 + doc/guides/contributing/ide_integration.rst | 85 +++ doc/guides/contributing/index.rst | 1 + doc/guides/rel_notes/release_24_11.rst | 5 + examples/meson.build | 15 +- meson.build | 14 + 9 files changed, 710 insertions(+), 2 deletions(-) create mode 100755 buildtools/gen-vscode-conf.py create mode 100644 doc/guides/contributing/ide_integration.rst -- 2.43.5