Go to file
2014-03-02 11:59:31 -05:00
dlib Made the add_python_module cmake file look in more folders for boost when compiled 2014-03-01 21:39:10 -05:00
docs updated docs 2014-03-02 09:57:17 -05:00
examples Fixed warning on visual studio. 2014-03-01 21:38:47 -05:00
python_examples Fixed incorrect comment. 2014-03-02 11:59:31 -05:00
tools Made the python object detection tools process color images 2014-03-02 11:19:06 -05:00
.hgignore added to ignore list 2014-03-02 11:18:23 -05:00
.hgtags Added tag v18.6 for changeset 6a929c3ad782 2014-01-13 16:12:29 -05:00
README.txt updated repo level readme file 2014-01-28 21:09:07 -05: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
       ./test --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.