Uwe, Dawid, and Robert, Thank you for the helpful pointers! I do have Visual Studio 2017 on my machine which I don't use much lately.
https://github.com/microsoft/vswhere *"vswhere* is included with the installer as of Visual Studio 2017 version 15.2 and later, and can be found at the following location: %ProgramFiles(x86)%\Microsoft Visual Studio\Installer\vswhere.exe." From the Gradle github you shared, looks like it first tries to locate vswhere on the machine and execute some command on it. If not found it just returns an empty list. So I removed vxwhere.exe from the path and builds are successful now! Although this is a stop gap measure, it will work for me. Thanks a lot! https://github.com/gradle/gradle/blob/v7.3.3/subprojects/platform-native/src/main/java/org/gradle/nativeplatform/toolchain/internal/msvcpp/version/CommandLineToolVersionLocator.java#L63 -Rahul On Wed, Sep 14, 2022 at 11:51 AM Dawid Weiss <dawid.we...@gmail.com> wrote: > > I have no idea how to fix this. Dawid: Maybe we can also make the > > configuration of that native stuff only opt-in? So only detect Visual > > Studio when you actively activate native code compilation? > > It is an opt-in, actually. The problem is: gradle fails on applying the > plugin - even if the tasks are ignored. > > I'm +1 to remove the native thing entirely if nobody is using it and > there are no benefits to keeping it maintained. > > Dawid > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >
