-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
Distribution: Raw AppImage builder using Docker #912
Conversation
TODO: Fix Perl include paths
…some linking issues left to iron out
Thanks a lot Henrique ! I gave it a try and was able to build the AppImage but when executing it, I have the following message:
Is this what you mean with "invoke external executables without the environment variable mangling" or did I do something wrong ? |
I'm usually having no such file or directory instead of permission denied, strange... Anyways, this PR will take some more time to be ready, because of a lot of complexity:
So there's a LOT of stuff to iron out and make flexible, and there's a lot of code that's going to have to be changed to match. Then after I'm done there will be a lot of testing both inside and outside AppImage to ensure the changed pieces are working fine. About the permission denied problem, something somewhere is probably not marked as executable, I'm using WSL so maybe that has something to do with it, probably Windows "forces" execution even without the executable flag... |
…ame Perl interpreter and same AppImage env
The X11 problem didn't occur today even though I changed nothing locally, very strange. At least now the shell finally opens :) Just need to iron out this, current commit ignores the configuration option:
And then more extensive testing, of course. Also, sorry for not even saying on the PR how to build the docker image. I will edit it with the information. |
Does the AppImage work for you after these last changes? |
No joy :( Here is what I see if I run it on the same machine:
It looks like we are not using the right version of perl or using a "strict" mode or something ; I'm lost at this stage... |
I actually forgot a |
Oh yes, of course ... I see ; did not realize you made that many changes and that it was actually a "real" error ;) So, I did fix it locally, tried again and ... it works ! That looks like a great news :) I'll play around and we'll also need to see how we can automate this build in our Travis script. Thanks a lot. |
Good, nice to hear that it works there as well! I'll have the other TODOs patched up sometime this week probably. And documentation :x |
Both "shell directory" and "use login shell" settings work properly now. Still need to test more and check for strings used on anything that spawns a subprocess so that every one of those is checked for env variable prefixing, depending on what it does and what it invokes. |
… improve restart on config import
Seems stable and complete now. Missing docs for now |
Docs done 👀 |
Hi Henrique, Thanks again for the terrific work to get this working ! I made a test with the latest loki release and was able to create an AppImage with the latest loki code. It's working fine for me. The only little glitch I see is the following message for every terminal you want to start:
Any idea why I see this ? Can we do something about it ? I now need to see how we can build this automatically when we start our automated build. |
I couldn't reproduce that here, it seems some GTK module outside the AppImage is being picked up. From searching around about GTK module loading I saw some documentation about |
Try now on the branch, that |
Henrique, still searching for a way to publish the AppImage from our automated build... In the meantime, I created an entry on AppImageHub and uploaded manually: |
Is using a separate build orchestration an option, or does it need to be on the same Travis CI? I can try to integrate with Travis CI or GitHub Actions and post the resulting code, if it would help :)
Could you cherry-pick henry701@b95b324 and try again? It probably solves the issue you described here. |
Yes, certainly.
Well, adding this to Travis CI is fairly trivial if I would have a way to upload the build to AppImageHub (or anything else...).
Sure, will do. Thanks again for this great feature ! |
It works like a charm :) Thanks a lot ! I uploaded "apha-2" on https://www.appimagehub.com/p/1796061 |
Do not use external env XDG_DATA_DIRS and LD_LIBRARY_PATH as fallback
AppImage builder from scratch using Docker.
Closes #804.
PR here just for tracking, so far. It's still not working because Asbrú will need some code changes in order to invoke external executables without the environment variable mangling (that was done in order to run the AppImage with the correct relative paths of the embedded libs). More about the progress in the comments below.
To build the AppImage, you will need Docker installed and accessible from your POSIX shell. Then, just
cd
to the root directory of the project, and run:./dist/appimage-raw/make_appimage.sh
. It will be available on./dist/appimage-raw/build
.