Get Started

You need:

  • 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

Get fips

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:

> cd ~
> mkdir fips-workspace
> cd fips-workspace
> git clone
> cd fips
> _

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’

> ./fips
run 'fips help' for more info

NOTE: usually ‘./fips’ is run from the root directory of a ‘fipsified’ C/C++ project, not from the fips directory

Get help

Run ‘./fips help’ to show available fips commands:

> ./fips help
fips: the high-level, multi-platform build system wrapper

fips build
fips build [config]
   perform a build for current or named config
> _

You can also show help for a single command:

> ./fips help diag
fips diag
fips diag all
fips diag fips
fips diag tools
fips diag configs
fips diag imports
    run diagnostics and check for errors
> _

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.

> ./fips diag tools
=== tools:
git:	found
cmake:	found
ccmake:	found
make:	found
ninja:	OPTIONAL, NOT FOUND (required for building '*-ninja-*' configs)
xcodebuild:	found
java:	found
ant:	found
python2:	found
> _

NOTE that some tools are optional and only required for specific build configurations