From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>, <john.mcnamara@intel.com>
Subject: Re: [RFC PATCH v2 0/1] Add Visual Studio Code configuration script
Date: Tue, 30 Jul 2024 17:14:29 +0200 [thread overview]
Message-ID: <47f8ac03-239a-4560-b30d-f651b99592eb@intel.com> (raw)
In-Reply-To: <ZqkASqziWbjBr6Rb@bricha3-mobl1.ger.corp.intel.com>
On 7/30/2024 5:01 PM, Bruce Richardson wrote:
> On Mon, Jul 29, 2024 at 02:05:51PM +0100, Anatoly Burakov wrote:
>> 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 using Visual Studio Code. It makes starting working
>> on DPDK in Visual Studio Code so much easier!
>>
>> ** NOTE: Currently, only x86 configuration is generated as I have no way to test
>> the code analysis configuration on any other platforms.
>>
>> ** 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. No other OS's are currently
>> supported by the script.
>>
>> (if you're unaware of what is Remote SSH, I highly suggest checking it out [1])
>>
>> Philosophy behind this script is as follows:
>>
>> - The assumption is made that a developer will not be using wildly different
>> configurations from build to build - usually, they build the same things, work
>> with the same set of apps/drivers for a while, then switch to something else,
>> at which point a new configuration is needed
>>
>> - Some configurations I consider to be "common" are included: debug build, debug
>> optimized build, release build with docs, and ASan build (feel free to make
>> suggestions here!)
>>
>> - By default, the script will not add any meson flags unless user requested it,
>> however it will create launch configurations for all apps because not
>> specifying any flags leads to all apps being enabled
>>
>> - All parameters that can be adjusted by TUI are also available as command line
>> arguments, so while user interaction is the default (using whiptail), it's
>> actually not required and can be bypassed
>>
>
> The management of dependencies of components to be built is obviously a
> tricky area here, when specifying e.g. enable_drivers flags. It may be
> possible to improve the situation in meson itself, but that probably
> requires massive rework of the lib/meson.build, drivers/meson.build and
> app/meson.build files to process the subdirs and save the results for later
> use (effectively process them twice within the restrictions of meson only
> allowing subdir once).
>
> In the meantime, as a better-than-nothing improvement, I've pushed a draft
> patch to have meson produce a dependencies file as part of its processing[1].
> That may be of use to you in doing new versions of the TUI - i.e. in the
> background you could run a dummy meson config to /tmp and then process the
> resulting deps file from it, to allow you to recursively enable
> dependencies of the user-selected components..
Thanks, this looks very interesting! It's a shame it can't be done
without creating a build directory at all (e.g. by using meson dummy
runs or something), but like you said, better than nothing!
>
> Regards,
> /Bruce
>
> [1] https://patches.dpdk.org/project/dpdk/patch/20240730145508.551075-1-bruce.richardson@intel.com/
--
Thanks,
Anatoly
next prev parent reply other threads:[~2024-07-30 15:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 12:42 [RFC PATCH v1 " 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 [this message]
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 ` [PATCH v1 0/1] Add Visual Studio Code configuration script Anatoly Burakov
2024-09-02 12:17 ` [PATCH v1 1/1] buildtools: add VSCode configuration generator 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=47f8ac03-239a-4560-b30d-f651b99592eb@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).