AW: Trouble with new lo-build

[Juergen Funk]

Hi Christian,

Thanks for the tips,

but since I never use LODE (I prefer to have everything under my control.), I always find it annoying to install VS, even though it can be installed in the same way as cygwin. That's why I would like to provide the command for this in the documentation as an alternative. Is that okay? I will also test it (then with wsl).

vs_community.exe --quiet --wait --norestart --add Microsoft.VisualStudio.Workload.CoreEditor -add Microsoft.VisualStudio.Workload.NativeDesktop -add Microsoft.Net.Component.4.8.SDK -add Microsoft.VisualStudio.Component.Git -add Microsoft.VisualStudio.Component.VC.ATL -add Microsoft.VisualStudio.Component.VC.CMake.Project -add Microsoft.VisualStudio.Component.VC.ATL.ARM64 -add Microsoft.VisualStudio.Component.VC.Llvm.Clang -add Microsoft.VisualStudio.Component.VC.Redist.MSM -add Microsoft.VisualStudio.Component.VC.Tools.x86.x64 -add Microsoft.VisualStudio.Component.VC.Tools.ARM64 -add Microsoft.VisualStudio.Component.VC.Tools.ARM64EC -add Microsoft.VisualStudio.Component.Windows11SDK.22621

That way, you don't have the chicken-and-egg problem, and it's easier to copy than always having to search for it together.


best
juergen

________________________________________
Von: Christian Lohmaier <lohmaier at googlemail.com>
Gesendet: Freitag, 25. Juli 2025 14:26
An: Juergen Funk
Cc: Ilmari Lauhakangas; libreoffice at lists.freedesktop.org
Betreff: Re: Trouble with new lo-build

On Thu, Jul 24, 2025 at 7:15 PM Juergen Funk <j-funk at outlook.de> wrote:
>
> Hi Christian,
>
> > IANAL, but all the documents I read about that read about intranet or
> > a share in your company or something like that, even if there's a
> > network based method, it still doesn't sound to me like it could be
> > offered over the internet.
> Yes, you're right, I confused that with the “offline layout via web server,” which is not what we have.
>
> But you can also install it using the command line.
> for example (can not found the .vsconfig)

the .vsconfig is also in the root of the core repository (linked to
the .config/vs2022.vsconfig file, there's also a 2022_cross.vsconfig
file that would add the necessary components to cross compile for
ARM64)

> vs_community.exe --quiet --wait --norestart --add Microsoft.VisualStudio.Workload.ManagedDesktop --add Microsoft.VisualStudio.Workload.NetWeb

yeah, since we're not using only the workloads, but also need some
individual components, using the vsconfig instead is much
easier/shorter.

> winget install --id Microsoft.VisualStudio.2022.Community --override "--quiet --add Microsoft.VisualStudio.Workload.ManagedDesktop --includeRecommended"

The winget configuration file uses winget to install visual studio, so
that's coming full-circle :-) and as for --includeRecommended: that's
used by the default .config/configuration.winget - the
.config/jenkins.winget omits those (and also uses the cross variant of
the config)

> In the documentation, we could include a note about installing
> vs_community --quiet --wait --norestart --add Microsoft.VisualStudio.Workload.ManagedDesktop --add ...
> as an alternative to manual installation.

I don't see a point in using manual vs-installer method over winget
configure, the latter is much simpler (and doesn't require you to hunt
down the vs-installer beforehand)

> > "winget configure -f .config/configuration.winget" – that will install
> > visual studio with the required packages
> Where can I find the document?

That's in the core repo – it is basically using winget as you
described above to install VS, except that it doesn't manually list
the components (which the configuration could just as well), but it
uses the vsconfig file that already exists for the list of packages.

Winget configure is described here:
https://learn.microsoft.com/en-us/windows/package-manager/configuration/
The part specifically for Visual Studio lives here:
https://github.com/microsoft/VisualStudioDSC

ciao
Christian