Community Wiki documentation on the boot process
Since detailing the whole process into its finest details requires quite some analysis and research to be applicable to all Windows versions, and to outline the minor details of the setup; please help write this community wiki which can benefit other users in the future which are trying to understand where and why their boot procedure has failed... Thank you!
Copying Windows Files:
Since expanding everything from the installation medium would be tedious, setup first copies everything.
Copies boot.wim to C:\$Windows.~BT
Copies install.wim to C:\$Windows.~LS
Expanding Windows Files:
Now that we have our files, they can be expanded.
Expands install.wim in C:\, for Users, ProgramData, Program Files, Windows, ...
Expands boot.wim, containing the executable(s) and configuration to be able to boot.
Installing Features:
Enables and configures the features that need to be enabled, note that these can be customized. Given that the files are already in place, this is most likely making some hard links and changing some registry features to make the features present on the system.
Installing Updates:
Installs any KB updates that have been packed onto the installation medium. This is a common practice such that when you have to do multiple installations, it doesn't have to fetch the updates from the internet every time.
Completing Installation:
Detects your drivers, installing any drivers that came with the installation medium. If you need to install to a lot of computers of the same type, packing the drivers is worth it.
Cleans up anything temporary the setup has left behind.
Makes sure the system can be rebooted.
Makes sure the data on the hard drive has been synchronized and is no longer cached.
Reboots the system.
First Boot:
Some more configuration, mostly to further customize the OS to your hardware.
Audit Mode (optional):
If the system is set to boot in audit mode; either via unattended configuration, sysprep /audit or by holding Ctrl+Shift+F3 then the installation can be customized prior to making an user, this is useful to provide certain features (called crapware these days) before finalizing the installation. Note that usually this phase is automated, which finishes with a call to sysprep /oobe.
Out of Box Experience:
Finally, you arrive at the Welcome Screen where you can create your user profile.
The first login per user applies some further personal configuration.
Best Answer
Make is a general purpose workflow program, usually used for compilation. But it can be used for anything.
When you do something like "make all", the make program executes a rule named "all" from a file in current directory named "Makefile". This rule usually calls the compiler to compile some source code into binaries.
When you do "make install", the make program takes the binaries from the previous step and copies them into some appropriate locations so that they can be accessed. Unlike on Windows, installation just requires copying some libraries and executables and there is no registry requirement as such. In short, "make install" just copies compiled files into appropriate locations.