- python 2.7.9
- cmake 2.8.11 or better
- a working C/C++ development environment:
- on OSX: Xcode + command line tools
- on Linux: make/gcc (or clang)
- on Windows: Visual Studio 2013 or better
fips will create additional directories on the same directory level as the fips directory itself, thus it is recommended to git-clone fips into a separate ‘workspace’ directory:
Test if fips works
Invoke the fips main script by running ‘./fips’ from within the fips directory:
NOTE: on Windows, run ‘fips’ instead of ‘./fips’
NOTE: usually ‘./fips’ is run from the root directory of a ‘fipsified’ C/C++ project, not from the fips directory
Run ‘./fips help’ to show available fips commands:
You can also show help for a single command:
Get required tools
Run ‘./fips diag tools’ to check for required tools, install any that are listed as ‘NOT FOUND’. The list of required tools may differ depending on your host platform.
NOTE that some tools are optional and only required for specific build configurations
Setup new project
A new fips project can be setup by running ‘./fips init path/to/project’. This will copy a few commonly used fips config files into the target project directory. From the fips directory run ‘./fips init project-1’ and the following will be setup for you:
NOTE fips will look for the folder in the root of the fipsified project (in this case the fips-workspace created above) and not in the fips folder itself.
From now on you can run all fips commands directly in the new project’s directory.