[Openmcl-devel] Re: Standalone binaries

[Hamilton Link]

With respect to the need to purchase a copy of whichever lisp system 
the app is created with, that depends... in the case of Allegro (from 
Franz, Inc.), if you pay for a suitable "Professional" license of 
Allegro you can I think (check their actual license) distribute a 
stripped-down version of their kernel along with your application that 
doesn't have the compiler, doesn't have Franz's development 
environment, and doesn't require the recipient of your application to 
purchase anything from Franz. If you want to include the compiler etc, 
your customers still don't have to buy anything from Franz, but *you* 
have to pay Franz a royalty for every copy you distribute (whether 
you're making a profit or not, IIRC, but again check their actual 
terms, I'm not representing Franz).

With Harlequin's Lispworks (or whoever is selling it today?), the 
licensing scheme is similar, I think. Your customers don't have to pay 
for Lispworks, but depending on what your distributing you have to pay 
royalties back to the vendor.

Bottom line, if you can develop your app in a free lisp, do so. If you 
can't, don't use the compiler in your app, just use it to build your 
app. If you can't do *that*, expect on turning enough of a profit to 
support the vendor as well.

h

On Friday, April 18, 2003, at 12:10 PM, Taoufik Dachraoui wrote:

> What I am asking for is probably not critical since openmcl is free, 
> but if openmcl was not free then anyone who wants to use your openmcl 
> application has to buy openmcl first.
>
> Another question, would be, if an image created on Mac OS X using 
> SAVE-APPLICATION can be used on a Linux system?
>
> Thank you for your help
>
> Taoufik
>
> On vendredi, avr 18, 2003, at 18:28 Africa/Tunis, Erann Gat wrote:
>
>>
>> On Fri, 18 Apr 2003, Taoufik Dachraoui wrote:
>>
>>> the JVM is allover the places, not openmcl.
>>
>> Sorry, can't help you there.  The world is the way it is.
>>
>>> For this reason I am looking for a way
>>> to create an executable where all needed stuff is in it (excluding
>>> functions in standard unix libraries and system calls), so that my 
>>> lisp
>>> applications can run on any unix system (I hope)!
>>
>> First, there is no way to create a binary executable (in any language)
>> that will "run on any unix system."  If you doubt this, try to take 
>> any
>> binary from one unix system (like Linux) and run it on a different 
>> unix
>> system (like Solaris).
>>
>> Second, Gary already told you how to create a standalone executable 
>> using
>> save-application.  You complained that it was too big, and I 
>> explained to
>> you why it had to be that big, and that the "fact" that apparently
>> self-contained C binaries appear small is really just an illusion.
>>
>> The only way to achieve what you seem to want is to make openmcl as
>> ubiquitous as the JVM.  That is a worthy goal, but very difficult to
>> achieve.  You are probably better off coming up with another plan.
>>
>> E.
>>
>
>
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/cgi-bin/mailman/listinfo/openmcl-devel
>



_______________________________________________
Openmcl-devel mailing list
Openmcl-devel at clozure.com
http://clozure.com/cgi-bin/mailman/listinfo/openmcl-devel