Go to file
Davis King cd64c51800 Made cmake script work a little better in projects that involve a lot of
subdirectories and create a lot of executables.
2015-02-16 17:14:34 -05:00
dlib Made cmake script work a little better in projects that involve a lot of 2015-02-16 17:14:34 -05:00
docs merged 2015-02-14 18:02:58 -05:00
examples Added spectral_cluster() example 2015-02-11 07:55:42 -05:00
python_examples clarified example 2015-01-03 23:33:46 -05:00
tools Fixed the python doc string so that it's correct relative to the python 2015-01-03 23:26:28 -05:00
.gitignore Update the gitignore to ignore vim and idea 2014-12-10 17:45:51 +00:00
.hgignore updated ignore file 2014-03-08 21:41:59 -05:00
.hgtags Added tag v18.13 for changeset 67c3ad208aae 2015-02-03 18:55:24 -05:00
README.txt updated readme 2014-08-19 19:11:24 -04:00


See http://dlib.net for the main project documentation.



COMPILING DLIB EXAMPLE PROGRAMS
   Go into the examples folder and type:
   mkdir build; cd build; cmake .. ; cmake --build .

   That will build all the examples.  There is nothing to install when using
   dlib.  It's just a folder of source files.  

RUNNING THE UNIT TEST SUITE
   Type the following to compile and run the dlib unit test suite:
       cd dlib/test
       mkdir build
       cd build
       cmake ..
       cmake --build . --config Release
       ./dtest --runall

   Note that on windows your compiler might put the test executable in a
   subfolder called Release.  If that's the case then you have to go to that
   folder before running the test.

DOCUMENTATION
   The source control repository doesn't contain finished documentation.  The
   stuff in the docs folder is just a bunch of scripts and xml files used to
   generate the documentation.  There is a readme in docs/README.txt which
   discusses how to do this.  However, unless you are trying to modify the
   documentation, you should just download a copy from http://dlib.net.