Skip to content
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

DRAFT: Fix for VSCode Windows Extension #89

Conversation

wyattearp
Copy link
Contributor

Looking to fix #87 - I believe the pico-vscode.cmake is likely missing from being commited, but I also think it should probably live in the .vscode directory, which is currently under the .gitignore list.

This is just a draft so I can make sure I'm getting the right items into place, will update with a corrected .vscode/ and .gitignore as well as the corrected pico-vscode.cmake (when I find it).

wyattearp and others added 30 commits September 4, 2024 18:50
now using the default cmake instead of the python one to align to the
operting system's preferred directions. this shouldn't really be an
issue as there's nothing extremely fancy going on in cmake

also moving the docker compose to my personal repo for now, need to talk
with the bp team if they're fine with me actually pushing a real org for
them.
now using the default cmake instead of the python one to align to the
operting system's preferred directions. this shouldn't really be an
issue as there's nothing extremely fancy going on in cmake

also moving the docker compose to my personal repo for now, need to talk
with the bp team if they're fine with me actually pushing a real org for
them.
with the inclusion of these changes, we address the python weirdness for
cmake as well as we now correct the issue with picotool being unable to
bootstrap. it comes at the cost that if we update picotool to a
different version, we have to update the docker, but that appears to be
a documented issue in their bugs so ... until that's better we're going
to have to stick with that.

also added the .devcontainers for vscode users. this should just "bring
up" a build environment for the vscode system. tested only on linux, but
looking for windows volunteers.

do note that if it fails to build, it's likely that you have a
permissions issue on your current build/ directory and need to clean it
up first.
…ipx-docker

Fix: update for pip and docker
Add legacy mode for third parties flashrom avrdude
@wyattearp
Copy link
Contributor Author

I think I'm really hitting something strange here, like the Windows command line character limit being 8191 characters. It's odd as well that cmake says the line builds but then errors out:

https://github.com/DangerousPrototypes/BusPirate5-firmware/actions/runs/10804479944/job/29969997946?pr=89#step:8:844

@wyattearp wyattearp closed this Sep 14, 2024
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.

Automated Build For Windows Failing
3 participants