You might be thinking, why should I go to all this trouble? You shouldīecause it's not that much trouble and then you will have a great unit testĮnvironment that does not interfere with your native environment. Workig with Windows and Docker, please contribute your instructions.) For Windows you can either use the newer Dockerįor Windows, if you have Hyper-V, or the older VirtualBox based Docker Toolbox. I use a Mac, so I've installed docker for Mac. TheĬompilers and tools are hidden in the docker container. To make it easy to get started I'm usingĪ cool thing about using Docker is that you don't have to install otherĬompilers on your system, though you do have to install docker. With the ever changing C/C++ environments, it has been a challenge to keep Instructions for building the book's code with Docker ![]() The structure so that there are no projects inside of projects. Of the code in Test-Driven Development for Embedded C. This directory structure is not exactly the same as the structure Book code for Test-Driven Development for Embedded C
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |