microsoft/openvmm
Publicmirrored fromhttps://github.com/microsoft/openvmmAvailable
Guide/src/dev_guide/getting_started.md
28lines · modecode
| 1 | # Getting Started (for Developers) |
| 2 | |
| 3 | This chapter discusses all the basic steps required to begin building code in |
| 4 | the OpenVMM project. |
| 5 | |
| 6 | By the end of this chapter, you will have: |
| 7 | |
| 8 | - Cloned the OpenVMM git repo |
| 9 | - Installed all required pre-build dependencies (e.g: Rust) |
| 10 | - Built local copies of both OpenVMM and OpenHCL |
| 11 | - (optionally) Set up a suggested VSCode-based development environment |
| 12 | |
| 13 | ### _Aside:_ What is HvLite? Underhill? |
| 14 | |
| 15 | As you explore the OpenVMM repo, you may find references to things called |
| 16 | **HvLite** and **Underhill**. |
| 17 | |
| 18 | Simply put: |
| 19 | |
| 20 | - **OpenVMM** is synonymous with **HvLite** |
| 21 | - **OpenHCL** is synonymous with **Underhill** |
| 22 | |
| 23 | HvLite and Underhill were former Microsoft-internal codenames for OpenVMM and |
| 24 | OpenHCL. |
| 25 | |
| 26 | Migrating all existing code and documentation away from these codewords is not |
| 27 | an overnight process, and it's quite likely these terms will linger in various |
| 28 | code comments, variable names, library names, etc... the forseeable future. |
| 29 | |