Skip to content

Releases: rwols/CMakeBuilder

0.9.2

30 Apr 12:01
Compare
Choose a tag to compare
  • Revert NMake fixes; breaks for Windows 10 VS2015 for some reason.

0.9.1

30 Apr 09:56
Compare
Choose a tag to compare
  • Fix NMake not working on x64 Windows 7 (thanks, paulfd)
  • Fix NMake file regex

0.9.0

08 Apr 09:48
Compare
Choose a tag to compare
  • Fix write_build_targets overwriting all of your other build systems.

    Previously, all other build systems that were present got overwritten.
    This is no longer the case; all your custom-written build systems
    remain intact.

    !!! IMPORTANT !!!

    The new behaviour of write_build_targets is such that
    it will probably create a new build system alongside your old one.
    It's best to remove your old build system and generate a new one. The
    new build system will update itself and not overwrite other build
    build systems.

  • Allow custom name for your new build system.

    This is realized as a new setting called

    "generated_name_for_build_system"

    By default, its value is "${project_base_name} (${platform})". When
    combined with the above fix, this allows multiple build systems (per
    platform) to live inside a single sublime project file. Thus, it should
    be possible to have a single cross-platform sublime project file now.

  • Remove deprecated commands.

    Use the settings, Luke!

  • Uniformize getting settings

    Every setting can be overridden in the "settings" dictionary of your
    sublime project file. For instance, if you want
    "silence_developer_warnings" to be off by default, but not for a
    particular project, you can do so in the settings of the project file.

  • Add a link to the README in the preferences like a pro.

0.8.0

22 Mar 14:57
Compare
Choose a tag to compare
  • Fix bug where if you didn't have the "command_line_overrides" key in the
    cmake dictionary you'd get an exception.

  • Add settings file (go to Preferences -> Package Settings -> CMakeBuilder)

  • The following settings are available as options in the settings file:

    • write_build_targets_after_successful_configure (boolean)
    • silence_developer_warnings (boolean)
    • always_clear_cache_before_configure (boolean)
    • configure_on_save (boolean)
    • ctest_command_line_args (string)

    Refer to the package settings for more details.

  • With the settings present, some commands are now obsolete. They are:

    • Configure (Silence Dev Warnings)
      You can set silence_developer_warnings to true in your settings
      file for the same effect.

    • Configure & Update Build System Targets
      You can set write_build_targets_after_successful_configure to true in
      your settings file for the same effect.

    • Run CTest (Verbose), Run CTest (Extra Verbose)
      You can set ctest_command_line_args to "--output-on-failure -VV".

    These three commands will dissapear in 0.9 (current version is 0.8).

  • Separate generators into platform-specific python packages.
    In the directory Packages/CMakeBuilder/Generators, we now have a Python
    file for each generator. That is, we define a one-to-one correspondence
    between pyfiles in those directories and platform-specific generators.

  • Add "Visual Studio" and "NMake Makefiles" generators for Windows.
    Yes, there's Windows support now. Hello, windows users! I haven't
    updated the package control channel yet, so they'll have to wait a bit
    longer. But the functionality is present.

  • Rewrite README.md for new users.

  • Add CONTRIBUTING.md file.

0.7.2

04 Mar 12:14
Compare
Choose a tag to compare
  • Add .no-sublime-package file in order to make sure that
    package control doesn't install the package in the
    "Installed Packages" folder screwing up the filename paths.

0.7.1

04 Mar 11:00
Compare
Choose a tag to compare
  • Fix wrong paths to syntax files

0.7.0

02 Mar 21:56
Compare
Choose a tag to compare

NEW features:

  • Diagnose command if you get stuck on what to do
  • Syntax highlighting for the CMakeCache.txt file
  • Syntax highlighting for the cmake output panel at the configuration step
  • Goto error/warning at the configuration step (press F4)

The supplied in-line message for the "goto error/warning" is kind of bonkers.
That's because Sublime Text 3 cannot handle multi-line error messages; see for
example 1 or 2. Anyway, that's the best I can do for now.

If you have an idea for improvement or if you find a bug please let me know at
github.com/rwols/CMakeBuilder/issues

0.6.1

24 Feb 19:54
Compare
Choose a tag to compare

0.6.0:

  • Added more strict checks for variable substitutions

    This should take care of subtle typo's in your cmake dictionary of your
    sublime-project file.
    (thanks, github.com/eugene-babichenko !)

  • Added new command (and variations): "Run CTest"

    If you have unit tests defined with the "add_test" command from CMake, you can
    run those tests by executing the commmand "Run CTest", either from the command
    palette or from the "Tools -> CMakeBuilder" menu at the top of the window.
    This command is only available when your build folder is populated with cmake-
    related files.

    See also:
    https://cmake.org/cmake/help/v3.0/command/add_test.html

0.6.1:

  • Fix wrong mnemonics
  • CTest outputs whatever the program outputs on test failure

If you have an idea for improvement or if you find a bug please let me know at
github.com/rwols/CMakeBuilder/issues

0.5.0

27 Jan 23:09
Compare
Choose a tag to compare
  • Added new commands:
    • "Clear Cache": Removes all cmake-related files
      (thanks, github.com/eugene-babichenko !)
    • "Clear Cache & Configure": Simply runs the commands "Clear Cache" and
      "Configure" one after the other. This command does NOT ask for confirmation
      for deleting the cmake-related cache files.
  • If a prerequisite for a command is not satisfied, the command will not be
    executable. For instance, if you're not in "project mode" and you don't have
    a "cmake" dictionary in your project file, the "Configure" command will just
    not show up in the Command Palette. Similarly, if the project has not yet
    been configured, you cannot write build targets to your project file.
  • All commands are now also in the "Tools" menu at the top of the screen.
  • If the generator is "make" (the default), then building the default ("all")
    target will now build with the max number of cores of your machine by default.

If you have an idea for improvement or if you find a bug please let me know at
github.com/rwols/CMakeBuilder/issues

0.4.0

20 Jan 21:50
Compare
Choose a tag to compare
  • Fixed a bug where if you didn't specify the generator, nothing would happen.
  • Improved regex for catching warnings and errors.