[Autogenerated] what we've seen in the previous demo is that the
executable has a bunch of dependencies which are written as part of
the import inside the portable executable.
This also applies to DLS which might depend on other dealers.
This is known as implicit linking to a DLL.
And the way it's done from a developer perspective is by using a
small leap file that contains the name of the DLL without any
path and the list of exported symbols.
And these are the things that going to be then embedded as part of the p of
the executable or DLL that is using or needs that other DLL.
And so at runtime,
the loaders purpose is to locate that DLL and all
the other dependencies of course,
and to bind the real function implementation where they happen to fall if
the DLL is not found using the search path that we described earlier or the
dealer main function of that DLL returns false,
indicating that it failed to initialize.
For some reason, then the process would be terminated,
which means that this DLL are necessary.
These are mandatory.
The process can't really go forward without these DLL existing.
Let's see what that looks like in code