Failure to find tool x86_64-w64-mingw32-strip.exe on Windows

[damcaoson]

Hi,

It looks like the MinGW64 build for Windows has renamed x86_64-w64-mingw32-strip.exe to strip.exe. I'm getting the following error when running the Gradle task jnigenBuildHost on a fresh installation. I renamed strip.exe back to x86_64-w64-mingw32-strip.exe, and it worked fine.

Failure to find tool x86_64-w64-mingw32-strip.exe. Make sure that its available on your path
Failure to build
java.lang.RuntimeException: Tool was not found
	at com.badlogic.gdx.jnigen.build.ToolFinder.getToolFile(ToolFinder.java:56)
	at com.badlogic.gdx.jnigen.build.ToolFinder.getToolFile(ToolFinder.java:52)
	at com.badlogic.gdx.jnigen.build.toolchains.GNUToolchain.checkForTools(GNUToolchain.java:40)
	at com.badlogic.gdx.jnigen.build.toolchains.BaseToolchain.build(BaseToolchain.java:67)
	at com.badlogic.gdx.jnigen.build.PlatformBuilder$1.accept(PlatformBuilder.java:88)
	at com.badlogic.gdx.jnigen.build.PlatformBuilder$1.accept(PlatformBuilder.java:65)
	at com.badlogic.gdx.jnigen.build.PlatformBuilder.build(PlatformBuilder.java:65)
	at com.badlogic.gdx.jnigen.gradle.JnigenBuildTask.run(JnigenBuildTask.java:65)

[Tom-Ski]

That's annoying....
Its not going to be able to pick the correct strip in that case, as its based off unique names of the executable.
Perhaps we could hack in a fallback on windows. Use the compilers directory and fallback to a strip.exe in that same parent directory if we can't find with prefix on path.

[damcaoson]

Yes, I think adding a fallback lookup would be a simple and clean solution.