|BST - The multi-platform Propeller Tool Suite|
The bst suite of tools comprises :
This little application simply allows you to load pre-compiled .binary and .eeprom files into your propeller.
bstc is a completely Parallax syntax compatible SPIN and PASM compiler and linker.
bst is a fairly complete Integrated Development Environment that aims (and still
falls short) to be eventually comparable and compatible with the Parallax Propeller Tool.
bst and friends now have a manual. The manual is under constant development and improvement, however the latest version can always be found in this directory : Manual
Like bstc, bst has several features not found in other Propeller development tools, such as an integrated code listing window, basic serial debug terminal and complete project file management. bst also allows you to associate each editor window to a Propeller to allow easy management of multiple Propeller projects.
bst also has a native interface to Terry Hitt's PropBASIC compiler, allowing seamless integration of SPIN and PropBASIC projects in the bst IDE environment. Please download the latest PropBASIC binary for your platform here : PropBASIC Binaries
Bugs, niggles or issues with any of the tools can be reported directly to the author (proptools@NOSPAMPLEASEfnarfbargle.com) by removing the from NOSPAMPLEASE from the E-mail address.
Additionally, often updates, changelogs or bugs are reported in the Parallax Propeller Forums The development of bstl, bstc and bst can be followed on the Parallax forum threads linked below, and release notes and Changelogs are often posted in the top post.
bstl thread - http://forums.parallax.com/forums/default.aspx?f=25&m=297274
bstc thread - http://forums.parallax.com/forums/default.aspx?f=25&m=297566
bst thread - http://forums.parallax.com/forums/default.aspx?f=25&m=298620
All tools are presented in binary form and target the Windows Win32 platform, Linux i386 and MacOS X Intel and PowerPC
The QA procedures applied prior to an "official" release of any of the bst tend to be quite time consuming, so to speed up the "bug-fix" process, as issues are identified and fixed, periodic binary snapshots of the current development code will be uploaded to the snapshot directory. As these have not been through the QA process, we make even fewer guarantees that any of the code is "fit for purpose", however it does represent the binaries we are currently using ourselves.
If you are a Windows user and looking for setup.exe, you will find one Here