|
Download
You can download the source code to sbf at the
SourceForge downloads page. The current version is 0.9.4.
Select your platform:
I assume most Linux users can install a program built with autoconf. If you already know this, skip the next paragraph.
Mac OS X users who don't know about the command-line need to learn about it before trying to use sbf. Not trying to be elitist or asinine, but the program only has a command-line interface, and if you can't use the OS X command-line, you can't use a command-line program. A handy reference for the OS X command line (and bash in general) for newbies can be found here.
To install sbf on any Unix-like environment, download and uncompress the folder, then cd to the folder. Type ./configure to create the Makefile, then make to build sbf. To install it so it can be called as a builtin program, type make install. To run tests before (or after) installation to make sure that sbf is working correctly, type make check. sbf will probably be installed in /usr/local/bin. It's manpages will be installed in /usr/local/man/man1 and /usr/local/man/man7.
sbf has a man page - sbf(1) - which documents the program and all it's options. It also comes with numerous other manpages - bflang(7), bfport(7), etc. - most of which are about the brainfuck language more than sbf's functionality. Basically, anything in man1 is about sbf, the program, and anything in man7 is about brainfuck, the language.
sbf also comes with a few extra programs that are built around parts of the sbf source code. These are meant mostly to show how sbf's parts can be reused in other programs. To compile these, type make extra.
sbf also has some incomplete features, such as partial language translations. These are disabled by default. To enable them, sbf must be compiled with the EXPERIMENTAL macro defined. To do this, type make experimental.
Top
The best way to use sbf under Windows is to install Cygwin and follow the instructions for Linux. Any native build of sbf would require a C compiler (I recommend MinGW), a GNU-compliant version of make for Windows, and would still require someone to execute the ./configure shell script in a bash shell, with some modifiers specifying the final compilation target and such. It may be best to try and build a Windows port on Linux or OS X and then just test it on Windows, and distribute the binary, since Windows is so hard to develop on.
Top
|
|