Skip to content

Conversation

@kaycebasques
Copy link
Contributor

No description provided.

cmake-*
build
build-*
build_*
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pico_setup.sh seems to create build_pico and build_pico2: https://github.com/raspberrypi/pico-setup/blob/master/pico_setup.sh#L82

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess that suggests that an alternative approach might be to modify pico_setup.sh to use build-directory names that are already covered by the .gitignore in pico-examples? ping @liamfraser
The advantage of modifying the pico-setup repo instead of the pico-examples repo, is that edits to pico-setup are made directly on master (and so get "released" immediately); whereas edits to pico-examples get made on the develop branch (and so don't get "released" until @kilograham does the next merge from develop to master).

@kilograham kilograham merged commit d03763e into raspberrypi:develop Feb 13, 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.

3 participants