I have a shared library I am considering licensing via LexActivator. The shared library will be part of a suite of tools plus and SDK.
The suite of tools is link to the shared library.
The SDK can be use to build new applications but will still need to link to the shared library.
What I hope to achieve is that the moment the shared library is loaded, it will trigger the LexActivator calls I can put in.
This shared library will be build for Linux, MacOS and Windows
Is there a portable way/location to place the LexActivator calls ?
I am considering
__attribute__((constructor)) for Linux/MacOS and
DllMain() for Windows. Are these suitable within the context of licensing via LexActivator.
Is there a recommended approach for licensing DLL that cryptlex recommends ?