| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| dev:building_the_standalone_client [2011/04/17 20:59] – [Building the Standalone Client] rmzelle | dev:building_the_standalone_client [2011/04/17 21:14] – [Building the Standalone Client] rmzelle |
|---|
| - Build prerequisites | - Build prerequisites |
| - Tools: ''subversion'', ''bash'' and ''perl'' | - Tools: ''subversion'', ''bash'' and ''perl'' |
| - 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 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. |
| - Location of the build: ''${BUILD_PATH}/Zotero_${BUILD_ARCH}/zotero'' (found with ''ls -alt ${BUILD_PATH} $(find -executable -type f) | grep -ve '.so$'''). | - Location of the build: ''${BUILD_PATH}/Zotero_${BUILD_ARCH}/zotero'' (found with ''ls -alt ${BUILD_PATH} $(find -executable -type f) | grep -ve '.so$'''). |
| Building Zotero_linux-x86_64</code> | Building Zotero_linux-x86_64</code> |
| |
| The run step puts up a zotero window similar to that normally seen in Firefox. When initially run separately from the terminal, it produced the output | The run step puts up a Zotero window similar to that normally seen in Firefox. When initially run separately from the terminal, it produced the output |
| |
| <code>$ ./Zotero_linux-x86_64/zotero & | <code>$ ./Zotero_linux-x86_64/zotero & |
| but I have not observed that subsequently. | but I have not observed that subsequently. |
| |
| Unfortunately I don't currently know how to test the built sa (much less from Chrome) aside from the following smoketest: if I | Unfortunately I don't currently know how to test the build (much less on how to use it with Chrome) aside from the following smoketest: if I |
| - Run the executable (e.g., ''${ZOTERO_TARGET_EXEC}'', ''./Zotero_linux-x86_64/zotero''). | - Run the executable (e.g., ''${ZOTERO_TARGET_EXEC}'', ''./Zotero_linux-x86_64/zotero''). |
| - Wait for the zotero window, then select "Zotero Quick Start" in its middle pane. | - Wait for the Zotero window, then select "Zotero Quick Start" in the center column. |
| - Hit button=View in the rightmost pane. | - Hit button=View in the right column. |
| |
| a browser launches and and opens the [[/support/quick_start_guide|quick start guide]]. That's comforting, but I'd prefer to know: | a browser launches and and opens the [[/support/quick_start_guide|quick start guide]]. That's comforting, but I'd prefer to know: |
| |
| - Is there a more extensive test suite? E.g., what do youse do pre-commit? | - Is there a more extensive test suite? E.g., what do the Zotero development team do pre-commit? |
| - How to load up my own (backed up) Zotero data (from my Firefox profile, or wherever else it might be) and do actual work? | - How to load up my own (backed up) Zotero data (from my Firefox profile, or wherever else it might be) and do actual work? |
Upgrade Storage