# Stand alone binary executable

**URL:** <https://discourse.julialang.org/t/stand-alone-binary-executable/5026>\
**Category:** General Usage\
**Created:** [July 23, 2017, 2:03am UTC](https://discourse.julialang.org/t/stand-alone-binary-executable/5026 "2017-07-23T02:03:33Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![RoyiAvital](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/royiavital/32/571_2.png) [@RoyiAvital](https://discourse.julialang.org/u/RoyiAvital)\
**Post date:** [July 24, 2017, 12:29pm UTC](https://discourse.julialang.org/t/stand-alone-binary-executable/5026/12 "2017-07-24T12:29:07Z")

</div>

This feature was asked over and over on [List of most desired features for Julia v1.x](https://discourse.julialang.org/t/list-of-most-desired-features-for-julia-v1-x/4481).

I think the solution should be composed of 2 steps:

1. Allow something like [MATLAB’s p File](https://www.mathworks.com/help/matlab/ref/pcode.html). Maybe it should be only on JuliaPro or something like that. Probably even someone could create a package to allow similar functionality with user own key or something like that.
2. Something like MATLAB Compiler to allow creation of a full independent application (Executable).

### Update

The reason I wrote it might be only by Julia Pro isn’t in order to put it behind paywall.  
The idea was that someone needs to embed the key in the engine and not tell the rest of the world and they are the one who distribute binaries.

If there’s a way to do it otherwise (Each one creates its own key yet the code can somehow be shared) it would have been even better.

---

_[View the full topic](https://discourse.julialang.org/t/stand-alone-binary-executable/5026)._