LINKING AEABI-COMPLIANT MODULES USING A
THIRD-PARTY LINKER
If you have a module produced using the IAR C/C++ Compiler and you plan to link that
module using a linker from a different vendor, that module must be AEABI-compliant,
see Enabling AEABI compliance in the compiler, page 198.
In addition, if that module uses any of the IAR-specific compiler extensions, you must
make sure that those features are also supported by the tools from the other vendor. Note
specifically:
● Support for the following extensions must be verified: #pragma pack,
__no_init, __root, and __ramfunc
● The following extensions are harmless to use: #pragma location/@, __arm,
__thumb, __swi, __irq, __fiq, and __nested.

ENABLING AEABI COMPLIANCE IN THE COMPILER
You can enable AEABI compliance in the compiler by setting the --aeabi option. In
this case, you must also use the --guard_calls option.
In the IDE, use the Project>Options>C/C++ Compiler>Extra Options page to
specify the --aeabi and --guard_calls options.

С одной стороны вроде бы возможно
(цитата из EWARM_DevelopmentGuide.ENU.pdf)

а с другой, если авторы этой библиотеки пренебрегли рекомендациями или просто не задумывались об этом, то библиотека получится не совместимая.