Would it be possible to implement something to make it possible to specify a custom libindiclient.a path when installing pyindi-client?
It's a very interesting feature to embed "libindiclient.a" and "pyindi-client" in an application and not only in "/usr/lib/" + march, "/usr/lib", "/usr/lib64", "/lib", "/lib64", "/usr/local/lib/" + march and "/usr/local/lib".
To do so (and be compatible with both a "python setup.py install" and "pip install pyindi-client"), the solution is to add an environment variable (for example _INDICLIENTPATH):
...
if "LIBINDICLIENT_PATH" in os.environs:
libindisearchpaths.append(os.environs["LIBINDICLIENT_PATH"])
libindipath = ""
...
And regenerate setup.cfg:
[build_ext]
swig_opts = -v -Wall -c++ -threads -I<LIBINDICLIENT_PATH>/include/libindi
include_dirs = <LIBINDICLIENT_PATH>/include/libindi
library_dirs = <LIBINDICLIENT_PATH>/lib
libraries = cfitsio nova z
Dear pyindi-client deceloppers,
Would it be possible to implement something to make it possible to specify a custom libindiclient.a path when installing pyindi-client?
It's a very interesting feature to embed "libindiclient.a" and "pyindi-client" in an application and not only in "/usr/lib/" + march, "/usr/lib", "/usr/lib64", "/lib", "/lib64", "/usr/local/lib/" + march and "/usr/local/lib".
To do so (and be compatible with both a "python setup.py install" and "pip install pyindi-client"), the solution is to add an environment variable (for example _INDICLIENTPATH):
And regenerate setup.cfg:
Best regards, Jérôme