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
without modification or dependencies. If you are an end user, stop here, go download the
binary package, and use it. Enjoy it and have fun.
-Still with us? Then you must be a new member of the Citadel team and you're packaging
-the software for a new architecture or something. So here's what you have to do to build
-the binary:
+Still with us? Then you must be a new member of the build team. So here's what you have
+to do to build the binary:
1. Download the Citadel source tree (if you're reading this, you've already done that).
2. Install all system dependencies. The same ones needed for Easy Install are fine.
binary should be able to run. The distribution does not matter -- for example, a
binary built on Debian should run fine on Ubuntu or Red Hat or whatever -- but the C
library and other very base system libraries are only upward compatible, not downward
-compatible. For example, at the time of this writing, I am building on Ubuntu 14 and
-it's early 2021.
+compatible. For example, at the time of this writing, I am building on Ubuntu 16 and
+it's early 2021.
projects / citadel.git / blobdiff