Skip to content

Releases: Swoffa/SublimeKickAssemblerC64

Version 1.3.6

26 Apr 11:14
Compare
Choose a tag to compare

Changes in version 1.3.6:

Version 1.3.5

18 Nov 11:21
Compare
Choose a tag to compare

Changes in version 1.3.5:

  • Fix: Make command now works again
    Also fixes non-working pre- and post build commands
    Issue #72 reported by @BacchusFLT
  • Fix: Correct default path to x64c
    Issue #68 reported by @anthonyjclarke
  • Fix: Create and empty bin-folder works correctly again

Version 1.3.4

08 Mar 09:45
Compare
Choose a tag to compare

Changes in version 1.3.4:

  • Fix: Using full paths for Vice (x64) commands,
    Since version 3.5 for macOS does not handle relative paths well.
    Issue #64 reported by John Cook (https://github.com/jcook793)
  • New feature: startup-file build annotion
    Put startup-file annotation on first line of a file to configure which file to compile for "startup commands".
    Has precedence over setting kickass_startup_file_path.
    // @kickass-build "startup-file": "filename.asm"
    Issue #57 reported by Pontus Berg (https://github.com/BacchusFLT)

Version 1.3.3

13 Aug 08:40
Compare
Choose a tag to compare

Changes in version 1.3.3:

  • Fix: Changed the default (Vice) executable path for run and debug, since Vice executable is now located in the bin sub folder. The old path also works.
    Issue #58 reported by Pontus Berg (https://github.com/BacchusFLT)

Note:
If you need to use any other executable path, just customize with settings kickass_run_path and/or kickass_debug_path.

Version 1.3.2

03 Jun 08:53
Compare
Choose a tag to compare

Changes in version 1.3.2:

  • Fix: Changed the default executable for run and debug, from x64 to x64sc.
    In Vice 3.4 x64 is no longer available, so x64sc is used instead.
    Several people reported this.

Note:
If you need to use x64, or any other executable, just customize with settings kickass_run_path and/or kickass_debug_path.

Version 1.3.1

14 Jan 11:42
Compare
Choose a tag to compare

New in version 1.3.1:

  • New feature: Segment support, file annotation to configure which file to start
    Put startup-file annotation on first line of startup file (replace filename.prg):
    // @kickass-build "file-to-run": "filename.prg"
    With Vice you can start files on D64-disks with syntax "diskFilename.d64:prgname" (lower case without prg-extension)
    If you use settings custom kickass_run_command_xx or kickass_debug_command_xx commands, you will need to update them to use this feature, since the way to describe the prg-file has changed
    Issue #33 reported by Pontus Berg (https://github.com/BacchusFLT)

Version 1.3.0

21 Nov 11:23
Compare
Choose a tag to compare

New in version 1.3.0:

  • New feature: Integrating the KickAss Tooltips pluign
    Shows documentation when hovering over opcodes, vic-registers, sid-registers and some kick assembler directives.
    More documentation to come.
    Thanks to @brushesm and @ogt2 for this.
  • New feature: Default commands for C64Debugger
    Use of C64Debugger thru the kickass_run_path or kickass_debug_path settings
    is now detected and a custom command is used to start C64Debugger.
    The command will use symbols and breakpoints (4.x breakpoints) from Kick Assembler, see note below.
    Thanks to @arekbr for suggestion and to @BroneCk for help implementing
  • New setting kickass_env to add environment variables when building
    These variables has precedence over other environment variables with the same names.
    Mostly useful for prebuild, postbuild and make commands
    Suggested by @og2t
    Details: #22
  • A warnig is now shown if settings cannot be loaded when a build is requested, asking the user to restart Sublime.
    This should avoid some strange errors after updating, or switching between cloned and package control install modes.
  • New settings for detailed customization of compile, run and debug commands:
    kickass_run_command_x64
    kickass_debug_command_x64
    kickass_debug_command_c64debugger
    kickass_run_command_c64debugger
    kickass_compile_args
    kickass_compile_debug_additional_args
    Hopefully I will write a more detailed blog post about this later, at https://goatpower.org/
    Thanks to @arekbr for suggestion and to @BroneCk for help implementing
  • Verified basic Kick Assembler 5 support (Kick Assembler 4.x still supported)
    Both old ( break() ) and new ( .break ) breakpoints can be used.
    Using the default segment works, better support for multi segment things will be added later.
  • Minor bug fixes and improvements

Note:
It is possible to use the new dbg-files created by Kick Assembler 5 in C64Debugger (version 0.64.56).
Just add this setting to your user settings.
"kickass_args": "-debugdump"
And C64Debugger will automatically load the dbg-file.

Version 1.2.5

29 Oct 15:40
Compare
Choose a tag to compare
  • Bug fix: Preferences and settings menus now works when package is installed thru Package Control.
    Thanks Pontus Berg (@BacchusFLT) for reporting this
  • New Feature: Make command, assigned to key F8. Invokes a script called make.bat/make.sh.
    Use setting default_make_path for setting default make path,
    make-scripts located in the current directory will take precedence,
    but if not found the default path is also checked. No default value.
    Suggested by Pontus Berg (@BacchusFLT)

Version 1.2.4

25 Oct 21:05
Compare
Choose a tag to compare

Emergency release to fix serious bugs breaking the whole thing.

Release 1.2.3

25 Oct 08:27
Compare
Choose a tag to compare
  • New setting kickass_output_path for setting output-folder, default is bin
  • New setting kickass_compiled_filename for setting filename of compiled prg-file
    Default is SourceFile.prg (where SourceFile is the name part of the compiled asm-file), which is a change, before it was SourceFile_Compiled.prg
    Thanks wizofwor for suggestion
  • Menu items for accessing settings and preferences
    Can be found in menu Preferences -> Package Settings -> SublimeKickAssemblerC64.
    Thanks to @brushesm for this.
  • New Feature: Settings default_prebuild_path and default_postbuild_path for setting default prebuild-/postbuild path. Prebuild/postbuild-scripts located in the current directory will take precedence, but if not found the default path is also checked. No default value.
    Thanks to Achim (https://github.com/4ch1m) for fixing this
    More info: #25
  • Bug fix: Paths for pre/post scripts can now include spaces
  • Bug fix: User settings in file Preferences.sublime-settings should now work again