Hi *, On Thu, Jul 3, 2025 at 7:09 PM Regina Henschel <[email protected]> wrote: > it does not work for me. > > There was a missing bracket.
A yes, missed the closing parenthesis of the $(MSYSTEM) variable, sorry for that. > So I have used > sh -c "cd $(shell cygpath -ml $(BUILDDIR)); $(if $(MSYSTEM),$(WSL) > )$(SRCDIR)/autogen.sh" And just to be extra sure: you also added the line for SRCDIR above the target, right? > Then after making the suggested changes, I run autogen.sh. > After that I see again the changed Makefile files and the bogus > include/include file. > > My autogen.sh is > c:/BuildLO4/core/autogen.sh \ > --with-external-tar=c:/BuildLO4/externalsrc \ > […] > --enable-python=fully-internal \ > PKG_CONFIG=C:/BuildLOAdds/pkg/pkgconf-2.4.3.exe That should be fine, (and not sure whether you really call it with all the options on the commandline, you can put all of them in autogen.input so you don't have to specify them every time. > What information can help you to determine what goes wrong for my build? I guess we need to switch to the autogen.sh directly then. in the block "if ($src_path ne $build_path)" is where the problem occurs, when $src_path and $build_path aren't really different, but one is a shortened path and the other is a full-length one. But looking at your paths, BuildLO4 is only 8 characters long, so there shouldn't be any need for path shortening/there shouldn't be a difference between shortened path and long path. So let's find out what paths the autogen.sh actually uses when comparing. Remember that autogen.sh is actually perl, so above the "if ($src_path ne $build_path)" line add a line print STDERR "src_path: -$src_path- build_path: -$build_path-\n"; and you can stick an exit(1); in there as well to stop it from messing up the checkout while debugging that. What kind of difference there'll be between the src_path and build_path variables should give further hints as to how to fix that issue. ciao Christian
