1. 03 Jul, 2017 1 commit
  2. 26 Jun, 2017 1 commit
  3. 21 Jun, 2017 2 commits
  4. 20 Jun, 2017 1 commit
  5. 11 Jun, 2017 1 commit
  6. 08 Jun, 2017 1 commit
  7. 30 May, 2017 1 commit
  8. 19 May, 2017 1 commit
  9. 20 Apr, 2017 1 commit
  10. 15 Apr, 2017 1 commit
  11. 24 Mar, 2017 1 commit
  12. 23 Mar, 2017 1 commit
  13. 21 Feb, 2017 1 commit
  14. 13 Feb, 2017 1 commit
  15. 12 Feb, 2017 1 commit
    • Gabriel B. Nunes's avatar
      Work around CMake bug that mangles install dir · 88e54ca1
      Gabriel B. Nunes authored
      CMake has a long-standing bug/feature (see [here](https://cmake.org/pipermail/cmake/2015-March/060204.html) and reply [here](https://cmake.org/pipermail/cmake/2015-March/060209.html)) which can mangle certain path variables by attempting to make them into relative paths if you try to set them with CACHE PATH.
      
      Say you have your OpenCV download at `/path/on/my/computer/to/opencv/`. What actually happens is that if you try to set this variable by invoking CMAKE with `-DCMAKE_INSTALL_PREFIX=/my/desired/install/path`, what you end up is *not* `/usr/local/` and *not* `my/desired/install/path`, but instead, this monstrosity: `/path/on/my/computer/to/opencv/src/OpenCV-build//my/desired/install/path`.
      
      That is, CMake attempts, for some reason, to turn the path that you passed into a path relative to `${CMAKE_BINARY_DIR}`. See the links I posted above: this is a known (and apparently unfixable) issue with CMake.
      
      In OpenCV's case, among other potential issues, this leads to broken paths in `opencv_tests_config.hpp`, which can break the build or cause bizarre behaviour.
      
      The fix for this issue, as stated in my links above, is to test that the variable hasn't been set yet with an `if(NOT DEFINED ...)` before attempting to set it. This is what I've implemented here. I admit I don't know enough about OpenCV's internals to know whether you *really* need to force the install to be in `/usr/local`, but as it stands right now you get *neither* a clean `/usr/local` path *nor* a customized `/my/desired/install/path`, but a broken mess. This change at least allows the user to customize their install directory.
      
      In the meantime, there's a workaround for this, by explicitly defining the variable as a path with `-DCMAKE_INSTALL_PREFIX:PATH=my/desired/install/path`. But if this change can save anyone else the hours of headaches that I had today, I'll be happy.
      88e54ca1
  16. 09 Feb, 2017 1 commit
  17. 31 Jan, 2017 1 commit
  18. 23 Jan, 2017 1 commit
  19. 22 Dec, 2016 1 commit
  20. 13 Dec, 2016 1 commit
  21. 01 Dec, 2016 1 commit
  22. 29 Nov, 2016 1 commit
  23. 27 Nov, 2016 4 commits
  24. 23 Nov, 2016 1 commit
  25. 18 Nov, 2016 1 commit
  26. 10 Nov, 2016 1 commit
  27. 22 Oct, 2016 1 commit
    • Arek's avatar
      Merge pull request #7518 from ArkadiuszRaj:aravis-buffer-status · e77bc24b
      Arek authored
      Aravis several updates
      
      * Fix adressing camera with id=0
      
      * Aravis buffer property control & status added
      
      * Modify of autoexposure algorith, ream frame ID from aravis + new properites
      
      * Change of macro name
      
      * VideoCapture now returns no frame on camera disconnecion
      
      * Allow aravis-0.4 usage, proper camera object release.
      e77bc24b
  28. 07 Oct, 2016 1 commit
  29. 04 Oct, 2016 1 commit
  30. 19 Sep, 2016 1 commit
  31. 09 Sep, 2016 1 commit
  32. 25 Aug, 2016 1 commit
  33. 23 Aug, 2016 1 commit
  34. 17 Aug, 2016 1 commit
  35. 10 Aug, 2016 1 commit
  36. 04 Aug, 2016 1 commit