-
Notifications
You must be signed in to change notification settings - Fork 52
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
Make relocatable in the filesystem #311
Comments
In the meantime, super crude workaround (only used duing my own development):
|
You need to use
Setting
The Twinkle core is also used to build a non-GUI client, so it cannot depend on Qt, but I guess we could always check |
@fbiere, what I want to achieve is that it still works after renaming or moving Workaround:
|
While working on something completely unrelated, I just coincidentally discovered that the GUI client has a |
Thanks, will try it out.
Since we both didn't immediately discover it, this makes me wonder why it isn't the default... |
Because it needs an actual value, such as |
I see. I can make that work for my use case, even though it's a bit less elegant than "automagic" would be. Thanks! |
It would be nice if the application could run from paths other the one defined at compile time. This would allow one to put Twinkle into Mac-style
.app
bundles, ROX-style.AppDir
directories, and.AppImage
files.Currently we get
when we try to run Twinkle from a location other than the one that was defined at compile time:
This is because an absolute path to
DATADIR
https://github.com/LubosD/twinkle/search?q=DATADIR gets compiled in.It would be nicer if instead of compiling in
DATADIR
this would be figured out at runtimeQStringList QStandardPaths::standardLocations(QStandardPaths::AppDataLocation);
(using theXDG_DATA_DIRS
environment variable)QString QCoreApplication::applicationDirPath()
and constructing a path to../share/twinkle/
from thereThe text was updated successfully, but these errors were encountered: