Factor contains a stand-alone application deployment tool that compiles a vocabulary down to a native executable which runs the vocabulary's MAIN: hook. Deployed executables do not depend on Factor being installed, and do not expose any source code, and thus are suitable for delivering commercial end-user applications.
Deploy tool documentation
Some of the demos in
To look at the deploy settings used, run
Look at Examples for more.
How it works
The deployment tool works by bootstrapping a fresh image, loading the vocabulary into this image, then applying various heuristics to strip the image down to minimal size.
Sometimes when you run the deploy tool, "staging images" get generated. These are minimal Factor images which do not contain your application, just parts of the library. Different staging images are generated for different deployment configurations. All applications you deploy will share the same set of staging images. This process can take a few minutes.
Once you've deployed your app once, you won't have to wait again, unless you delete them manually, or run the
Deploying apps that use FFI
Deployed applications require externally linked libraries to be present in the host OS, application folder, or .app bundle on Mac OS X. Factor includes the runtime library libfactor by default.
This revision created on Fri, 6 May 2011 01:32:13 by akkartik (Rollback)
All content is © 2008-2010 by its respective authors. By adding content to this wiki, you agree to release it under the BSD license.