Force linking of application-specific components
Posted: Mon Feb 18, 2019 4:45 am
Hi,
I have an application-specific component that is not referenced from anywhere else. Because of that the linker is not including the module. While this behavior is OK for the vast library of ESP-specific components, it causes issues for my app. Of course I can add an artificial dependency to that application-specific component but I wonder if there are any flags/parameters where I can tell the linker to always include my components.
Thanks,
AP
I have an application-specific component that is not referenced from anywhere else. Because of that the linker is not including the module. While this behavior is OK for the vast library of ESP-specific components, it causes issues for my app. Of course I can add an artificial dependency to that application-specific component but I wonder if there are any flags/parameters where I can tell the linker to always include my components.
Thanks,
AP