Could anyone share experience on how to distribute a C++ wrapper through package manager?
My workflow idea is the following:
package is available from a third-party registry
wrapped library and C++ shim are packaged in binary form and available from the same registry
Given that the shim depends on the wrapped library and the Julia module needs to load the shim first to work, what would be the recommended way to specify the paths to the corresponding artifacts?
Yes, I think so too but so far I don’t have experience with that.
Say, I’ve managed to build a JLL for a binary library.
Now, how should I get the path to the .so file associated with it? Would it be exported in JLL or maybe it’s going to be a fixed path relative to JULIA_DEPOT_PATH?
I was thinking too if it would be logical to package both wrapper and the original library into a single JLL. Thanks for pointing to a way how it may be done!
I think my problem is related to the original question, but not exactly the same. I cannot figure out how I would be packaging (i.e. publishing on the registry) a CxxWrap based project that needs a Visual studio build of libcxxwrap-julia. When CxxWrap is installed on Windows, it pulls in a Mingw build of libcxxwrap-julia, which is not compatible with the glue that I need, since I am wrapping a Visual Studio built library (this is a given). What magic do I need in my project to make CxxWrap not load the Mingw version, or am I asking the wrong question.