* add unspecified build type and remove CMAKE_BUILD_TYPE prop when it's used
* reverted commenting out debugger
* let debugger stop on error again
* updated changelog
* updated the docs with the new option
* updated default kit build type
* fix failing tests
---------
Co-authored-by: Garrett Campbell <86264750+gcampbell-msft@users.noreply.github.com>
* Replace intra-repo absolute URLs with relative ones.
* Replace remaining pointers to `vector-of-bool` with `microsoft`
in the URLs than must remain absolute.
Co-authored-by: Garrett Campbell <86264750+gcampbell-msft@users.noreply.github.com>
* add syntax files, add languages, grammars, to package.json
copy over stuff to play with later
got the grammars working with the other stuff commented out
cleaned up, not tested
remove stuff
I don't think we really need to have a unique ID, we should tell people to only install our extension
remove unnecessary method
update our syntaxes from what we do in VS
test pipeline
update cgmanifest
temporarly force cg
test different version
use .3 version
update notice, it includes textmate reference
manually add kitware/cmake reference to NOTICE
fix trigger
fix pipeline name
get repo
make sure we checkout the repos
powershell
inline
reference variables correctly
testing for differences, CHANGE LATER
updating textmate
see if we're getting the right git diff
test with explicit path
update dates
write output
try to properly access variables
use embeddedbot
put emails and username in variables
switch when I update config
orgurl
add logging
update auth
update docs
testing out PR tool
remove 'description' option
add console.log statements for testing
map system token
run index.ts for both grammars and quickinfo, put paths into variables, condition based on parameters
fix trigger
access variables correctly
access variables correctly
only run job if one of the share steps is enabled
fix job name
test without prefix
remove difference
remove snippets keyword until we actually add this
remove stray miscopy
remove powershell
* small update
* ignore tools directory when packaging
* don't build the tools directory when building and testing the extension
* exclude tools for webpack?
* revert webpack
* try webpack fix again
* try another fix
* revert
* we need to remote the NOTICE for testing earlier so yarn doesn't fail
* rename notices.txt to get around yarn issue
* update changelog
* Update the already available settings to use in presets.
Turns out, we already have configure, build, buildTool, and test
args/envs that can override. I modified the code to use these in
presets. Also, I added a small sentence to the settings descriptions to
notify users that when using CMake Presets, they are designed for
overrides, not general configuration.
* pending further discussion, use general environment for all
* add temporary override string for presets to environment setting description
* don't remove configureSettings
* add text to specify that configureSettings isn't for presets scenario
* Add tentative treeview UI and output message for configure
Still need to do build/test/etc, and likely improve the strings
themselves.
* add output lines, improvement on the string to come, testing for location
* don't output message when we're using cache
* add handlers that update the nodes when a test or build setting is modified
* slight refactor and add * to status bar
* add button that only appears when overrides present that allows opening those settings
* share some code
* fix localize calls
* update tsconfig.json
* update eslint
* slightly reword the settings
* fix buildTool args
* avoid duplication
* ensure we only return -3 when testPreset isn't defined
* fix imports
* changelog and docs
* refactor to avoid circular dependency
* missed one
* fix imports
* storing initial thoughts
* rough version of trying to work on new options for debugger configurations
* made progress enabling script debugging from launch.json
* add some output messaging regarding the debugger and script
* add TODO's in case I don't get to it today
* log statements, ensure package.json allows the right args in right situation, set up env for script debugging
* push worst case copying the description and settings of the debugger options
* I think I've covered all launch config cases
* better package.json schema, though still not perfect, matches other debug types, and stub validation in code
* localize error messages
* add 'The'
* switch to double quotes
* add docs page for debugging
* slight modifications
* didn't handle case where scriptEnv was undefined
* add configurationSnippets
* add stub for debugconfigurationprovider
* add ability to 'run and debug' without launch.json on *.cmake files
* modify when we sanity check
* make adjustments based on feedback and add automatic configuration
* ensure that configure with debugger works with the right format
* update changelog
* add lldb to debug-launch.md
This adds the lldb configuration needed for macOS
* Update CHANGELOG.md
---------
Co-authored-by: Ben McMorran <bemcmorr@microsoft.com>
* Resolve ${cmake.testWorkingDirectory} to the WORKING_DIRECTORY property of a test in launch.json
To be used in "cwd" field for tests to have the same context when debugging as when running normally
* Add example usage of cmake.testWorkingDirectory in docs
* Add changelog entry
Sandro Pedrett
Lin Hsu
Sinem Akinci
Garrett Campbell
Andrew Shark
snehara99
Cy 'kkm' Katsnelson
Andreea Isac
cctv130
Werner Robitza
salo-dea
Bailey Lissington
Patrick Keil
philippewarren
Elaheh Rashedi
TisziV
Bob Brown
Ernst Sjöstrand
Josh Deaton
Elaheh Rashedi
David Fong
josetr
Thi
kouhe3
Michelle Matias