-
-
Notifications
You must be signed in to change notification settings - Fork 938
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
Unify docker devcontainer with dockerfile used for CI #1587
Merged
NeroBurner
merged 23 commits into
InfiniTimeOrg:main
from
BloodStainedCrow:unifyDockerDevcontainer
Mar 23, 2024
Merged
Changes from all commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
d3709cc
Only use one Dockerfile and build.sh script for both docker and devco…
BloodStainedCrow 6a46d7b
Remove all now unneccessary tasks and scripts
BloodStainedCrow 82fd87d
Update to clang-format-14
BloodStainedCrow b828a1a
Move devcontainer.json into root folder
BloodStainedCrow a242eff
Fix: .devcontainer.json pointing at wrong Dockerfile location
BloodStainedCrow ec9ede2
Fix conditional statements in Dockerfile
BloodStainedCrow 890793c
Move .devcontainer/README into doc/usingDevcontainers
BloodStainedCrow 7ab3177
Remove obsolete VSCode Task
BloodStainedCrow 4a7b0c5
Change standard compiler path to the correct compiler
BloodStainedCrow 71ad9a0
Use the correct compiler for building and for IntelliSense
BloodStainedCrow ac39029
Set GDB Path for debugging
BloodStainedCrow 3a58fde
Hide broken buttons from CMake Extension
BloodStainedCrow e8477c7
Refactor .devcontainer
BloodStainedCrow a565015
Remove unneccessary runArgs
BloodStainedCrow 7d6bff9
Remove unneccessary postBuildCommand
BloodStainedCrow 1dc1609
Add devcontainer dependencies to all docker images
BloodStainedCrow 2826a25
Clean outdated comment
BloodStainedCrow 9b2c1b6
Add Devcontainer Debug launch config
BloodStainedCrow de77ef8
Add an additional c_cpp_properties config as a fallback for devcontainer
BloodStainedCrow 077af79
Remove obsolete Docker Argument
BloodStainedCrow 0a0a4c3
Re-Add stopping on main after restart
BloodStainedCrow f0e3984
Fix wrong C/Cpp versions
BloodStainedCrow c326cd9
Fix silent fail of gdb, add libncurses5
BloodStainedCrow File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at: | ||
// https://github.com/microsoft/vscode-dev-containers/tree/v0.154.2/containers/cpp | ||
{ | ||
"build": { | ||
"dockerfile": "docker/Dockerfile" | ||
}, | ||
"customizations": { | ||
"vscode": { | ||
"settings": { | ||
// Set *default* container specific settings.json values on container create. | ||
"terminal.integrated.profiles.linux": { | ||
"bash": { | ||
"path": "/bin/bash" | ||
} | ||
}, | ||
"terminal.integrated.defaultProfile.linux": "bash", | ||
"editor.formatOnSave": true, | ||
// FIXME: This and the Dockerfile might get out of sync | ||
"clang-format.executable": "clang-format-14" | ||
}, | ||
// Add the IDs of extensions you want installed when the container is created. | ||
"extensions": [ | ||
"ms-vscode.cpptools", | ||
"ms-vscode.cmake-tools", | ||
"marus25.cortex-debug", | ||
"notskm.clang-tidy", | ||
"mjohns.clang-format" | ||
] | ||
} | ||
}, | ||
"remoteUser": "infinitime" | ||
} |
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
[ | ||
{ | ||
"name": "InfiniTime Compiler", | ||
"environmentSetupScript": "${workspaceFolder}/docker/build.sh" | ||
} | ||
] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
can the "GCC_ARM_PATH" variable be used here?
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.
As far as I know (see my previous attempts above) VSCode currently does not support loading variables for launch.json from anything but launch.json itself, which sadly means without some serious hacks, there will be this reference here, which might become outdated.
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.
Looking at this though, the very least I should do is unify the occurrences of it in a variable in launch.json so only one value can grow stale
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.
that would be very welcome, as it would minimize the staleness factor (if that is a word 😁 )
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 was mistaken, it seems is not possible to share variables (outside a .env file, but that would be out of scope for this PR IMO) between mutiple launch.json configurations.
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.
Additionally I currently have no way to test the other configuration on, whether they even still work in their current state, from what I can tell, at least one of them is around 3 years out of date...
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.
Not a different compiler? We just need one (the currently officially supported one)
Or what configurations are you talking about. If they are deprecated the maybe we can remove those?
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.
In
launch.json
there are different launch configurations usable via a button in VSCode. These are what I meant.While I am open to removing them/replacing them with ones that actually work, I would probably like some more input from people who might use them, so maybe in another PR...
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.
Thanks for the clarification. I agree. Let's merge this!