Python tests do not work without AudioTK Python libraries installed #16
Comments
This ticket arose out of of issue #15. |
Thanks a lot! But it's a workaround only, I need to figure out a proper way to fix this. The refactoring to streamline the Python generation should help, as I can also generate the init.py file from them and then just rename the parent folder accordingly. |
Hey, |
When I run
I'm not sure whether this did in fact run the Python tests. |
Definitely didn't run the Python tests (they are prefixed with Py). |
I guess the output |
It comes from here actually: https://github.com/mbrucher/AudioTK/blob/master/CMakeLists.txt#L188 |
Still getting only 13 tests. This is my configuration / compilation sequence (in an up-to-date git checkout):
The output from cmake seems to indicate that the Python installation is found:
I'm out of my depth here with cmake and ctest. I'd need more specific instructions if I'm to test this further. BTW, the compilation output is incredibly noisy. Is there a way to reduce the number of warnings, especially the following:
|
I wonder if there is some remnant configuration somewhere... |
Same results.
The build process I use for AUR packages always starts with a fresh clone of of an up-to-date git checkout. |
Seems like everything should work. That's odd. I'll have to check a few things. |
I tried it on an embedded Linux and the latest develop version, it worked as expected, the tests did have all the Python scripts :/ |
The Python tests do not work without the Python libraries installed, so the test can not be run from the source or build tree without installing first, which is a problem e.g. for distribution packagers.
The reason is that they import the ATK modules in the form
from ATK.Xyz import xyz
, but the directory for the ATK python package is only created on installation of the modules. In the build tree there is noATK
directory and hence noATK
package. So even adding thebuild/Python
directory toPYTHONPATH
for the tests wouldn't work.I don't see a quick solution for this. IMHO either the build process should be altered in such a way that the modules are created in a proper package directory structure under
build/Python/ATK
or a testing environment should be used, that creates a temporary installation of the Python package (like e.g. tox.)The text was updated successfully, but these errors were encountered: