Open evandrocoan opened 7 years ago
Just for the record, how many build systems are we talking about and why do you need this many? It just seems to me that ST's build systems are not the proper tool for this job.
I faced this problem on a project with git submodules. I wanted to not write, therefore hide from the main project how the submodule is built by sublime-build
. So not changing the parent project .sublime-project
build systems list, adding the submodule build system. So it would be basically one sublime-build
per git submodule.
Basically would be allowing to slit the .sublime-build
embedded on the .sublime-project
their own files written on .sublime-build
. This is somehow related to:
Load
*.sublime-build
files from my project workspaceThis is useful for big projects to split across several
.sublime-build
files the several build systems a project may have. Currently you can create on big file at your.sublime-project
within all build systems all together.The initial custom build support on
.sublime-project
files was requested on:Now it would allow build systems
.sublime-build
to be written across the project files. For example, if I write a file calledmake.sublime-build
inside my project, Sublime Text would load that build system specification and allow the user to choose it when building a project by going onTools -> Build With... (Ctrl+Shift+B)
.