Protecting libraries

Solar2D General Questions/Discussion
#1

I have developed several apps, and over the years I have created a quite extensive code library. 

There’s this new app I need to develop and and its code has to be transferred to the customer (including intellectual property). Now I would really like to use my own code library since that’ll take me far less time to develop, but I do not want to share the code from that library. 

Is there a way that I can compile my existing lua code in that library and use it as a binary plug-in? Without using an Enterprise license?

Looking forward to your replies.

Best regards,

~Rob

#2

You might consider the plugin route:  https://coronalabs.com/blog/2015/06/23/tutorial-building-a-pure-lua-plugin-for-corona/

You should be able to just include the compiled plugin in a folder named “plugin” in the project and they would in theory only have access to your compiled bytecode.

You probably want to test this before  you head down this road. Most people making plugins distribute them through the store, but I’m guessing this will work.

Rob

#3

Alternately, amend your contract and make it clear that they don’t get rights to that library content.  I’d talk to a lawyer about this though.

I have this same problem when working with clients. :confused:

#4

You might consider the plugin route:  https://coronalabs.com/blog/2015/06/23/tutorial-building-a-pure-lua-plugin-for-corona/

You should be able to just include the compiled plugin in a folder named “plugin” in the project and they would in theory only have access to your compiled bytecode.

You probably want to test this before  you head down this road. Most people making plugins distribute them through the store, but I’m guessing this will work.

Rob

#5

Alternately, amend your contract and make it clear that they don’t get rights to that library content.  I’d talk to a lawyer about this though.

I have this same problem when working with clients. :confused: