New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Feature: Setting for default prebuild-/postbuild-path #25
New Feature: Setting for default prebuild-/postbuild-path #25
Conversation
@4ch1m |
This will be fantastic to merge. I am using a similar setup where I have |
sync master
…build # Conflicts: # KickAssembler (C64).sublime-settings # kickass_build.py
@Swoffa: OK. |
@4ch1m |
@4ch1m |
* new feature: default pre-/post-build-path via settings * new feature: default pre-/post-build-path via settings
Another small feature/improvement. ;-)
I pretty much always want to run the same "prebuild.sh" before building/running any ASM-file (simply to execute 'killall x64', etc.).
ATM I have to place a copy of my "prebuild.sh"-file into the folder where the ASM-file resides.
And if I ever change/update my "prebuild.sh"-file I will have to change/udpate all existing copies of it. :(
(I know that I could use symlinks... but the symlinks also will have to be created manually every time; for every directory I intend to build/run a ASM-file. And Windows-users also might not have the possibility of using symlinks.)
With this PR you can define a default-path where the "prebuild.sh"-file is located via a simple settings-entry.
Any "prebuild.sh" located in the ASM-file-directory will still take precedence; but if none is present we also check the default path.
Oh... and all of this also applies for the "postbuild.sh". :)