Added the proper link to show what is blocked.

I think we can start with a static library, if that turns out to be simpler

David.Hall, the collation code is in "strings" library, which depends on , or rather like interdepends on mysys and dbug.
In CMake, you'd need to
TARGET_LINK_LIBRARIES(your_binary strings)

I would not do that in storage engine code, since it can use symbols from the server. But in an executable it should work.
Any reason you can't use static library?

Part of the code is in mysys, so one might need TARGET_LINK_LIBRARIES(your_binary mysys) too.

There's no reason we can't use a static lib. If it makes it easier for you, lets do it that way.
We can link whatever libs we need, so long as I can find them at link time. I don't think code bloat will be an issue here.

Code bloat is not an issue, those libraries are rather tiny. David.Hall, should be keep the issue open, or can we close this, if static linking works for you?

If the libs are ready, this can be closed. I may need to bother you if I have problems getting things to link. Probably won't have a problem, but you never know.

The libs are "strings", they are there, and always been, during the server build. The interdependency between strings and mysys is mentioned by serg, so one might need to link with mysys as well, and also with dbug.

Supporting collation/charset code is in mysys — loading, comparing, compiling, etc. Actual collations/charsets are in string.

I'm closing it for now. Hopefully there is no problems with proposed solution (static libs)