Re: Unit tests on Windows DLL internals

[Mark Rivers via Core-talk <core-talk at aps.anl.gov>]

> (No such problem on Linux where all functions inside the shared library are visible.)


That is true by default, but GCC >= 4 has __attribute__ ((visibility ("hidden"))) which will also hide classes on Linux.


This article makes the argument for why it is a good idea to use it:


https://gcc.gnu.org/wiki/Visibility

Mark

________________________________
From: Core-talk <core-talk-bounces at aps.anl.gov> on behalf of Ralph Lange via Core-talk <core-talk at aps.anl.gov>
Sent: Wednesday, January 27, 2021 5:01 AM
To: EPICS Core Talk
Subject: Unit tests on Windows DLL internals

Question about developing on Windows:

How do you manage unit testing of internal classes in DLLs?

Internal classes (that are not DLL exported) are by design not visible through the DLL interface, which means linking a unit test against the DLL won't allow it to access the internal APIs it is supposed to test.
(No such problem on Linux where all functions inside the shared library are visible.)

I know I can work around by linking the needed objects directly into the test executable. Is there any preferable or better solution?

Thanks,
~Ralph