Compiled libraries depend on being inside the "bin"-folder

Hi,

I just found out, that the compiled DLLs rely on beeing inside a folder called "bin" (as they are after the compilation process). Renaming the "bin"-folder after compilation (like to "binary" for example) results in the following error:

`ERROR: Unable to load dependent library ...\binary\../bin/libgcc_s_seh-1.dll`

There should be no path construct like that in the final DLL (_go one path element down an re-enter the "bin"-path_), a DLL should be independent of its path (if possible). The "bin"-folder can be moved to any location and the DLLs still work, as long the "bin"-folder is not renamed.

BTW, the EXE fails with code `0xc0000142`.

Thanks and regards!

Edit: Testet on Windows 10 (64-bit) with the shipped library example.

Use the shipped library example on Windows 10 (64-bit) and first reproduce the failure by renaming the compiled "bin" folder to "binary". Inspect the generated DLL dependency path and the EXE failure, then verify that the compiled DLLs and executable still load after the folder is renamed or moved without requiring a "bin" path.

Written by the indexing model from the issue text.