You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see currently library is being built as a static library. That makes every project that uses this library inject the code inside their program. Instead it can be built as a dynamic library (.so on linux and .dll on windows) and link dynamically on the runtime. It will reduce size of the result binaries and will get an option to users to update ittapi library without updating application (if the ABI is compatible).
My question is if it possible to add shared target to the build? It should be as easy as removing STATIC keyword from add_library and then it can be controlled with BUILD_SHARED_LIBS argument. Or there is a reason why it can't be loaded as a shared library?
The text was updated successfully, but these errors were encountered:
In short, ittapi being a static library is a design decision and converting it to a shared library would break a lot of things. ittapi has to distinguish the dynamic library it was being called from in some cases and the simplest way was to do it was to link statically to each of the instrumented exes/dlls.
I see currently library is being built as a static library. That makes every project that uses this library inject the code inside their program. Instead it can be built as a dynamic library (
.so
on linux and.dll
on windows) and link dynamically on the runtime. It will reduce size of the result binaries and will get an option to users to update ittapi library without updating application (if the ABI is compatible).My question is if it possible to add shared target to the build? It should be as easy as removing
STATIC
keyword fromadd_library
and then it can be controlled with BUILD_SHARED_LIBS argument. Or there is a reason why it can't be loaded as a shared library?The text was updated successfully, but these errors were encountered: