Wine's goal is first and foremost emulation of Windows userspace, and Windows uses DYNAMICBASE and HIGH_ENTROPY_VA for its DLLs.

Hi,

I'm not sure I understand this stance since both mingw and��msvc provide full control over the DYNAMICBASE flag at compile time.�� In our case, we MUST be able to control this flag for compatibility��with older DLLs to maximize compatibility��with our software, otherwise the non-Windows versions of LMMS would��have an artificially imposed��regression/limitation over versions targeting Windows directly.�� In practice, this means that a large percentage of older VST plugins will just stop working overnight, simply because we used a modern version of wineg++ to compile our bridge.��

I'm not aware of any documentation or tutorial, but you can consult existing DLLs like wpcap, mountmgr.sys, or winscard (or anything that uses WINE_UNIX_CALL).

Thanks for the pointer.�� Depending��on how successful (or more specifically, lack thereof), we may need to build a custom winebuild for the foreseeable future.�� We already plan to do this for the short-term, but as other wineg++ apps run into crashes when��ASLR/DYNAMICBASE is enabled, this is likely to be requested again in the future.