Unit tests of internal functions
lukeh at padl.com
Wed Dec 30 09:29:50 EST 2009
On 30/12/2009, at 3:23 PM, Luke Howard wrote:
> On 30/12/2009, at 3:09 PM, Ezra Peisach wrote:
>> Ignoring the bashing of libtool...
>> There is another solution to the problem and requires the export of only
>> one function... It is however ugly... One could build the test programs
>> into the library requiring a single function to execute them.... For a
>> static library this would not be so bad as the test code would be thrown
>> out at linking. With shared libraries, all executables get the code as
> But maybe combined with the idea of linking the shared library twice (with and without tests), this is workable?
Or always build it static for testing, and dynamic/static otherwise for install.
More information about the krbdev