Skip to content

Conversation

sporniket
Copy link

  • use -B <path_to_build_folder> to manage build folder, instead of manually creating directory and going there.
  • use --target ... to avoid delving into specific subfolder and calling makeinstead of cmake.
  • The build folders are created outside of pico-* folders, so that they are not lost among the various subfolders of the pico-examples folder.

* use `-B <path_to_build_folder>` to manage build folder, instead of manually creating directory and going there.
* use `--target ...` to avoid delving into specific subfolder and calling `make`instead of cmake.
* The build folders are created **outside** of pico-* folders, so that they are not lost among the various subfolders of the pico-examples folder.
@lurch
Copy link
Contributor

lurch commented Mar 10, 2025

Note that pico_setup.sh was originally written to closely mirror the instructions in https://datasheets.raspberrypi.com/pico/getting-started-with-pico.pdf (back from before the Raspberry Pi Pico VS Code extension existed 😂 ), which is probably why it does things "the long way" rather than using "advanced options" ?

@sporniket
Copy link
Author

Ho I see.

@lurch
Copy link
Contributor

lurch commented Jul 8, 2025

I think that this PR is now redundant, in light of 7e995b4 and 38b21a3 ?

@sporniket
Copy link
Author

yes seems better.

@sporniket sporniket closed this Jul 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants