WIP: Add the base containerized c toolchain environment #11
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "10_env_image"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I opened this more as a chance to discuss about the process, than with the idea to have it merged.
I haven't got too much of an idea how this image should look like, or how it will interact with the project, where it should be placed in the codebase, and such. Would like to take this opportunity to discuss.
Add:
nasm
hdxxdThis is essentially it.
docker-compose.yml needs to be placed in project root. I personally place all Dockerfile files in
/Dockerfiles/
.Regarding vim, I think the best way to enforce project-level configuration is to use something like this. This means using local vim binary, but loading additional configuration (on top of an existing
.vimrc
) based on a project-level configuration file placed inside project root. I haven't actually used this before, just thinking out loud...Add the base containerized c toolchain environmentto WIP: Add the base containerized c toolchain environmentI have merged existing Wiki explanations with your proposed README changes into https://gitea.dmz.rs/sborovic/dmzOS/src/branch/main/README.md#development-environment. Does it look okay?
I'd review if all the software from the list above is actually available inside the image. After that, I think that pull request if ready to be closed.
EDIT: Also, as proposed README changes are conflicting maybe they can be removed from the pull request.
Pull request closed