Bug 141156 - Create 'vscode-ide-integration' build target to prepare VS Code IDE integration, like other integrations are created
Summary: Create 'vscode-ide-integration' build target to prepare VS Code IDE integrati...
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-22 06:25 UTC by Mike Kaganski
Modified: 2022-07-26 13:48 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Kaganski 2021-03-22 06:25:16 UTC
Thanks to Cloph, we have a great VS Code template for IDE integration [1]. But it is managed differently compared to all other IDE integrations: VS, Vim, Qt Creator, KDevelop, XCode. While all those are generated using

> make <name>ide-integration

that makes sure it's prepared and placed correctly for this system, VS Code integration is just a static workspace configuration, that does not automatically adjust to the environment.

E.g., on Ubuntu 20.04, gdb is not at  /usr/libexec/gdb, but at /usr/bin/gdb.

This task is about converting VS Code workspace configuration into a proper 'vscode-ide-integration' build target, which could use the existing files to replace some keywords with system-specific values, place to the proper place, remove the "the workspace file is recreated from a template whenever configure is run" step mentioned in current wiki, and potentially do other kinds of customizations required for rich IDE experience.

[1] https://wiki.documentfoundation.org/Development/IDE#Visual_Studio_Code_.28VSCode.29
Comment 1 Roman Kuznetsov 2021-03-23 20:35:27 UTC
I think it's more an enhancement. Set to NEW
Comment 2 Christian Lohmaier 2022-07-26 13:48:38 UTC
that was done with https://gerrit.libreoffice.org/c/core/+/126860  - just didn't think of putting the bugnumber into the subject line...