festvur.blogg.se

Using an existing Docker image – TDD in C with CeedlingĪnyone using or experimenting with Test-Driven-Development in C will probably be aware of Ceedling, unity and CMock.

Using a pre-build Microsoft container setup.Using an existing Docker image from Docker Hub.In this post, we shall cover three options: There are several different approaches to using Dev Containers.

Getting started with Dev Containers and Docker Using a custom Docker image based on a local Dockerfile – GoogleTest, GoogleMock.Using a pre-build Microsoft container environment – C++ and CMake.Using an existing Docker image – TDD in C with Ceedling.Getting started with Dev Containers and Docker.However, it would be my last take because I set this for not just me but my team (and yours, too), and Vim’s learning curve is very heavy for most developers. Let’s go with VS Code.Īpparently, we can use Vim directly within the container and install awesome plugins into it.

At the time writing this article, the features set looks good enough for starting, too. Nevertheless, the extension is officially developed and maintained by Microsoft (not open source) and is planned to be used in a lot of future services as a web companion IDE or cloud IDE - so it is very promising. The VS Code Remote-Containers extension has just recently released, so it is not as mature as GoLand. However, this feature is only applicable in the purchased version. GoLand support looks pretty mature because it has been there for a while (originating with IntelliJ). Luckily, there are two popular editors supporting just this: GoLand and VS Code. I was a bit worried when I was researching solutions for this objective because it heavily depends on vendors of code editors/IDEs being fine with working within a container.