FileWorkbench is built from one source tree for all platforms. Most source is shared but there are also some platform specific features. Also that is stored in the shared tree.
The main builds are:
with the two first being more supported.
A strong C++ compiler is required, since FWB uses template code to a large extent. GCC/G++ version 4.0 (or better) and Visual C++ 8.0 (or better) are supported. Other compilers may work, or earlier versions of GCC / VC might work, but that is not tested. Patches to support other maintained compilers are welcome.
Roughly speaking, for all builds, there are three main build steps:
This order is followed pretty much for all platform/build combinations.
More detailed build instructions are available in the files build-windows.txt and build-unix.txt .
NOT YET! Source code is available from our SVN repository, or can be downloaded (as a frozen version) here. In general, 3:rd party source code (under ext directory) is not included in our SVN, but must be downloaded and copied there. Patches to the libraries (*.p0, *.p1, *.p2, …) are kept in our SVN and should be applied before building.
There is nothing apparent stopping an OS/X port of FWB. The question is more one of building FileWorkbench against wxWidgets for Mac (Carbon port). It’s reasonable to expect some patch work, given that FWB exercises a fair bit of the wxWidgets library.
If anyone wants to investigate this further, please contact the FWB team.