`v6.10.0` is not compatible with projects that are built and used in different locations
Closed this issue · 1 comments
birdofpreyru commented
It turns out PR #42 is not compatible with projects that are meant to be build in one location, and used in another. This is because it effectively injects into compiled code the absolute path to getClassName at the moment of compilation; which will be invalid if compiled project is moved to a different location.
Thus, I recommend to use the previous release, v6.9.4 for now; until I find time to investigate how to solve the problem solved by PR #42 without causing the problem it introduced.
birdofpreyru commented