Open Source Computer Vision Library
Go to file
Stefan Brüns 0a45b8c478 Handle absolute OPENCV_INCLUDE_INSTALL_PATH correctly
In case OPENCV_INCLUDE_INSTALL_PATH is absolute (i.e. starts with a "/"),
the path ends up with a double "/".

While this is mostly equivalent to a single slash, it may have a nasty
side effect when:
- OpenCV_INSTALL_PATH is empty
- OPENCV_INCLUDE_INSTALL_PATH is "/usr/include"
- the calling build script uses "-isystem" to specify the path to the
  headers of dependencies (to avoid warnings)

Specifying "-isystem /usr/include" breaks the path ordering, and GCC can
no longer find its "stdlib.h", thus CMake filters such statements.
Unfortunately it fails to do so when using "//usr/include".
2019-06-28 15:44:45 +02:00
.github migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
3rdparty ffmpeg: update 3.4.6 2019-06-12 16:54:47 +00:00
apps Update haarfeatures.cpp 2019-05-13 16:41:03 +03:00
cmake Handle absolute OPENCV_INCLUDE_INSTALL_PATH correctly 2019-06-28 15:44:45 +02:00
data Some mist. typo fixes 2018-02-07 06:59:15 -05:00
doc pre: OpenCV 3.4.7 (version++) 2019-06-21 16:57:17 +03:00
include add missing DNN header to opencv2/opencv.hpp 2018-02-15 15:59:14 +01:00
modules dnn: adjust compilation options 2019-06-27 17:37:31 +03:00
platforms [#14873] Fix code signing issue in Try Compile script 2019-06-25 10:02:54 +02:00
samples Remove extra ")" 2019-06-26 17:27:56 +03:00
.editorconfig add .editorconfig 2018-10-11 17:57:51 +00:00
.gitattributes cmake: generate and install ffmpeg-download.ps1 2018-06-09 13:19:48 +03:00
.gitignore git: .gitignore update 2017-11-07 17:24:48 +03:00
CMakeLists.txt cmake: typo in hook name 2019-06-14 19:07:54 +03:00
CONTRIBUTING.md migration: github.com/opencv/opencv 2016-07-12 12:51:12 +03:00
LICENSE copyright: 2019 2019-01-02 01:18:04 +00:00
README.md Improve README (#9243) 2017-09-13 17:58:34 +03:00

OpenCV: Open Source Computer Vision Library

Resources

Contributing

Please read the contribution guidelines before starting work on a pull request.

Summary of the guidelines:

  • One pull request per issue;
  • Choose the right base branch;
  • Include tests and documentation;
  • Clean up "oops" commits before submitting;
  • Follow the coding style guide.