Version 13, last updated by arst at Jul 07 19:55 2008 UTC
Building !FileWorkbench
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:
- makefile based builds on Unix (Linux/BSD/…)
- Visual Studio builds on Windows (2000/XP/Vista)
- premake based builds on Unix
- makefile builds on Windows (mingw32)
with the two first being more supported.
C++ Compiler
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.
Three Build Steps
Roughly speaking, for all builds, there are three main build steps:
- Building the wxWidgets library for a given platform
- Building other support libraries
- Building the FileWorkbench application
This order is followed pretty much for all platform/build combinations.
Build docs
More detailed build instructions are available in the files build-windows.txt and build-unix.txt .
Source code
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.
Mac – OS/X Port Status
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.
