Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
| dev:building_the_standalone_client [2011/04/17 20:56] – rmzelle | dev:building_the_standalone_client [2011/04/17 20:59] – [Building the Standalone Client] rmzelle |
|---|
| - Non-source inputs: XULRunner. ''build_sa'' mentions a requirement for XULRunner runtime 2.0.*. However, Ubuntu does not package a 2.x XULRunner before [[https://wiki.ubuntu.com/NattyNarwhal|11.04]], which is currently pre-release. For now, Pre-release xulrunner-2.x runtimes can be obtained from http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/latest-trunk/. ''build_sa'' states implicitly that it requires separate runtimes for each target architecture, and expects to find each such runtime in a directory with a conventional name (see bash scriptlet below). | - Non-source inputs: XULRunner. ''build_sa'' mentions a requirement for XULRunner runtime 2.0.*. However, Ubuntu does not package a 2.x XULRunner before [[https://wiki.ubuntu.com/NattyNarwhal|11.04]], which is currently pre-release. For now, Pre-release xulrunner-2.x runtimes can be obtained from http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/latest-trunk/. ''build_sa'' states implicitly that it requires separate runtimes for each target architecture, and expects to find each such runtime in a directory with a conventional name (see bash scriptlet below). |
| - Build control: ''build_sa'' uses no config file, takes no arguments, and is non-interactive. ''build_sa'' will build one or more of the target OSs (''linux'', ''mac'' or ''win32''), but it decides which architectures are built for each. | - Build control: ''build_sa'' uses no config file, takes no arguments, and is non-interactive. ''build_sa'' will build one or more of the target OSs (''linux'', ''mac'' or ''win32''), but it decides which architectures are built for each. |
| - Running the built sa (as opposed to running the build): after building, and some perusal of (e.g.) the output of ''ls -alt ${BUILD_PATH} $(find -executable -type f) | grep -ve '.so$''', I found ''${BUILD_PATH}/Zotero_${BUILD_ARCH}/zotero''. | - Location of the build: ''${BUILD_PATH}/Zotero_${BUILD_ARCH}/zotero'' (found with ''ls -alt ${BUILD_PATH} $(find -executable -type f) | grep -ve '.so$'''). |
| |
| ===== Bash Scriptlet ===== | ===== Bash Scriptlet ===== |
Upgrade Storage