From 7f6002caba3f0a6749820c2772161caf55b8d267 Mon Sep 17 00:00:00 2001
From: neonloop
Date: Fri, 7 May 2021 20:00:12 +0000
Subject: Initial commit (uqm-0.8.0)

---
 build/unix/README.packages | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 build/unix/README.packages

(limited to 'build/unix/README.packages')

diff --git a/build/unix/README.packages b/build/unix/README.packages
new file mode 100644
index 0000000..68acfaf
--- /dev/null
+++ b/build/unix/README.packages
@@ -0,0 +1,31 @@
+This file describes the easiest way to use this build system from
+a packaging system such as rpm.
+
+If you want an interactive configuration, you can start the build process
+like you would do manually:
+	./build.sh uqm
+to build the game, and
+	./build.sh uqm install
+to install it.
+			
+
+If you want the configuration to be non-interactive, you'll want to do
+the following: execute
+	./build.sh uqm config
+once. This will generate a 'config.vars' file, which you can then
+include in your package. Then when you want to build the game, put this
+file the directory pointed to by $BUILD_WORK (default is the current
+directory), and do
+	./build.sh uqm reprocess_config
+to generate all the configuration information for the build, and then
+	./build.sh uqm
+to build the game, and
+	./build.sh uqm install
+to install it.
+
+You may wish to set the environment variable BUILD_WORK to a directory
+where the files created in the configuration and build process should be
+stored. That way, the source tree will remain clean and no write access
+to it is required.
+
+
-- 
cgit v1.2.3