-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use common pico-vscode.cmake file #41
Conversation
"endif()\n" | ||
f"set(sdkVersion {params['sdkVersion']})\n" | ||
f"set(toolchainVersion {params['toolchainVersion']})\n" | ||
f"set(picotoolVersion {params['picotoolVersion']})\n" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, this also directly fixes an issue I noticed during testing that currently the extension always generates a CMakeLists.txt
with a picoTool version equal to it's selected SDK version (see L593).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a great addition for the modularity and platform independence of pico projects.
I tested it with different projects and it worked without problems in all scenarios we implemented before like switching SDK version.
Instead of different DO NEVER EDIT lines for each SDK version, include a common file which does all that logic Update any existing CMakeLists.txt files to this new style when extension is loaded
Use USERHOME, rather than a full path
96dd2b4
to
c2d6918
Compare
Instead of different DO NEVER EDIT lines for each SDK version, include a common file which does all that logic
Update any existing CMakeLists.txt files to this new style when extension is loaded, and also copy the pico-vscode.cmake into place whenever the extension is loaded to ensure it is up-to-date
This will make future updates which require changes to that section of the file much simpler, as the separate pico-vscode.cmake file can be updated instead