OpenVisus installs files back into the build directory
yurivict opened this issue · 4 comments
Instructions like this cause files to be installed into build directory. like this file:
/disk-samsung/freebsd-ports/science/openvisus/work/.build/Release/OpenVisus/include/Gui/Visus/ArrayStatisticsView.h
This install instruction should look like this:
INSTALL(DIRECTORY Libs/Kernel/include DESTINATION include/OpenVisus)
In its current form OpenVisus can't be installed into a standard file hierarchy with bin/include/lib/share directories.
OpenVisus install is heavily customized and not very standard (mainly due to the fact that is a C++ library and Python package).
It builds and installs using local directories (i.e. inside build).
It creates python packages (several combinations: PIP, conda, with-or-without GUI); it deploys packages (to PyPi, conda, Docker, etc).
After that, users usually only install binary artifacts.
Most of the time you can overcome this limitation by export PYTHONPATH=... or just copying the build directory.
Many software packages so the same - they build C++ libraries, Python libraries on top of C++ libraries, then they distribute Python libraries on PyPI, Conda and what have you, and they are still buildable and installable into standard locations.
What makes OpenVisus different that warrants such a radical deviation from standards?
Pull requests are welcome: the only requirement is that they don't break current deployments.
(first thing to check is that unit-testing passes and PyPI/conda packages are produced).
will get back to this soon. This is important.