AppImage format and how it works.
Again, do NOT try to run this on your production machine. For that matter, don't try to
-run it on anything other than a dedicated build host. It will ERASE /usr/local/citadel
-and /usr/local/webcit during the build process.
+run it on anything other than a dedicated build host. It may ERASE data you intended to
+keep.
If you're an end user you shouldn't have any need to do this at all. The whole point of
this is that we can supply ready-to-run binaries that will run on any Linux/Linux system
cc ctdlvisor.c -o citadel.AppDir/usr/bin/ctdlvisor || exit 1
cpu=`uname -p`
+basefilename=citadel-`date +%s`
if [ $cpu == x86_64 ] ; then
- ARCH=x86_64 appimagetool citadel.AppDir/
- md5sum Citadel-x86_64.AppImage | awk ' { print $1 } ' >Citadel-x86_64.AppImage.md5
+ ARCH=x86_64 appimagetool citadel.AppDir/ ${basefilename}-x64.appimage
+ md5sum ${basefilename}-x64.appimage | awk ' { print $1 } ' >${basefilename}-x64.appimage.md5
else
- ARCH=ARM appimagetool citadel.AppDir/
- md5sum Citadel-armhf.AppImage | awk ' { print $1 } ' >Citadel-armhf.AppImage.md5
+ ARCH=ARM appimagetool ${basefilename}.AppDir/ ${basefilename}-arm32.appimage
+ md5sum ${basefilename}-arm32.appimage | awk ' { print $1 } ' >${basefilename}-arm32.appimage.md5
fi