1. Up to you to design for and verify software security, just like any other platform. 2. Extensive use of `precompile`, plus the mentioned build_executable/userimg.jl, are the only two current options for precompiled native code. There is no attempt at obfuscation. Several such libraries exist for LLVM; in principle one could be integrated with Julia's codegen. However, this is not something I can imagine any core contributor would be willing to work on for free.
On Thu, Aug 27, 2015 at 5:36 AM, bernhard <[email protected]> wrote: > Dear all > > We have some Julia code which we would like to "deploy" client side. > Installing Julia (and possibly dependencies) on the clients machine(s) > should not be an issue. There are however two important restrictions we > face: > 1. The client data (on which our code will work) cannot leave their IT > environment. > 2. We want to protect our intellectual property (i.e. our code) at any > cost. > > Is this feasible today? Or is it partially feasible (i.e. in a way such > that decompliation is possible only to a certain extent). > > I must admit that I do currently not even know whether compilation is > possible (I think it is not in 0.3.10) and until now I always copied the > raw Julia code to other machines when I needed to calculated something on > other machines. > > Bernhard >
