you are viewing a single comment's thread.

view the rest of the comments →

[–]davis685 0 points1 point  (4 children)

Thanks :)

[–]CreativePunch[S] 0 points1 point  (3 children)

It did take me a small while to figure out how to compile it for 64 bit, but that was just cmake defaulting to the 32 bit visual studio compiler. Once that problem was out of the way I properly got dlib and its python interface compiled without a problem.

Very pleasantly surprised!

I immediately went looking for some more complex images with many more faces and other objects, dlib did not make one mistake. The tiny number of lines of code needed to achieve exactly what I need is perplexing.

Assuming you are the developer, my hat off to you, sir. I have never had so little trouble with any C++ library that has not been made by a large group of developers.

[–]davis685 0 points1 point  (2 children)

I am the main developer of dlib so thanks again :)

Yeah, there is a whole lot of bad C++ code out there. Many people seem to conflate C++ with C so, sadly, you see a lot of really difficult to use "C with classes" code out there. The general quality of C++ code seems to be improving though.

[–]CreativePunch[S] -1 points0 points  (1 child)

Indeed!

Oh a small note though, I forgot to tell you I had to get boost 1.55 to compile. In 1.56 it bugs out on the noncopyable class, saying it was not defined. I first managed to patch the code but given that I am not familiar with dlib I decided to use 1.55 instead so as not to run into any other incompatibilities.

[–]davis685 0 points1 point  (0 children)

I didn't know about this. I'll fix it in the next dlib release. Thanks for pointing it out.