1. 19 Apr, 2019 1 commit
    • Brad King's avatar
      VS: Provide the default platform name to project code · db02be85
      Brad King authored
      The value of `CMAKE_VS_PLATFORM_NAME` is computed by Visual Studio
      generators based on `CMAKE_GENERATOR_PLATFORM` or some default.
      Prior to the VS 2019 generator, the default was always `Win32`.
      However, for the `Visual Studio 16 2019` generator, the default is
      based on the host platform.
      Store the default in a new `CMAKE_VS_PLATFORM_NAME_DEFAULT` variable for
      use by project code.  This is particularly useful in toolchain files
      because they are allowed to set `CMAKE_GENERATOR_PLATFORM` and so
      `CMAKE_VS_PLATFORM_NAME` is not yet known.  Of course the toolchain file
      author knows whether it will set `CMAKE_GENERATOR_PLATFORM`, and if not
      then `CMAKE_VS_PLATFORM_NAME_DEFAULT` provides the platform name that
      will be used.
      Fixes: #19177
  2. 04 Apr, 2019 1 commit
  3. 29 Mar, 2019 1 commit
    • Fred Baksik's avatar
      GHS: Print status message regarding GHS_OS_DIR · 266dadf8
      Fred Baksik authored
      -- Rename platform script so it runs before initial try_compile() in
         project() command.
      -- Fix incorrect variable name GHS_OS_DIR_OPTION
      -- Remove unnecessary ".*" from REGEX expression for GHS_CANDIDATE_OS_DIRS
      -- Forward GHS_OS_DIR_OPTION to try_compile() and preserve trailing
         whitespace of the variable.
  4. 21 Mar, 2019 1 commit
  5. 16 Feb, 2019 1 commit
  6. 08 Feb, 2019 1 commit
  7. 06 Feb, 2019 1 commit
  8. 28 Jan, 2019 2 commits
  9. 16 Jan, 2019 4 commits
    • Fred Baksik's avatar
      GHS: try_compile() now uses GHS platform variables · 436cc5e9
      Fred Baksik authored
      -- Forward GHS platform variables to try_compile()
         CMAKE_TRY_COMPILE_PLATFORM_VARIABLES only worked for source signature try_compile()
      -- Update tests to no longer add GHS platform variables to try_compile()
      -- Avoid linker error in GhsMulti/GhsMultiCompilerOptions/CMakeLists.txt by building library
    • Fred Baksik's avatar
      GHS: Fix toolset selection · 4a1ec0de
      Fred Baksik authored
      -- Allow -T to accept full or partial paths
      -- Use "C:/ghs" if GHS_TOOLSET_ROOT is empty string
      -- Put more information in error messages
    • Fred Baksik's avatar
      GHS: Integrity Application updates · 0c9e47d7
      Fred Baksik authored
      -- Check the property "ghs_integrity_app" on executables to set [INTEGRITY Application]
         If the property is not set then check if an integrate file is one of the source files (.int file).
         Dynamic Downloads that do not have an integrate file can use this property along with setting
         the compiler flag "-dynamic".
      -- Remove parsing for -dynamic flag; it is only used to print a comment
         The MULTI GUI will show if it is a Monolith or Dynamic Download application
      -- Use project references to specify which executables are part of the Integrity Application
         Usually Implicit Dependency Analysis will ensure that executable targets
         become part of the application.  This does not work for Dynamic Download without integrate files.
         Use `add_dependencies(dd vas)` to mark that the vas target is part of dd target.
      -- Update file locations in the Integrate files.
    • Fred Baksik's avatar
      GHS: Place build system outputs per target output directives · 2ed2d6b4
      Fred Baksik authored
      -- Set output and object file locations
      -- Suffixes are no longer being forced but will now follow the target properties
         By default GHS tools have no suffix for executable files so
         CMAKE_EXECUTABLE_SUFFIX was changed to meet this behavior
      -- Remove #if 0 blocked out code; it has been replaced.
         Forcing the -relprog option has been removed from non-kernel executable targets.
         The default value of this option (if it is even available) is determined by the
         tool-chain for the specified target and platform (Some tool-chains default to
         -locatedprogram).  The use of -relprog can have unexpected results as it cannot
         always produce a fully relocated executable.
      -- Clarify use of CMAKE_BUILD_TYPE to control build configuration
  10. 11 Jan, 2019 1 commit
    • Brad King's avatar
      VS: Add Visual Studio 16 2019 generator · 57e48f16
      Brad King authored
      Add this generator *without* support for specifying the target
      architecture in the generator name.  cmake-gui will be taught
      to provide a field for this, and command-line builds can use -A.
      Also, teach this generator to select a default target architecture
      based on the host architecture.
      Fixes: #18689
      Inspired-by: Egor Pugin's avatarEgor Pugin <egor.pugin@gmail.com>
  11. 10 Jan, 2019 1 commit
  12. 25 Sep, 2018 1 commit
  13. 09 Aug, 2018 1 commit
  14. 11 Jul, 2018 5 commits
    • Fred Baksik's avatar
      GHS: Update default BSP name · 281c6010
      Fred Baksik authored
      -- Use default value of sim<arch> if not user defined
      -- Also no reason to trim quotes or changes slashes; it is just a name not a path
    • Fred Baksik's avatar
      GHS: Update setting default OS location for Integrity platforms · 01c98c6c
      Fred Baksik authored
      -- Update how the latest OS is determined; scan the location GHS_OS_ROOT and sort it
         No longer use registry settings looking for installations
           The registry values are assigned in installation order for Green Hills tools not version order
         Filter out files from the list of directories (i.e if int1234.zip and int1234 are both in root folder)
    • Fred Baksik's avatar
    • Fred Baksik's avatar
      GHS: Add platform selection support · f80692cf
      Fred Baksik authored
    • Fred Baksik's avatar
      GHS: Add toolset selection support · a37a4a00
      Fred Baksik authored
      -- Use the specified toolset located within GHS_TOOLSET_ROOT
      -- Update how the latest toolset is determined; scan the location GHS_TOOLSET_ROOT and sort it
         No longer use registry settings looking for installations
           The registry values are assigned in installation order for Green Hills tools not version order
      -- Update to use gbuild.exe from the proper toolset
      -- Clarify that CMAKE_MAKE_PROGRAM should not be set by user.
      -- Detect some toolset changes when regenerating project files
         This could occur if GHS_TOOLSET_ROOT was changed by user after the initial project generation
         This could occur if CMAKE_MAKE_PROGRAM was changed at the command line
      -- Use placeholder values for CMAKE_<LANG>_COMPILER
         The MULTI build system only uses gbuild to build a project
           gbuild uses the project file to determine which set of compilers to use based on target platform and architecture
           because compiler detection is skipped, placeholder values are used so that CMake does not complain
  15. 07 Jul, 2018 1 commit
    • Fred Baksik's avatar
      GHS: Support ARM, PPC, 86 architectures · 5d40d2b4
      Fred Baksik authored
      -- Update -A option to choose target architecture.
      -- Update commentary about which variables are used to control toolset and target settings
      -- Remove setting CMAKE_SYSTEM_PROCESSOR because the value is overwritten to be "" by subsequent CMAKE processing
  16. 02 Apr, 2018 1 commit
  17. 24 Jan, 2018 1 commit
    • Alexander Neundorf's avatar
      Generators: remove KDevelop3 generator · 9198e6a2
      Alexander Neundorf authored
      The last KDevelop3 release was many years ago, in 2008 I think.
      I haven't seen or read about anybody using KDevelop 3 since a
      long time, so I think it can safely be removed from CMake.
      KDevelop 4 (first released in 2010) has its own proper CMake
      support now, independent from this generator.
  18. 19 Oct, 2017 1 commit
    • Brad King's avatar
      VS: Select and save a VS 2017 instance persistently · 9ffb3538
      Brad King authored
      Visual Studio 2017 supports multiple instances installed on a single
      machine.  We use the Visual Studio Installer tool to enumerate instances
      and select one.  Once we select an instance for a given build tree, save
      the result in `CMAKE_GENERATOR_INSTANCE` so we can re-configure the tree
      with the same instance on future re-runs of CMake.
      Fixes: #17268
  19. 14 Sep, 2017 1 commit
    • Sagrer's avatar
      CodeBlocks: add option to exclude external files · fb19b778
      Sagrer authored
      Add variable `CMAKE_CODEBLOCKS_EXCLUDE_EXTERNAL_FILES` to optionally
      exclude files from outside the project root from the project file
      written by the CodeBlocks extra generator.  This optionally restores
      logic that had been removed by commit v2.8.3~40^2 (CodeBlocks Generator:
      Do not omit files in the project file listing, 2010-10-05) in response
      to QTCREATORBUG-2250.
      Issue: #12110
      Fixes: #17188
  20. 10 Jul, 2017 1 commit
  21. 22 Apr, 2017 1 commit
  22. 21 Apr, 2017 1 commit
  23. 19 Apr, 2017 1 commit
  24. 13 Mar, 2017 1 commit
  25. 10 Jan, 2017 1 commit
  26. 29 Nov, 2016 1 commit
  27. 14 Oct, 2016 1 commit
    • Brad King's avatar
      VS: Provide an option to use x64 host tools · d079e71c
      Brad King authored
      Visual Studio provides toolchains that are themselves built for 32-bit
      or 64-bit host architectures.  By default it uses the 32-bit tools, but
      it can be told to prefer the 64-bit tools on 64-bit hosts.  Extend the
      `CMAKE_GENERATOR_TOOLSET` specification to provide a way to request
      use of the 64-bit host tools.
      Closes: #15622
  28. 13 Oct, 2016 1 commit
  29. 30 Sep, 2016 1 commit
  30. 26 Sep, 2016 1 commit
  31. 22 Sep, 2016 1 commit
  32. 07 Sep, 2016 1 commit
    • Brad King's avatar
      VS15: Add Visual Studio 15 generator · bdc679a8
      Brad King authored
      Call the generator "Visual Studio 15" without any year because the
      preview version of VS 15 does not provide a year in the product name.
      Copy cmGlobalVisualStudio14Generator to cmGlobalVisualStudio15Generator
      and update version numbers accordingly.  Add the VS15 enumeration value.
      Note that we do not need to add a MSVC15 variable or v150 toolset
      because Visual Studio 15 comes with an updated version of the v140
      toolset and remains ABI-compatible.
      Teach tests VSExternalInclude, RunCMake.GeneratorPlatform, and
      RunCMake.GeneratorToolset to treat VS 15 as they do VS 10-14.
      Closes: #16143