Trouble with new lo-build

[Christian Lohmaier]

Hi Jürgen,

On Sun, Jul 6, 2025 at 4:05 PM Juergen Funk <j-funk at outlook.de> wrote:
>
> > 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

Oh, my AMD Ryzen disagrees (but might very well be that I already was
on a windows10 insider build at the time)

> > 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?

yeah, the chicken-and-egg problem. I think it is more important to
have git configured properly first.
If you were to clone the repo with the default setting that rewrites
line-endings you'll have "random" problems later.
And furthermore git-bash is installed as part of Visual Studio, so you
cannot really checkout the source without having installed /something/
first...

> > 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

Yeah, But that is not a lightweight installer you can offer people to
download to get "the necessary stuff".
I don't think there's an easy way for that/none that's easier than a
winget configuration file
and re latest version I meant the latest release of VS2022 for
example, while there are dedicated LTS channels to use e.g. 17.10.x
instead of 17.14.x, those also require additional commandline flags to
run, so again not easier than to run the installer and pass the
vsconfig file..


> > 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

To further debug output issues I'd recommend to not use any additional
wrappers.. Interesting output since the shifted lines/characters at
the end don't seem to be interwoven build-output, but looks more like
a cat sitting on the keyboard/spacebar...

anyhow no idea regarding that issue..

ciao
Christian