1. 27 7月, 2017 1 次提交
  2. 21 7月, 2017 1 次提交
  3. 03 7月, 2017 1 次提交
  4. 26 6月, 2017 1 次提交
  5. 21 6月, 2017 2 次提交
  6. 20 6月, 2017 1 次提交
  7. 11 6月, 2017 1 次提交
  8. 08 6月, 2017 1 次提交
  9. 30 5月, 2017 1 次提交
  10. 19 5月, 2017 1 次提交
  11. 21 4月, 2017 1 次提交
  12. 15 4月, 2017 1 次提交
  13. 24 3月, 2017 1 次提交
  14. 23 3月, 2017 1 次提交
  15. 22 2月, 2017 1 次提交
  16. 14 2月, 2017 1 次提交
  17. 12 2月, 2017 1 次提交
    • G
      Work around CMake bug that mangles install dir · 88e54ca1
      Gabriel B. Nunes 提交于
      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
  18. 10 2月, 2017 1 次提交
  19. 31 1月, 2017 1 次提交
  20. 23 1月, 2017 1 次提交
  21. 23 12月, 2016 1 次提交
  22. 14 12月, 2016 1 次提交
  23. 02 12月, 2016 1 次提交
  24. 30 11月, 2016 1 次提交
  25. 28 11月, 2016 4 次提交
  26. 23 11月, 2016 1 次提交
  27. 18 11月, 2016 1 次提交
  28. 10 11月, 2016 1 次提交
  29. 23 10月, 2016 1 次提交
    • A
      Merge pull request #7518 from ArkadiuszRaj:aravis-buffer-status · e77bc24b
      Arek 提交于
      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
  30. 08 10月, 2016 1 次提交
  31. 04 10月, 2016 1 次提交
  32. 20 9月, 2016 1 次提交
  33. 09 9月, 2016 1 次提交
  34. 25 8月, 2016 1 次提交
  35. 24 8月, 2016 1 次提交
  36. 17 8月, 2016 1 次提交