On Sunday 02 August 2009 17:28:01 keller wrote: > On Aug 2, 2009, at 1:53 PM, Jörn Nettingsmeier wrote: > > keller wrote: > >> On Aug 2, 2009, at 12:50 PM, Raymond Martin wrote: > >>> I am referring to the Launch4J scripts to build an executable and > >>> others. > >>> For example, you have an .exe for windows, isn't Launch4J what was > >>> used? > >>> If so, there is a script for it, as indicated in the build.xml. > >> > >> As stated before, launch4j is a commercial product that I was using > >> on > >> a trial version. There is no way that I can provide that. I was > >> considering buying it if worked well, but even then, I cannot provide > >> it. > >> > >> All it does is wrap the .jar file and other dirs to make it > >> convenient > >> for the users to install and launch. So I guess you're saying it's > >> not > >> allowed? > > > > as stated in another mail, this is hogwash. you are perfectly entitled > > to chose whatever build tool you want, without having to redistribute > > it. just be careful that all the third-party software you include has > > the original build files included. > > As I am hearing now then, I can use install4j as long as I provide the > install4j script (but not install4j itself) in the source repository. > > Is that correct? >
Yes. Raymond _______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
