Bug 156708 - Automate installing and checking for individual components of Visual Studio on Windows
Summary: Automate installing and checking for individual components of Visual Studio o...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
24.2.0.0 alpha0+
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Dev-related
  Show dependency tree / graph
 
Reported: 2023-08-10 09:49 UTC by Hossein
Modified: 2024-12-14 16:13 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Hossein 2023-08-10 09:49:51 UTC 
One of the reasons that some people fail to build LibreOffice on Windows is the lack of individual Visual Studio components. They have to be installed manually in a tedious task, which is also error prone.

On the other hand, it is possible to do it automatically, and (possibly) query the installed components.

Use command-line parameters to install, update, and manage Visual Studio
https://learn.microsoft.com/en-us/visualstudio/install/use-command-line-parameters-to-install-visual-studio?view=vs-2022

How to automate (from command-line) the installation of a Visual Studio Build Tools build environment, for C++, .NET, C#, etc
https://stackoverflow.com/q/62551793

There are 2 tasks here: To automate installing and checking for individual components of Visual Studio on Windows:

1. Install: The required components should be installed with a script. Even a separate script can be OK in my opinion.

2. Check: The installed components should be checked during the configuration phase, and if something is missing, the user should be asked to run the script added for #1.