BuildFactory - Create a self-executable binary

System: BeOS, Zeta

Binding yab sources is an easy and quick job, however the data in your code isn't very secure. Therefor it's a good thing to bind your source code with the BuildFactory. The BuildFactory does not only bind your source code on yab, he compress the source before.

The BuildFactory is included in yab. Check under /boot/home/yab-interpreter if there is a folder with the name BuildFactory. If not it's best to download the newest one at the Projektpage.

yab can be downloaded over cvs from the Projectpage. How you do this can be found here.

Create backups for any important data that you lying around in the yab-interpreter folder before updating the new version over cvs..

If you have installed cvs you can now switch in the Terminal to the yab-interpreter location. With cvs update you can easily update the yab source to the latest version.

Here some rules to bind the source code using the BuildFactory: 

• Names for Subroutines can only be used once, no mater how many files you use. If a name is used twice only one will be used.
• If you use libraries, please ensure that they are included inside subs and export subs. If you use other functions between sub and export subs, they will be ignored.
• All libraries who are merged with import in the program code will be considered. Considered are also Libraries who are merged in Libraries.
• The libraries have to be in the same folder as the source file or in /boot/home/config/lib/yab/.
• All source files must reside in the BuildFactory folder to bild.:

Binding Source code

To bind your source code copy all related (to the source code) files inside the BuildFactory folder (Mainfile, Libraries, ...). Open a Terminal session and change into the BuildFactory folder. Now enter the next command in the Terminal to bind the source file

If [-ZETA-Tab] is used, ZETA Tabs will be created. If you leave this option out the Haiku Tabs will be used (default).

The binary will be saved in the Buildfactory if you don't add a path to the command. On top of that you will find a few more files, once the new Source code and the error files.

Possible Problems

- With older ZETA version it can be that the ZETA Tabs don't function, you'll see an error message appearing then. In that case it's best to use the Haiku Tabs.

- You have to got ncurses to be able to bind the source code with the BuildFactory. If ncurses is not installed you can find it at BeBits.