• Add back "CMake: New Project" command due to popular demand

• Use CMake's File API
• Integration with Terminus
• Integration with GDB and LLDB debuggers

• Remove deprecated server functionality.
  It was an interesting ride but at the end of the day I don't think it was
  the right kind of API for cmake.

• Use the new "file API", requires cmake 3.15 or newer.
  OSX users can use brew upgrade cmake. Windows users can point-and-click
  to a new cmake binary, Linux users can use their package manager to update
  cmake. Ubuntu 19 users are unfortunately stuck with cmake 3.14 so you'll
  have to upgrade manually.

• Remove "NMake Makefiles" support. I don't think many people used this.
  If you really need this, consider contributing code at
  github.com/rwols/cmakebuilder.

• You can now provide an exact visual studio generator on windows. So for
  instance, "Visual Studio 16 2019" or "Visual Studio 15 2017". These are also
  the only supported ones at the moment. But that is because of the next
  bullet point.

• Fix up handling of vcvarsall.bat. Because the location of vcvarsall.bat,
  as well as the method of finding the file has changed significantly since
  VS2017, I only provide support for VS2017 and up. If you really need support
  for VS2015 and older, consider contributing code.

• We now generate a SublimeText build system in a much more compact way,
  using custom target commands.

• Terminus integration. The "Terminus" plugin is a plugin that allows you to
  reliably run a terminal from within SublimeText. CMakeBuilder uses the
  terminus_open command to run/debug executables from within SublimeText.
  This is exposed as just another build variant with a "Run:" prefix.

• Fix missing encoding attribute for Sublime Text builds 3153 and higher.
• The "TARGET" notification in the status bar now displays once you configured.
• Present a list of targets once configured succesfully.
• Better diagnostic message when trying to build a cmake target that fails.
• Account for protocol version 1.1.
• The lowest ST build that I'm willing to support is probably going to be 3153,
  due to how Default.exec.ProcessListener was changed a bit in that version.
  Most people will have a sufficiently high version once I release this on
  Package Control I believe.

• Add cmake experimental server functionality for cmake >= 3.7

• Integer parse fix for visual studio generator
• Add new item to "Preferences" menu: "Report an Issue"

• Improved the diagnosis output somewhat by using the "tabulate" library.
• Removed the migrator logic. I hope everybody migrated their cmake dicts
  to the settings dict.
• Improved "auto configure" somewhat.
• Removed CMakeCache syntax, it's in the CMake package now.
  Make sure you have the "CMake" package!

It's finally here! The moment you've all been waiting for! Version 1.0!
All kidding aside, I consider the plugin in a mature state now, so let's
call this version 1.0.

What will the future hold for this plugin? Since cmake version 3.7, there
has been "server" functionality in the cmake executable. You can check if
your cmake has a server mode by running "cmake -E capabilities".

The server mode of cmake can configure the project, list all targets,
and report on various progress updates. This is basically what we've been
doing with this plugin "manually". The roadmap for version 2.0 of this
plugin will be to integrate this server functionality with Sublime Text
to give us a smoother cmake experience.

• As always it seems, a tiny patch for tradition.
  Fix typo in message dialog.

• Add "Edit Cache" command. This will simply open the CMakeCache.txt file.
  Try it out!

• Add "New Project" command. This will create a template project for you.
  Try it out!

• Made variable names in the CMakeCache.txt syntax (locally) indexable.
  What this means in practice is that you can "goto anything", type an
  "@" character and all of the variables will show up if you're looking
  at a cache file.

• Remove deprecated command "CMake Clear Cache And Configure".

• Allow this package to be a zip file. What this means is that you'll
  no longer find CMakeBuilder in the Packages directory, but in the
  Installed Packages directory. If you still want to hack on CMakeBuilder,
  consider cloning this package via GitHub.

• Made the decision to put the "cmake" dict in the "settings" dict of the
  project file. This allows the plugin to react to changes in a more
  dynamic way. I've written a small migrator command to automate the
  arduous process of moving the dict yourself. This command will go away
  in version 1.0.0.

• Set "configure_on_save" to "true" by default.

• Various improvements to handling settings.

• "configure_on_save" also reacts to changes to the cmake dict now.

• Set "write_build_targets_after_successful_configure" to "true" by
  default. It's mature enough.

• Add Ninja generator for Windows.

  For Windows users: to enable Ninja, download a binary from

  github.com/ninja-build/ninja/releases
  

  put it somewhere like C:\Ninja, and add that to your %PATH%.

• Refactor vcvarsall.bat handling for Windows.

• Improve Visual Studio output panel syntax highlighting

• Improve CMakeCache.txt syntax highlighting

• Improve Ninja output panel syntax highlighting for OSX and Linux

• Improve Unix Makefiles output panel syntax highlighting for OSX and
  Linux

• Allow Visual Studio to compile for 64 bit (see below).

• New item in cmake dictionary: "env"

  This is a dict of key-value pairs of strings. Place your environment
  variables at configure time in here. For example, to select clang as
  your compiler if you have gcc set as default, you can use

  "env": { "CC": "clang", "CXX": "clang++" }
  

• New item in cmake dictionary: "target_architecture"

  This is only applicable for Windows users. "target_architecture" must be
  a string and can be one of "x86", "amd64" or "arm".

• New item in cmake dictionary: "visual_studio_versions"

  This is only applicable for Windows users. "visual_studio_versions" must
  be a list of numbers specifying the preferred versions of Visual Studio,
  provided that "Visual Studio" is the chosen generator. The priority is
  specified by the order that the numbers appear in the list. For example,
  if the list is

  "visual_studio_versions": [ 15, 14 ]
  

  then CMakeBuilder will first attempt to configure the project for Visual
  Studio 15 2017, and if that's not found, then it will attempt to
  configure for Visual Studio 14 2015. Moreover, if "target_architecture"
  is set, then it will append a further architecture argument to the cmake
  generator invocation. For instance, if "target_architecture" is set to
  "amd64" and "visual_studio_versions" is set to [ 15 ], the generator
  invocation will be "Visual Studio 15 2017 Win64".