Tree [26c0b6] default tip /

File Date Author Commit
dlib 1 day ago Davis King Davis King [4e3941] Fixed policy setting so it works on old cmakes
docs 1 day ago Davis King Davis King [26c0b6] Created release v18.12
examples 2014-12-09 Davis King Davis King [1575a4] Added an example for svm_c_trainer.
python_examples 2014-08-12 Davis King Davis King [cd0834] Updated the Python API, train_simple_object_det...
tools 2014-12-06 Davis King Davis King [abaa99] more cmake changes to avoid cmake warnings
.gitignore 2014-02-18 Davis E. King Davis E. King [e563dc] Added .o to .gitignore file
.hgignore 2014-03-09 Davis King Davis King [4dd804] updated ignore file
.hgtags 1 day ago Davis King Davis King [418337] Added tag v18.12 for changeset 4e3941b13ca8
README.txt 2014-08-19 Davis King Davis King [1501a0] updated readme

Read Me

See for the main project documentation.

   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.  

   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.

   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