Spitfire - Process Development Framework Code
Status: Alpha
Brought to you by:
fluctus
Menu
▾
▴
Tree [69fff3] master 0.5.1 / History
marko
Read Me
NOTE! The Spitfire is (currently) at alpha stage, so you may not want to do a full install. Instead you can experiment with it within the source package. The official Spitfire paying-around-and-having-fun instructions: ---------------------------------------------------------------- *********************************** MACOSX Users! You may want to modify the shared memory system settings: sudo nano /etc/sysctl.conf kern.sysv.shmmax=16777216 kern.sysv.shmmin=1 kern.sysv.shmmni=128 kern.sysv.shmseg=32 kern.sysv.shmall=4096 and reboot. http://www.spy-hill.net/help/apple/SharedMemory.html *********************************** First you have to configure the environment. For this purpose there is a set of scripts on the utils directory fluctus@WhiteRabbit:~/Prog/spitfire$ cd utils/ fluctus@WhiteRabbit:~/Prog/spitfire/utils$ ls make.sh runme-non-argp.sh runme-osx.sh runme.sh run.sh spf.cfg fluctus@WhiteRabbit:~/Prog/spitfire/utils$ The 'make.sh' is the script that is used for configuring and building the Spitfire system. Execution of the script may take some time, since it also compiles the software. fluctus@WhiteRabbit:~/Prog/spitfire/utils$ ./make.sh + aclocal + type glibtoolize + libtoolize --force --copy libtoolize: putting auxiliary files in `.'. ... make[1]: Leaving directory `/home/fluctus/Prog/spitfire' fluctus@WhiteRabbit:~/Prog/spitfire/utils$ --- If you had all the necessary packages installed, the system is ready to run. Go up one level and run the basic tests. This also takes some time. Don't worry about the memory dump text. This is an alpha software, so I want to verify that the memory looks okay... (And it looks cool...) fluctus@WhiteRabbit:~/Prog/spitfire/utils$ cd .. fluctus@WhiteRabbit:~/Prog/spitfire$ make check Making check in src make[1]: Entering directory `/home/fluctus/Prog/spitfire/src' Making check in core ... PASS: ex_999_daemon =================== All 25 tests passed =================== make[3]: Leaving directory `/home/fluctus/Prog/spitfire/examples' make[2]: Leaving directory `/home/fluctus/Prog/spitfire/examples' make[1]: Leaving directory `/home/fluctus/Prog/spitfire/examples' make[1]: Entering directory `/home/fluctus/Prog/spitfire' make[1]: Leaving directory `/home/fluctus/Prog/spitfire' fluctus@WhiteRabbit:~/Prog/spitfire$ fluctus@WhiteRabbit:~/Prog/spitfire$ So, all the tests pass, and you are ready to go. You can have a look at the examples in the 'examples' directory. They give some general idea how to work with the system. --- The daemons can be started manually by running the script 'runme.sh' fluctus@WhiteRabbit:~/Prog/spitfire$ cd utils/ fluctus@WhiteRabbit:~/Prog/spitfire/utils$ . ./runme.sh done. fluctus@WhiteRabbit:~/Prog/spitfire/utils$ The MACOSX users need to run the other script, namely 'runme-non-argp.sh' fluctus@WhiteRabbit:~/Prog/spitfire/utils$ . ./runme-non-argp.sh done. fluctus@WhiteRabbit:~/Prog/spitfire/utils$ --- There are instructions for programming and starting the system on the 'doc' directory. They are in .tex format so you need to compile them first. There is a README file on the 'doc' directory explaining how to compile the documents in the Ubuntu system. The other Linuxes work similarly. Mac instructions will follow later on. --- Have fun!
