1. 18 Apr, 2015 1 commit
  2. 13 Apr, 2015 1 commit
  3. 07 Apr, 2015 5 commits
  4. 05 Apr, 2015 1 commit
  5. 03 Apr, 2015 6 commits
  6. 02 Apr, 2015 1 commit
  7. 01 Apr, 2015 3 commits
  8. 31 Mar, 2015 1 commit
    • Roman Donchenko's avatar
      Use imported targets for linking to CUDA · 6e121b2e
      Roman Donchenko authored
      This retains the desirable quality of not including paths to CUDA libraries
      from the build system into the config files, and has two major advantages:
      
      * It removes the need to use link_directories, which doesn't guarantee that
        the libraries from the supplied directory will be used (there may be
        libraries with the same names earlier in the search path).
      
      * It removes the need to put -L entries into OPENCV_LINKER_LIBS. This variable
        is used with target_link_libraries, where such entries are treated as linker
        flags, so doing this is unportable. I remove the support for -L entries
        from OpenCVGenPkgconfig.cmake, as well, to discourage adding them in the
        future.
      6e121b2e
  9. 30 Mar, 2015 3 commits
  10. 29 Mar, 2015 1 commit
  11. 26 Mar, 2015 1 commit
  12. 25 Mar, 2015 4 commits
  13. 24 Mar, 2015 2 commits
    • Alexander Nitsch's avatar
      d4306647
    • Tim D. Smith's avatar
      Don't explicitly link Python on OS X · d057828e
      Tim D. Smith authored
      Explicitly linking to a Python framework on OS X prevents modules from
      being built against one python (i.e. system python) and imported from
      another (i.e. Homebrew python); the interpreter segfaults if there's a
      linkage to a foreign python. Building the module with `-undefined
      dynamic_lookup` instead of an explicit link allows the symbols to be
      resolved at load time from a compatible python.
      d057828e
  14. 23 Mar, 2015 1 commit
  15. 20 Mar, 2015 5 commits
  16. 19 Mar, 2015 3 commits
  17. 18 Mar, 2015 1 commit