Here we document some of the issues we have encountered, so future development can be quicker
Table of Contents
- Visual Studio CMake Error
- Libs folder empty
- Latest version of libczi isn't present
- Pip install .all sticks
- Pip install or test fails with python version issue
- Pip install succeeds but tests fail to find interface
- Unable to add new interpreter to RMS_PyPi_pylibCZIrw
- Libs Submodule keeps showing a change
Visual studio build shows CMAKE_C_COMPILER and CMAKE_CXX_COMPILER error. This is because C/C++ tools for visual studio aren't installed. Use Visual Studio installer to modify current setup.
The library dependencies are linked using git submodules which have not been pulled.
Use git pull --recurse-submodules
The libczi library is a submodules which where the latest need to be referenced.
Use git submodule update --remote and keep the latest hash from libczi.
Pip version requires --use-feature=in-tree-build
run pip install --use-feature=in-tree-build .[all]
The virtual environment has some python version dependency, so change to that version of python using conda install python==<version_number>
If the python stub is created as expected, but python test run fails to find new interface, there is an issue with something broken in git
Open git bash on the repo and run git clean -fdx
If adding python interpreter using 'Add new interpreter -> Add local interpreter' fails, create a new conda environment using a new PyCharm window.
Then on open of the pylibCZIrw project, point the base python interpreter as the python.exe in the conda env
Ex: %USERPROFILE%\.conda\envs\pylibczi310\python.exe
If the libs folder keeps show changes, this could be due to an older version of a submodule being used. To clean this, run the commands below. The first command completely "unbinds" all submodules, the second then makes a fresh checkout of them. git submodule deinit -f . git submodule update --init