Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo


Tree [f05da5] 0.15-almost /

File Date Author Commit
benchmarks 2011-10-19 Lars Kotthoff Lars Kotthoff [515d95] update for python 3
cmake-modules 2012-11-29 Chris Jefferson Chris Jefferson [85bcde] Improve handling of empty constraints
docs 2012-12-10 Chris Jefferson Chris Jefferson [f89da8] Prepare for 0.15 release
generators 2011-10-20 Lars Kotthoff Lars Kotthoff [159d31] more updates for python 3
mini-scripts 2012-12-05 Chris Jefferson Chris Jefferson [3a718a] More fixes and test improvements for gaceq
minion 2012-12-12 Chris Jefferson Chris Jefferson [10805d] Enable checking short tuples for haggisgac, and...
nauty24b7 2012-10-16 Chris Jefferson Chris Jefferson [4fc4a2] Clean up nauty code which violates GPL
release-scripts 2009-05-05 larsko larsko [1e806a] adding shell opt for extended glob expansion
summer_school unknown
sym_test unknown
test_instances 2012-12-12 Chris Jefferson Chris Jefferson [f05da5] Add new tests
visualisation 2011-02-15 Lars Kotthoff Lars Kotthoff [abe2b4] fixing cabal file and some legacy stuff
CMakeLists.txt 2012-11-22 Chris Jefferson Chris Jefferson [bc5e46] Fix mac release
HOW-TO-RELEASE 2012-07-27 Peter Nightingale Peter Nightingale [0ffab6] update howto release
LICENSE.txt unknown
README 2009-05-27 Peter Nightingale Peter Nightingale [9a780b] Merge branch 'master' of https://pn@keith.cs.st...
build-all-windows.bat unknown
build-all.sh unknown
experiment-notes 2010-11-22 Peter Nightingale Peter Nightingale [3cffcf] Merge branch 'flowconstraints'
regression.filelist unknown

Read Me

Welcome to the Minion source!

The minimum verson of CMake you'll need is 2.4.7. You'll also need Boost (at
least version 1.33).

First, create a directory to do the build in, e.g.

mkdir bin

Then change to that directory. Now run CMake to configure Minion:

cmake ..

This assumes that you've created the build directory in the Minion directory;
the argument to CMake is the directory that contains the Minion distribution.

This will look for the location of your compiler, and a few system libraries.
If you ever add additional constraints, or add or remove files, then
you should re-run cmake. The Makefile is generated by CMake; it is safe to
delete it.

After that, you can compile Minion by doing:

make minion

which should produce the binary "minion".

If you want to build the debug version, re-run cmake like

cmake -DDEBUG=1 ..

and then type

make minion

again. This should produce the "minion-debug" binary. The debug version is much
slower but has a large amount of internal checks. It should be used if you are
unsure / worried about the results Minion produces, or it crashes.

Note that CMake caches your configuration between runs, i.e. just running

cmake ..

after having built the debug version will again produce Makefiles for the debug
version. To turn debugging off, run

cmake -DDEBUG=0 ..

To test your Minion installation, you can use the "test-quick", "test", and
"test-slow" Makefile targets.

To clean all generated files, simply delete the directory you did the build in.

the "docs" directory contains a full manual for Minion. 
The "benchmarks" directory contains a range of example programs.
The "generators" directory contains a number of generators, these are
in general poorly documented.