From: Anatoly Burakov <anatoly.burakov@intel.com>
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 [thread overview]
Message-ID: <cover.1725279341.git.anatoly.burakov@intel.com> (raw)
In-Reply-To: <cover.1721997016.git.anatoly.burakov@intel.com>
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
next prev parent reply other threads:[~2024-09-02 12:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 12:42 [RFC PATCH " Anatoly Burakov
2024-07-26 12:42 ` [RFC PATCH v1 1/1] devtools: add vscode configuration generator Anatoly Burakov
2024-07-26 15:36 ` Stephen Hemminger
2024-07-26 16:05 ` Burakov, Anatoly
2024-07-29 13:05 ` [RFC PATCH v2 0/1] Add Visual Studio Code configuration script Anatoly Burakov
2024-07-29 13:05 ` [RFC PATCH v2 1/1] devtools: add vscode configuration generator Anatoly Burakov
2024-07-29 13:14 ` Bruce Richardson
2024-07-29 13:17 ` Burakov, Anatoly
2024-07-29 14:30 ` Bruce Richardson
2024-07-29 16:16 ` Burakov, Anatoly
2024-07-29 16:41 ` Bruce Richardson
2024-07-30 9:21 ` Burakov, Anatoly
2024-07-30 10:31 ` Bruce Richardson
2024-07-30 10:50 ` Burakov, Anatoly
2024-07-30 15:01 ` [RFC PATCH v2 0/1] Add Visual Studio Code configuration script Bruce Richardson
2024-07-30 15:14 ` Burakov, Anatoly
2024-07-30 15:19 ` Bruce Richardson
2024-07-31 13:33 ` [RFC PATCH v3 " Anatoly Burakov
2024-07-31 13:33 ` [RFC PATCH v3 1/1] buildtools: add vscode configuration generator Anatoly Burakov
2024-09-02 12:17 ` Anatoly Burakov [this message]
2024-09-02 12:17 ` [PATCH v1 1/1] buildtools: add VSCode " Anatoly Burakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1725279341.git.anatoly.burakov@intel.com \
--to=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).