Do you think that it would be interesting to split it into a library and an executable for the REPL rather than exporting symbols in the executable?
That would be much easier, indeed (and it’s what we do for ROOT). But for I’m not sure the benefits are as high for cling - which is more of a demo application of the underlying functionality. The cost, OTOH, will be people saying “I start cling and it fails to find its library”
Well, we do depend on cling in xeus-cling, and that would be a more natural thing for us to do if you split into two cmake targets. I find it unlikely that the executable can’t find the shared object.
Similarly, I would be in favor of splitting the jupyter kernel out of the main cling repository, because it brings a dependency to the Python interpreter and the whole Jupyter stack.