From 6825fa740f82701a69e7f3f0182ff363b81df61d Mon Sep 17 00:00:00 2001 From: Sam Hartman Date: Fri, 14 Feb 2014 14:03:03 -0500 Subject: [PATCH] Updates for autoconf --- release/test.mdwn | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/release/test.mdwn b/release/test.mdwn index cfd9d2e..2334f92 100644 --- a/release/test.mdwn +++ b/release/test.mdwn @@ -5,8 +5,8 @@ Security's test infrastructure. Log into moonbuild (10.1.10.11) and check out a tree. Below we check out a writable tree, because you'll probably end up making some changes: - ssh -A username@10.1.10.11 - git clone username@moonshot.suchdamage.org:/srv/git/moonshot.git + ssh -A @10.1.10.11 + git clone @moonshot.suchdamage.org:/srv/git/moonshot.git this will leave you on the master branch of the [[Moonshot repository|branches]]. However, to build Debian test packages, you want to be on the debian branch. So: @@ -16,9 +16,9 @@ However, to build Debian test packages, you want to be on the debian branch. So git submodule update --init Now, merge in the changes you want to test. -Let's say that you're updating moonshot itself and that your changes are already on master. +Let's say that you're updating moonshotUI and that your changes are already on master. - cd moonshot + cd ui git merge origin/master Now we'll need to update the debian version number so we can do a fresh build: @@ -27,6 +27,12 @@ Now we'll need to update the debian version number so we can do a fresh build: This will pull up an editor. Describe the change. You will be modifying debian/changelog. We will not commit this file because we're just generating test packages. +You probably want to run: + + autoreconf -f -i + +To regenerate configure scripts. + Change back to the root of your checkout of the master repository. Now, we want to disable stripping and optimization for our builds: @@ -37,9 +43,11 @@ Now would be a good time to remove the "debian_build" directory if it has conten And run the builds - ./debian-builder -s -c -s wheezy-i386 -s --arch=i386 -s -A directories + ./debian-builder -s -c -s wheezy-i386 -s --arch=i386 -s -A The "-s" option gets repeated a lot because it passes the following option to sbuild, the Debian package build infrastructure. That will run an i386 (32-bit) build of the software using the wheezy-i386 (Debian 7.0) chroot (filesystem image). For directories include the directory of the software you're wishing to build. +The build summary will have a status of "successful" if the build is successful. Most failures result in a status of "attempted". + The output packages will be placed in the debian_build directory. Copy these to any test machines you like. You might like a loop something like -- 2.1.4