Single exe vibe.d app

[Suliman via Digitalmars-d-learn]

On Thursday, 6 April 2017 at 17:39:15 UTC, Stefan Koch wrote:
> On Wednesday, 5 April 2017 at 12:13:38 UTC, Satoshi wrote:
>> Hi,
>> How can I build single exe application with vibe.d (windows)?
>> now it require zlib.dll, libeay32.dll and ssleay32.dll
>>
>> But I need it as single app.
>
> One solution would be to compile vibe.d without ssl support
> that way it will not need libeay32 and ssleay32
>
> It should not need zlib, really as zlib is already linked into 
> phobos.

Could anybody give very easy explanation about what different 
between static and dynamic libs. I read a lot of information that 
dynamic lib allow to loading at runtime and bla-bla-bla, but 
still do not understand what different between compilation at 
dynamic and static lib.

For example:
1. Does every lib can be compiler as static and as dynamic?
2. Can already compiled lib be converted to from static to 
dynamic and vise-versa.
3. If I have any dynamic lib, the only way is distribute it with 
app (or use import) or there is way to embed code from it to app?

Personaly I like if I can get single bin without any external 
dependence. In a lot of cases size do not important, it's better 
to have single bin, than heap of libs.