-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Module path is broken #308
Comments
Fix is to revert 776534b, however there might be other related issues as we still get
It is also possible to fix the issue by copying the required *.so's to $BUILD/output. |
QString currentPath = QCoreApplication::applicationDirPath(); The idea was that if compiled it returns the output path otherwise the lib folders, I didn't run into issues with the linux installations here. |
No they are definitely not the same. However modules did not work otherwise, after a clean build (if executed from $build/output. Obviously it should work if we call dynamind from a random path, but IMHO this should also work if we did not install it. I think a straight-forward way would be to just have a $DYNAMIND_MODULES env variable that can be used to include third-party modules. Built-In modules (i.e. modules that are in the tree, basic-modules/ *, dynavibe/ *, gdalmodules/ *) are just expected to be in $build/modules and can be savely loaded by determining the executable's path. If this is non-trivial we might wrap it via a script like the following and read out $DYNAMIND_HOME at runtime, something like
|
The executable (no GUI) can not find any modules. This regression is probably introduced via 776534b.
The text was updated successfully, but these errors were encountered: