A question for which I believe I know the answer, as I am currently embedding a statically linked libtiledb.a within a compiled python module.
If I wanted to make use of that same statically linked libtiledb.a within a build of TileDB-Py, I am guessing I would need to add the same entries to the
extra_link_args and other arguments to
Extension that I am currently using within my own compiled python module. I assume I would also need to avoid using the current
I know the python api is under active development. Is working from a personal fork of TileDB-Py with a replacement setup.py file the most reasonable means of packaging a statically linked library?
Any particular gotchas that you all can think of?