Skip to content
Snippets Groups Projects
  1. Oct 17, 2016
  2. Oct 14, 2016
  3. Oct 13, 2016
  4. Oct 11, 2016
  5. Oct 10, 2016
  6. Oct 08, 2016
  7. Oct 07, 2016
  8. Oct 06, 2016
    • Brad King's avatar
      Merge branch 'android-ndk-r13' into release · ffff5c17
      Brad King authored
      ffff5c17
    • Brad King's avatar
      Android: Update libc++ include directories for NDK r13 · 0c3a0477
      Brad King authored
      The Android NDK r13 moved the libc++ include directories.
      
      Closes: #16346
      0c3a0477
    • Brad King's avatar
      Android: Suppress -Wattributes warnings in test case builds · ebef3632
      Brad King authored
      We use `-Werror` in the Android test builds to make sure there are
      no warnings that we care about (e.g. unused flags).  However, the
      NDK r13 tools produce a warning about their own builtins:
      
      ```
      <built-in>: In function 'float abs(float)':
      <built-in>: warning: conflicts with previous declaration here [-Wattributes]
      ```
      
      Suppress this warning so that we can continue using `-Werror` but
      tolerate these warnings.
      ebef3632
    • Stephen Kelly's avatar
      cmGlobalGenerator: Add API to get settings from top-level cmMakefile · f59e8779
      Stephen Kelly authored
      At generate-time, definitions are sometimes read from a nearby cmMakefile,
      making the value directory-specific because they are read once per
      directory.  Often however, the intention is more
      often to create a 'global' setting, such that the user writes for
      example:
      
       set(CMAKE_IMPORT_LIBRARY_SUFFIX something)
      
      once at the top level of their project.
      
      Many of these are also set by internal platform files, such as
      CMAKE_EXTRA_LINK_EXTENSIONS.
      
      The set() definitions are not really suitable for 'global' settings
      because they can be different for each directory, and code consuming the
      settings must assume they are different for each directory, and read it
      freshly each time with new allocations.
      
      CMake has other variable types which are global in scope, such as global
      properties, and cache variables.  These are less convenient to populate
      for users, so establish a convention and API using the value as it is at
      the end of the top-level CMakeLists file.
      f59e8779
    • Brad King's avatar
      dcf9729e
    • Domen Vrankar's avatar
      CPack/RPM debuginfo package without binaries · f53b01ff
      Domen Vrankar authored and Brad King's avatar Brad King committed
      Handle case when a component doesn't contain
      any debuginfo symbols.
      f53b01ff
Loading