GitLab

* Forward CMake environment flags to libjpeg tests

* Forward CMake environment flags to libpng tests

* Add test case that makes MMOD loss go negative with certain ignore-rect configuration

* Disregard duplicate truth boxes

* Minor optimization

* Remove possibly outdated comment

* Clarify the detection count test criterion a little

* Review fix

* Review fixes:
- for perf reasons, keep only the first rect for each truth idx
- fix warning message grammar

* dos2unix tell_visual_studio_to_use_static_runtime.cmake

* Add an option to force static runtime

* Clear truth_idxs between samples

* Move truth_idxs inside loop body after all

* Push to truth_idxs even when the box can't be detected; improve formatting

add loss_mean_squared_per_channel_and_pixel

* Hold on to the CUDA buffer - second try
see: https://github.com/davisking/dlib/pull/1855#discussion_r314666348

* Fix #1849 by calling device_global_buffer() unconditionally

* Added aarch64 to list of 64-bit architechtures

* Const-corrected declaration of ssyevr

When dlib is compiling, cmake will compare python architecture and target
architecture. So in cross-compiling case, it is irrevelant because host and
target architecture often differs. The main problem come from checking python
architecture on host and not on target.

Here is an error when compiling dlib from x86_64 to arm 32-bit target :
```
Python config failure: Python is 64-bit, chosen compiler is 32-bit
```

So :
- Skipping the comparation when cross-compiling is enabled.
Signed-off-by: Romain Naour <romain.naour@smile.fr>
Signed-off-by: Alexandre PAYEN <alexandre.payen@smile.fr>

Push all include and link options needed for dlib to pkg-config.  We do this by getting them from the same list cmake uses.

* Add point assignment test

* Fix setting points y coordinate changes x instead (issue #1794)

Apparently pytest is still sort of busted.

This reverts commit 5e63d015.

Add input_grayscale_image_pyramid

libjpeg not being able to open some types of jpeg file.