Documentation Version for Comments and Changes

You are invited to make any changes...add any comments.

Changes will `eventually` be merged into the offical documentation.

Leave any commnents here...

...

... back to index page OE documentation

---

---

On Unix, the shrouder will make your shrouded file executable, and will add a ! line at the top, that will run eub.exe. You can override this ! line by specifying your own ! line at the top of your main Euphoria file.

Always keep a copy of your original source. There is no way to recover it from a shrouded file.

The Bind Command

Synopsis:

eubind [-c config-file] [-con] [-copyright] [-eub path-to-backend]  
       [-full_debug] [-i dir] [-icon file] [-list] [-quiet]  
       [-out executable_file] [-shroud_only [filename.ex] 

eubind does the same thing as eushroud, and includes the same options. It then combines your shrouded .il file with the interpreter backend (eub.exe, eubw.exe or eub) to make a single, stand-alone executable file that you can conveniently use and distribute. Your users need not have Euphoria installed. Each time your executable file is run, a quick integrity check is performed to detect any tampering or corruption. Your program will start up very quickly since no parsing is needed.

The Euphoria interpreter will not perform tracing on a bound file since the source statements are not there.

Options:

• -c config-file: A Euphoria config file to use when binding.
• -con: (Windows only): This option will create a Windows console program instead of a Windows GUI program. Console programs can access standard input and output, and they work within the current console window, rather than popping up a new one.
• -eub path-to-backend Allows specification of the backend runner to use instead of the default, installed version.
• -full_debug: Same as eushroud above. If Euphoria detects an error, your executable will generate either a partial, or a full, ex.err dump, according to this option.
• -i dir: A directory to add to the paths to use for searching for included files.
• -icon filename[.ico]: (Windows only) When you bind a program, you can patch in your own customized icon, overwriting the one in euiw.exe. eui.exe contains a 32x32 icon using 256 colors. It resembles an E) shape. Windows will display this shape beside euiw.exe, and beside your bound program, in file listings. You can also load this icon as a resource, using the name "euiw" (see ...\euphoria\demo\win32\window.exw for an example). When you bind your program, you can substitute your own 32x32 256-color icon file of size 2238 bytes or less. Other dimensions may also work as long as the file is 2238 bytes or less. The file must contain a single icon image (Windows will create a smaller or larger image as necessary). The default euphoria.ico, is included in the ...\euphoria\bin directory.
• -list: Same as shroud above.
• -quiet: Same as shroud above.
• -out executable_file: This option lets you choose the name of the executable file created by the binder. Without this option, eubind will choose a name based on the name of the main Euphoria source file.

A one-line Euphoria program will result in an executable file as large as the back-end you are binding with, but the size increases very slowly as you add to your program. When bound, the entire Euphoria editor, ed.ex, adds only 27K to the size of the back-end.

The first two items returned by command_line will be slightly different when your program is bound. See the procedure description for the details.