On 3/8/06, Andrus Adamchik <andru..bjectstyle.org> wrote:
> Also I suspect that even if you fix the win-path-ref issue, you'd
> still need a Windows specific version of Launch4J as there is some
> native code involved in building the .exe
Yes, I just realized that my "fix" was pointing at the linux directory.
I've installed windows launch4j 2.1.1. I've copied it over into
lib/windows/launch4j-2.1.1 mirroring what was done for mac/linux.
One thing I noticed was that the mac/linux versions don't contain
demo/head_src/src/web and a bunch of the top-level files. Was this
intentional? I checked the file sizes, and the "missing" pieces in
2.1.1 were only a fraction of the size of the copied pieces, so I
decided to copy over everything.
The build still failed with the xstream NoClassDefFoundError, but I
know that xstream is one of the jar files delivered with 2.1.1, so I
hopefully will be able to solve this.
I also noticed that launch4j is GPL'd software. We're going to have
to figure out how to remove this during incubation. We can probably
put it down as an optional system requirement for doing certain
releases.
This archive was generated by hypermail 2.0.0 : Wed Mar 08 2006 - 13:17:49 EST