Go to file
2014-03-09 13:38:44 -04:00
dlib A minor change to avoid a warning from visual studio. 2014-03-08 21:41:21 -05:00
docs fixed typo 2014-03-08 21:28:01 -05:00
examples Updated this example to use the scan_fhog_pyramid version of the object 2014-03-08 13:12:48 -05:00
python_examples changed python example so that running it without commands doesn't trigger a testing 2014-03-09 13:37:30 -04:00
tools Added epsilon to the python object detection training API. 2014-03-09 12:10:15 -04:00
.hgignore updated ignore file 2014-03-08 21:41:59 -05:00
.hgtags Added tag v18.7 for changeset 5a3fb1f81041 2014-03-09 13:38:44 -04: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.