#240 `ld` does not find the header objects and libraries when they are not relative to the JAR file

[Björn Kautler]

I have a Gradle task that executes Launch4j.
I use the Ant integration in Gralde for that.
I'd like to use the Launch4j and dependency JAR files directly from the Gradle dependencies cache.
For this I unpack the respective workdir artifact and set the launch4j.bindir system property so that windres and ld are found in that unpacked directory while the Launch4j jar is used from the original location.

The problem is, that this only affects where windres and ld are searched in. The windres call succeeds, but then the ld call fails as it given the header and library files relative to the jar containing the Util class still.

It would be nice if this could work somehow.
For example by specifying also that directory, or by being able to configure the whole basedir instead of the bindir.
Builder has a constructor that accepts a whole basedir, but it is used nowhere in the source code.

So I'd like to ask for a way to configure the basedir when calling the Ant task so that not only the executable, but also the header and library files are taken from there.

Please consider to make this an Ant task property (and also bindir) and not a System property (or additionally). If you use Launch4j from within another software, like the Gradle daemon and maybe even run things in parallel, using system properties is always building a race condition.