-
- since the current resulting codesize added by app4mcsim.lib and systemc is under 10mb, it make sense to use static linking because: - less problems executing the resulting binaries - more optimization opportunities and no dynamic loading and dispatch - systemc give no garuantees for their ABI to be compatible with different versions/compilers, therefore static linking improves robustness (although we already compiling SystemC within the project) Signed-off-by:
Benjamin Beichler <Benjamin.Beichler@uni-rostock.de>
- since the current resulting codesize added by app4mcsim.lib and systemc is under 10mb, it make sense to use static linking because: - less problems executing the resulting binaries - more optimization opportunities and no dynamic loading and dispatch - systemc give no garuantees for their ABI to be compatible with different versions/compilers, therefore static linking improves robustness (although we already compiling SystemC within the project) Signed-off-by:
Benjamin Beichler <Benjamin.Beichler@uni-rostock.de>
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
CMakeLists.txt 2.01 KiB