Re: Best-practise currently for testing internal parts of libs? *_TEST_EXPORT macro?

2015-09-02 Thread David Faure
On Monday 31 August 2015 14:41:00 Friedrich W. H. Kossebau wrote: > > The only place lxr.kde.org pointed out to use the *TEST_EXPORT approach was > grantlee, which simply creates a separate file with the define that then is > appended to the file generated with generate_export_header: >

Re: Best-practise currently for testing internal parts of libs? *_TEST_EXPORT macro?

2015-09-02 Thread Friedrich W. H. Kossebau
Hi Kevin, Jeremy & David, thanks all for your replies so far, gives me/us a palette to chose from, nice :) Seems exporting symbols only for testing is not a great no-go with known big traps, okay. So no need to port away from that tomorrow. So... below: Am Montag, 31. August 2015, 18:54:19

Best-practise currently for testing internal parts of libs? *_TEST_EXPORT macro?

2015-08-31 Thread Friedrich W. H. Kossebau
Hi, what approach is best-practise currently for testing internal parts of libs? E.g. by symbols (classes) are not exported by default? In Calligra we have code that uses XYZ_TEST_EXPORT macros for those symbols which should be only exported in test-enabled builds, e.g. by defining