devel:compile-unix-xuvbuild [2010/05/13 00:02]
mario removed aptitude calls, users should rather stick to chroot page |
devel:compile-unix-xuvbuild [2010/07/17 23:59] (current)
mario updated many details to current HEAD of xuvbuild script |
| | == Directory Layout == | | == Directory Layout == |
| | | | |
| - | The next steps should be getting the sources and installing them in the correct directories. It is highly recommended to stick to the following directory layout, where USER is the username of the active user (Call 'whoami' to find your user name). | + | The next steps should be getting the sources and installing them in the correct directories. It is highly recommended to stick to the following directory layout, where USER is the username of the active user (call 'whoami' to find your user name). |
| | | | |
| | <code> | | <code> |
| | <code> | | <code> |
| | source XuvTools/trunk/xuvtools/scripts/env-lmb.sh | | source XuvTools/trunk/xuvtools/scripts/env-lmb.sh |
| - | </code> | |
| - | | |
| - | == Compiling Thirdparty Prerequisites == | |
| - | | |
| - | Compiling the thirdparty prerequisites is required only the first time (or whenever there are updates). Currently, these prerequisites are the Qt library only. | |
| - | | |
| - | <code bash> | |
| - | cd thirdparty/ | |
| - | make | |
| | </code> | | </code> |
| | | | |
| | == Starting the XuvTools Compile == | | == Starting the XuvTools Compile == |
| | | | |
| - | Finally, you can now use the "xuvbuild.sh" script to compile the sources. When compiling the sources for the first time, you need to use the parameter "--qmake" to generate the Makefiles. For a first run it also recommended to use the parameter "--genfirst". Here is a sample run for compiling the first time: | + | Finally, you can now use the "xuvbuild.sh" script to compile the sources. When compiling the sources for the first time, you need to use the parameter "--qmake" to generate the Makefiles. For a first run it also recommended to use the parameter "--genfirst". Compiling the thirdparty prerequisites is required only the first time (or whenever there are updates). Thirdparty compilation is activated with the "--thirdparty" switch. Here is a sample run for compiling the first time: |
| | | | |
| | <code> | | <code> |
| - | emmenlau(decuman) ~/XuvTools/trunk> xuvtools/scripts/xuvbuild.sh --help | + | emmenlau(decuman) ~/XuvTools/trunk> xuvbuild.sh --help |
| | usage: xuvbuild.sh | | usage: xuvbuild.sh |
| | [--verbose|-v] - be more verbose (default=0) | | [--verbose|-v] - be more verbose (default=0) |
| | [--jobs|-jobs] - number of parallel jobs (default=autodetect) | | [--jobs|-jobs] - number of parallel jobs (default=autodetect) |
| | | | |
| - | emmenlau(decuman) ~/XuvTools/trunk> xuvtools/scripts/xuvbuild.sh --verbose --qmake --genfirst | + | emmenlau(decuman) ~/XuvTools/trunk> xuvbuild.sh --verbose --qmake --tools --thirdparty |
| | </code> | | </code> |
| | | | |
| - | Here is a sample run for compiling all additional times: | + | Here is a sample run for compiling all future times: |
| | | | |
| | <code> | | <code> |
| | emmenlau(decuman) ~/XuvTools/trunk> xuvbuild.sh --verbose | | emmenlau(decuman) ~/XuvTools/trunk> xuvbuild.sh --verbose |
| | </code> | | </code> |
| | + | |
| | + | ==== XuvTools Releases ==== |
| | + | |
| | + | XuvTools releases are packaged with a simple shell script. The script will package the XuvTools release automatically, and include the Java runtime environment and other dependencies. |
| | + | |
| | + | == Packaging a XuvTools Release == |
| | + | |
| | + | Depending on the platform, you can use one of currently three packaging scripts: xuvpackage-win.sh, xuvpackage-mac.sh or xuvpackage-lin.sh. Here we demonstrate xuvpackage-lin.sh: |
| | + | |
| | + | <code> |
| | + | emmenlau(decuman) ~/XuvTools/trunk> xuvpackage-lin.sh --verbose --version=<versionnr> |
| | + | </code> |
| | + | |
| | + | This will create a new packaged release in your XuvTools/trunk/releases/ directory. |
| | | | |