-
Notifications
You must be signed in to change notification settings - Fork 4
Installation and Setup
On all systems, it is possible to adjust the installation path by calling cmake as follows:
> cd /path/to/build
> cmake -DCMAKE_INSTALL_PREFIX:PATH=/path/to/install ..
The :PATH
seems only necessary on windows + powershell. It can be left out in other systems or shells.
The installation process is called from the powershell command-line with
> cd /path/to/build
> cmake --build . --config Release --target install
GUI users should build the install target.
All DCProgs files will go into a "dcprogs" folder under the CMAKE_INSTALL_PREFIX
folder.
It is now necessary to setup two environment variables:
- PYTHONPATH:
/path/given/to/cmake_install_prefix/dcprogs/python-pkg
should be added to it. This variable may not exist and may need to be created. - PATH:
/path/given/to/cmake_install_prefix/dcprogs/DLLs
should be added to it.
It should now be possible to run python and play with dcprogs.
NOTE: Windows does not seem to honor the user PATH. The best option is to move to a sensible and free OS. Otherwise, please set the system PATH.
The installation process should be launched from the MSYS command-line:
> cd /path/to/build
> make install
All DCProgs files will go into a "dcprogs" folder under the CMAKE_INSTALL_PREFIX
folder.
It is now necessary to setup two environment variables:
- PYTHONPATH:
/path/given/to/cmake_install_prefix/dcprogs/python-pkg
should be added to it. This variable may not exist and may need to be created. - PATH:
/path/given/to/cmake_install_prefix/dcprogs/DLLs;/path/to/MinGW/bin;/path/to/MinGW/lib
should be added to it. The last two paths make it possible for python to find and use dcprogs within and without the MSYS shell.
It should now be possible to run python and play with dcprogs.
The installation process should be launched from the command-line:
> cd /path/to/build
> make install
All DCProgs files will go into a "dcprogs" folder under the CMAKE_INSTALL_PREFIX
folder.
Assuming that it is /usr/
, then nothing further needs to be done (although it may require sudo power). Otherwise, one should modify the PYTHONPATH and the LD_LIBRARY_PATH (DYLD_LIBRARY_PATH on Mac) appropriately.