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?
Thanks.
Bob
Robert M. Keller, Csilla & Walt Foley Professor of Computer Science
Harvey Mudd College
Claremont, California 91711
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Received on Mon Aug 3 04:15:03 2009
This archive was generated by hypermail 2.1.8 : Mon Aug 03 2009 - 04:15:03 EEST