-
Notifications
You must be signed in to change notification settings - Fork 14
Automatically build key portions of AppImageKit #13
Conversation
olekw
commented
Mar 31, 2014
- Build only the portion necessary for creating Ember AppImages
- Use the resulting AppImageKit components to create the Ember AppImage
- This will remove the requirement to install/compile AppImageKit manually
- Minor cleanup/adjustment of existing AppImage code
I was going to write up the new process for building an AppImage to post on the wiki but it's not simple, and I'm lazy... so instead I modified hammer to take care of all the AppImage stuff internally. ;) Shell scripts are more fun to write than wiki pages and this will make the wiki page MUCH easier to write! |
Oh, almost forgot, there are two additional package dependencies with this change: xorriso and python-xdg. Don't think either should be a problem for any major GNU/Linux distro. |
echo " ogre - 3D rendering engine" | ||
echo " Hint: build ogre first then cegui" | ||
echo " cg - interactive effects toolkit" | ||
echo " AppImageKit - application packaging system" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer "appimagekit" to fit with the other options which are all lower case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, crap. That's a typo. The script already expects it to be lower case. I'll fix the "documentation"in the morning. It's past my bedtime now. ;-)
On March 31, 2014 1:45:17 AM CDT, Erik Ogenvik notifications@github.com wrote:
@@ -169,12 +169,13 @@ function show_help()
echo ""
echo "Usage: hammer.sh install-deps "
echo "Dependencies Available:"
- echo " all - install all dependencies listed below"
- echo " cegui - a free library providing windowing and
widgets for "- echo " graphics APIs / engines"
- echo " ogre - 3D rendering engine"
- echo " cg - interactive effects toolkit"
- echo "Hint: build ogre first then cegui"
- echo " all - install all dependencies listed below"
- echo " cegui - a free library providing windowing and
widgets for"- echo " graphics APIs / engines"
- echo " ogre - 3D rendering engine"
- echo " Hint: build ogre first then cegui"
- echo " cg - interactive effects toolkit"
- echo " AppImageKit - application packaging system"
I would prefer "appimagekit" to fit with the other options which are
all lower case.
Reply to this email directly or view it on GitHub:
https://github.com/worldforge/hammer/pull/13/files#r11105058
Sent from my Android device with K-9 Mail. Please excuse my brevity.
- Build only the portion necessary for creating Ember AppImages - Use the resulting AppImageKit components to create the Ember AppImage - This will remove the requirement to install/compile AppImageKit manually - Minor cleanup/adjustment of existing AppImage code
Ok, help screen updated. |
Running "./hammer.sh release_ember dev image" results in an error, but none is reported. The script finishes with this output: However, when looking at the logs AppDir.log says: and AppImage says: |
Possibly missing |
Erik, that path is from an older version of hammer. Could you try removing your hammer directory and re-cloning from the updated hammer? Let me know if that fixes the problem. |
David, the paths are different because this commit allows hammer to build the portions of AppImageKit that it needs, instead of using a separately compiled AppImageKit. |
- When creating an AppImage, certain libraries must be removed - The script will currently exit when it fails to delete such a library - The script should not exit if such a library was never present
Ok, just pushed that commit. |
Are you providing an AppImage for download and if so, where? |
We do provide AppImages of the latest release at https://sourceforge.net/projects/worldforge/files/Ember%20%28OGRE%20client%29/0.7.2/ We don't currently provide AppImages of the development version, mainly because we don't have a CI server setup. |
Thanks for the clarification, so I assume there is no support needed for generating the AppImage :-) |
We would be very happy for any help with working on the AppImage generation code. I haven't used it in a while, so I don't know how up to date it is. Presumably there's been developments in AppImage which we haven't kept us up to date with. |