Go to file
Davis King cc70a8e0fb Merged in Patrick Snape's patch that allows the python bindings to
be built without GUI support.
2014-11-15 09:28:48 -05:00
dlib Fixed a compile time error that prevented auto_threshold_image() from being 2014-11-15 09:15:36 -05:00
docs Fixed another forum link 2014-10-29 07:04:15 -04:00
examples Changed example to avoid tying a stream to itself since some iostream libraries 2014-09-30 19:21:38 -04:00
python_examples Updated the Python API, train_simple_object_detector() so you can call it 2014-08-12 19:47:41 -04:00
tools Merged in Patrick Snape's patch that allows the python bindings to 2014-11-15 09:28:48 -05:00
.gitignore Added .o to .gitignore file 2014-02-18 09:35:08 -05:00
.hgignore updated ignore file 2014-03-08 21:41:59 -05:00
.hgtags Added tag v18.11 for changeset dd8e950033d5 2014-10-14 05:12:28 -04:00
README.txt updated readme 2014-08-19 19:11:24 -04:00

README.txt


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.