Experimental class in baloo

[Michael Heidelbach]

On 21.03.2018 01:16, David Edmundson wrote:
>
>
> On Tue, Mar 20, 2018 at 9:43 AM, Michael Heidelbach <ottwolt at gmail.com 
> <mailto:ottwolt at gmail.com>> wrote:
>
>     Hi!
>
>     I've recently introduced a new class for baloo
>     <https://cgit.kde.org/baloo.git/commit/?id=9de78becc06346a734279c2dc13d081dc5861624>.
>     It is mainly for debugging. As it is accompanied with a command
>     line tool it may be useful for users too.
>
>     It is still in an experimental state and it's likely I'll wish to
>     change the public interface.
>
>     1) Is it possible to mark that class as experimental for some time
>     and have the allowance to chance the interface?
>
>
> Once you've exported symbols in the same library as baloo...not really.
>
>     2) If so, what is the best way to communicate that?
>
> If it's purely for debugging, stick it behind some optional CMake 
> definition so only users who explicitly enable it have the header 
> installed.
>
>
> David
>
Thank you for your reply, David.
In this case I would like to hide it (and the command line tool) at 
least until 5.46.
I'm not very knowledgeable with CMake. I guess sticking it 'behind some 
optional CMake definition' will also account for it not being part of 
the library. I've never done this before can you some help or an example 
please.

Michael


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20180321/6291dea3/attachment.html>