* Improve vscode clangd experience
- Resolve and use absolute path for the toolchain. This allows clangd to use compile_commands.json file without running under fbtenv, simplifies setup for vscode clangd extension. As a side effect, a rebuild is needed to update compile_commands.json after moving the source tree.
- Add the recommended default settings of the extension to settings.json.
* Use build/latest for compile-commands-dir
This makes it behave closer to c-cpp-properties.
* Reformat crosscc.py
This is a PEP-8 violation but black seems to enforce it
* Bypass --query-driver
This has some security implications as it grants clangd the ability to execute any executables anywhere while trying to probe a compiler based on CDB. However it's very hard to do this the safe and intended way without resorting to config generation due to reason listed in #2431. Besides that we already have workspace trust so what could go wrong? ;)
* Add an option for vscode_dist to switch between clangd and cpptools
This will install different extensions.json tuned for either clangd or cpptools based on user selection. It will also install c_cpp_properties.json when using cpptools since clangd doesn't use this file.
The root .gitignore now also doesn't accidentally ignore everything under the .vscode directory.
* Use absolute path for .vscode gitignore
Turns out the previously used "relative" paths aren't even valid gitignore patterns and to actually do what it means one needs to use the absolute paths instead.
* Handle variable parsing in commandline.scons
commandline.scons is the place where all other command line parsing happens. Move LANG_SERVER variable parsing there and add a constraint to make the code more consistent.
---------
Co-authored-by: hedger <hedger@users.noreply.github.com>
Co-authored-by: hedger <hedger@nanode.su>
* Scripts: OB recovery
* Scripts: slightly different ob
* Scripts: remove excessive return
* Scripts: simplifying work with registers
* Make PVS happy
Co-authored-by: SG <who.just.the.doctor@gmail.com>
* Allow loading user supplied keys and add CTR mode
* Add GCM mode to furi_hal_crypto
* Split up CTR and GCM code, add flag for adv crypto
* Add convenience functions for GCM crypto
* Run fbt format
* Update GCM to support additional auth data
* Update APIs
* FuriHal: update crypto documentation, method names and usage
* Clean up code for key (un)loading, GCM and CTR
- get rid of goto
- do not use furi_hal_bt_is_alive() when not using secure enclave
- give defines a type and wrap in ()
* Add unit test for CTR and GCM crypto
* FuriHal: const in crypto unit tests, cortex timer for crypto operations timeouts
* FuriHal: update crypto docs
Co-authored-by: twisted_pear <twstd@posteo.net>
Co-authored-by: hedger <hedger@users.noreply.github.com>
Co-authored-by: あく <alleteam@gmail.com>
* fbt: Fix building on Windows using path with space
* scripts: Fixed formatting
---------
Co-authored-by: hedger <hedger@users.noreply.github.com>
Co-authored-by: hedger <hedger@nanode.su>
* NFC CLI: Fix multiple apdu commands from not working when one of them gives an empty response
* Make PVS happy
Co-authored-by: hedger <hedger@users.noreply.github.com>
Co-authored-by: あく <alleteam@gmail.com>
* NFC: Fix key invalidation (again~)
* NFC: shouldn't be there
This code get called each time we check for B key
Co-authored-by: あく <alleteam@gmail.com>
* Add new rtc flags to device info
* FuriHal: bump info version
* Fix local
* Rework device info by hierarchy filtering
Co-authored-by: あく <alleteam@gmail.com>
