Development Environment - johnttaylor/epc GitHub Wiki
Two initial decisions you will need to make that will have a long-term impact on your project are:
-
Who will maintain the environment after it is set up? — In terms of maintainability, the preferred situation would be for you to work with your IT department to set up the development environment, and then, after it is up and running, have them support, maintain, and backup the environment. This will result in some additional communication and coordination overhead with your IT department, but in the long run, you will save more time not having to engage in IT-related (not coding-related) activities. This option may not be available to you, but if it is I strongly recommend you take it.
-
Will my development machines be real or virtual? — There is no right answer to this question; it is entirely dependent on your situation and your use cases.
The development environment for the GM6000 project consists of Windows and Linux machines. It is possible, of course, to have the development environment be exclusively Linux; you just need to install the Linux counterparts of all the Windows tools specified here. However, for the GM6000 exercise, the focus is strictly on the combined Windows and Linux environment.
The configuration of the build machine and the developer machine share some common tools. Here is a summary of what tools need to be installed on which machines:
| Developer Machine | Build Machine |
|---|---|
| Python | Python |
| Git | Git |
| Doxygen | Doxygen |
| Graphviz | Graphviz |
| Microsoft Help Compiler | Microsoft Help Compiler |
| gcovr | gcovr |
| pexpect | pexpect |
| MinGW-w64 Compiler | MinGW-w64 Compiler |
| Visual Studio | Visual Studio |
| [7-Zip] | 7-Zip |
| Jenkins | |
| Cloc | |
| STM32 Cube IDE | |
| STM32 Cube MX | |
| Outcast | |
| Segger J-Link tools | |
| Segger Ozone Debugger | |
| Segger SystemView | |
| [SinelaboreRT] | |
| [Cadifra UML Editor] | |
| [Putty] | |
| [Tera Term] |
|