You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-10Lines changed: 9 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,21 +62,20 @@ This extension provides the following settings:
62
62
*`raspberry-pi-pico.gitPath`: Specify a custom path for Git.
63
63
*`raspberry-pi-pico.cmakeAutoConfigure`: Provide a GitHub personal access token (classic) with the `public_repo` scope. This token is used to check for available versions of the Pico SDK and other tools. Without it, the extension uses the unauthenticated GitHub API, which has a lower rate limit and may lead to restricted functionality if the limit is exceeded. The unauthenticated rate limit is per public IP address, so a token is more necessary if your IP is shared with many users.
64
64
65
-
## Using the CMake Tools extension
66
-
By default, this extension only supports projects with a single executable who's name matches the project name, and the project name cannot be a variable. For more complex projects that require better CMake parsing (for example with multiple executables, or if the project name is set by a variable), this extension can integrate with the CMake Tools extension to perform that parsing. You can enable the CMake Tools extension by changing the following settings in your `settings.json` file:
65
+
## CMake Tools Extension Integration
67
66
68
-
*`raspberry-pi-pico.cmakeAutoConfigure`: From `true` to `false`
69
-
*`raspberry-pi-pico.useCmakeTools`: From `false` to `true`
67
+
For more complex projects, such as those with multiple executables or when the project name is defined as a variable, this extension can integrate with the CMake Tools extension to enhance CMake parsing. You can enable CMake Tools integration during project generation under the **Advanced Options**. Additionally, to manually enable it, adjust the following settings in your `settings.json`:
70
68
71
-
You may also wish to enable the following settings as well, as the default `settings.json` file disables a lot of the CMake Tools functionality:
69
+
-`raspberry-pi-pico.cmakeAutoConfigure`: Set from `true` to `false`.
70
+
-`raspberry-pi-pico.useCmakeTools`: Set from `false` to `true`.
72
71
73
-
*`cmake.configureOnEdit`: true
74
-
*`cmake.automaticReconfigure`: true
75
-
*`cmake.configureOnOpen`: true
72
+
For optimal functionality, consider enabling:
76
73
77
-
When prompted to select a kit by the CMake Tools extension, you should pick the `Pico` kit. You can then use the CMake Tools extension to set your Build and Launch targets appropriately.
74
+
-`cmake.configureOnEdit`: true
75
+
-`cmake.automaticReconfigure`: true
76
+
-`cmake.configureOnOpen`: true
78
77
79
-
Once the Launch target has been set correctly, this extension should continue to work seamlessly with debugging etc, it will just use CMake Tools for compilation rather than it's own backend. Do not use the CMake Tools debugging functionality, as that will not work with the Pico.
78
+
When prompted, select the `Pico` kit in CMake Tools, and set your build and launch targets accordingly. Use CMake Tools for compilation, but continue using this extension for debugging, as CMake Tools debugging is not compatible with Pico.
<label for="debugger-radio-swd" class="w-full py-4 ml-2 text-sm font-medium text-gray-900 dark:text-gray-300">SWD (Pi host, on Pi 5 it requires Linux Kernel >= 6.6.47)</label>
<label for="debugger-radio-swd" class="w-full py-4 ml-2 text-sm font-medium text-gray-900 dark:text-gray-300">SWD (Pi host, on Pi 5 it requires Linux Kernel >= 6.6.47)</label>
0 commit comments