AW: Trouble with new lo-build

[Juergen Funk]

Hi Christian,

> It would be slower if you were to develop within the wsl2 container,
> but actually wsl1 should be a little faster for cross-realm access
> (you have the LibreOffice files on the windows side, and not inside
> the wsl container), but the wsl calls are so minimal that the
> difference in wsl version doesn't really have an effect on the
> build-time.
Okay, thank you for the hint, then I make under wsl1
Info: The problem with wsl2 is not the combination of Win10 as host and Win11 as Guest
the problem of the nested virtualisation is the AMD-CPU it not supported,
it works only with Intel-CPU, but in Win11 is that solved

> We do provide the .vsconfig file, just look into your core checkout
oh nice to see, but the docu start first with install the VS?


> nah, pretty sure that won't work. If at all you could share the
> webinstaller, but that in turn would download the current version. To
> install a specific version (for example 17.10 LTS you can use
> additional commandline options to the installer, but that really then
> it outside the scope)
ne I have already built this for the LHM, VS2017 is always installed there,
the installation is done from a virtual disk
We can save/update the current version with
vs_community.exe --layout ServerPath\VSLayout --lang de-DE --config 2022.vsconfig
but it is possible we copy from a windows-path to the ServerPath\VSLayout
And install with https://LO-server/ServerPath/VSLAYOUT/vs_community.exe --noWeb --wait --quiet --norestart
in this case installed all compoment from 2022.vsconfig
and the  command --noWeb says load only from our server not from MS-Server
we therefore have control over a functioning VS


> That output didn't include any color-control characters, but again
> pasting that with mail is hard, so not sure what the paste was
> actually meant to show.
pic1

>  If it is about maybe the lines overlapping,
> then using make -O to not print as lines come it, but only print all
> messages of a target at once might help.
pic2

Jürgen









________________________________________
Von: Christian Lohmaier <lohmaier at googlemail.com>
Gesendet: Freitag, 4. Juli 2025 13:21
An: Juergen Funk
Cc: libreoffice at lists.freedesktop.org
Betreff: Re: Trouble with new lo-build

On Fri, Jul 4, 2025 at 1:01 PM Juergen Funk <j-funk at outlook.de> wrote:
>
> > you can change the wsl version with "wsl --set-default-version 1" And
> > not sure whether it is needed since it has been so long since I
> > installed a container: wsl's --install command also has a
> > --enable-wsl1 command (that switch should install the "Windows
> > Subsystem for Linux" windows feature
> change to wsl 1 has solve the problem but is slower as wsl 2

It would be slower if you were to develop within the wsl2 container,
but actually wsl1 should be a little faster for cross-realm access
(you have the LibreOffice files on the windows side, and not inside
the wsl container), but the wsl calls are so minimal that the
difference in wsl version doesn't really have an effect on the
build-time.

> Orther question why we not using https://learn.microsoft.com/en-us/visualstudio/install/use-command-line-parameters-to-install-visual-studio?view=vs-2022
> that for install.
> vs_community.exe --wait --quiet --norestart --config C:\Install\meineKonfiguration.vsconfig
> if we provide the lo.vsconfig you can install VS automatically.

We do provide the .vsconfig file, just look into your core checkout /
that is also what the winget configuration uses.
The problem is the chicken and egg problem. You need git to checkout
the repo, and that is provided by visual studio installer, and also
you should make sure to set git to not mess with lineendings (set
core.autocrlf to false) before cloning. And that is what I meant with
"you can also manually pass the 2022.vsconfig file to the Visual
Studio installer/load it in the installer UI" (the .vsconfig file is a
link to the 2022.vsconfig file)

> Or even better, we keep our own executable version ready (last year at this time there was only a buggy version) because MS has changed the license you can only download the current version, so the problem is avoided and you link it is supported by MS.
> However, it then requires ~6,5GB on the server.

nah, pretty sure that won't work. If at all you could share the
webinstaller, but that in turn would download the current version. To
install a specific version (for example 17.10 LTS you can use
additional commandline options to the installer, but that really then
it outside the scope)

>
> > Not sure what you mean the same - if it is without the color control
> > characters, then it should just be default text color on default
> > background, and no garbled output should happen.
> but it does, here the output with
> /opt/lo/bin/make
> (no color)
> [build CXX] sd/source/ui/view/NotesPanelViewShell.cxx
> […]

That output didn't include any color-control characters, but again
pasting that with mail is hard, so not sure what the paste was
actually meant to show. If it is about maybe the lines overlapping,
then using make -O to not print as lines come it, but only print all
messages of a target at once might help.

ciao
Christian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic1.jpg
Type: image/jpeg
Size: 119602 bytes
Desc: pic1.jpg
URL: <https://lists.freedesktop.org/archives/libreoffice/attachments/20250706/554ad6b3/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic2.jpg
Type: image/jpeg
Size: 174073 bytes
Desc: pic2.jpg
URL: <https://lists.freedesktop.org/archives/libreoffice/attachments/20250706/554ad6b3/attachment-0003.jpg>