Code owners
Assign users and groups as approvers for specific file changes. Learn more.
recorder.sublime-project 2.03 KiB
{
"folders":
[
{
"path": "../vimba",
"name": "vimba"
},
{
"path": ".",
},
{
"path": "../dox",
"name": "dox"
},
{
"path": "~/dox/idiv/camtron",
"name": "dox 2"
},
],
"build_systems":
[
{
"name": "recorder",
"working_dir": "$project_path/obj",
"shell_cmd": "qmake6 && make -j8 && cd ../bin && recorder",
// COLORS in output - HOW??
// "env": {"GCC_COLORS": "error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01"}, //force color for some CLI programs
// "env": {"CLICOLOR_FORCE": "1"}, //force color for some CLI programs
// "syntax": "/home/sugu/.config/sublime-text/Packages/User/make-output.sublime-syntax",
//### RESULTS // -> toggle with shortcuts ctr+alt+left/right
// capture up to four fields of error information from a results view, namely: filename, line number, column number and error message.
// Use groups in the pattern to capture this information. The filename field and the line number field are required.
// test in: https://regex101.com/r/yN4tJ6/1
"file_regex": "([a-zA-Z0-9\\.\\/_-]+):([0-9]*):([0-9]*): ((note|warning|error|fatal error): ([^\\n]*))",
// "line_regex": "...",
// If file_regex doesn’t match but result_line_regex exists and does match on the current line,
// walk backwards through the buffer until a line matching result_file_regex is found,
// and use the two matches to determine the file and line to go to.
"variants":
[
{
"name": "rebuild && run",
"shell_cmd": "make -j8 clean && qmake6 && make -j8 -B && LD_LIBRARY_PATH=../bin",
},
{
"name": "rebuild",
"shell_cmd": "make -j8 clean && qmake6 && make -j8 -B",
},
{
"name": "build",
"shell_cmd": "qmake6 && make -j8 ",
},
{
"name": "run",
"shell_cmd": "cd ../bin && recorder",
},
{
"name": "qmake6",
"shell_cmd": "qmake6",
},
{
"name": "clean",
"shell_cmd": "make -j8 clean",
},
],
},
]
}
//build sys @ ~/.config/sublime-text/Packages/User/C++.sublime-build