mozilla-devel:building_the_staff_client
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
mozilla-devel:building_the_staff_client [2011/01/20 12:44] – fix old world link, applies to 2.0 in general (but likely not to 2.1) tsbere | mozilla-devel:building_the_staff_client [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 7: | Line 7: | ||
====== Building the staff client ====== | ====== Building the staff client ====== | ||
- | The staff client | + | The staff client |
+ | |||
+ | See the instructions below for building the client packages for the staff client, which are not built by default. | ||
===== BUILD_ID ===== | ===== BUILD_ID ===== | ||
Line 31: | Line 33: | ||
During install: | During install: | ||
<code bash> | <code bash> | ||
- | make STAFF_CLIENT_VERISON=0mytest.200 install | + | make STAFF_CLIENT_VERSION=0mytest.200 install |
</ | </ | ||
Line 62: | Line 64: | ||
</ | </ | ||
- | This replaces older STAFF_CLIENT_BUILD_ID='' | + | This replaces older STAFF_CLIENT_BUILD_ID= instructions for creating such a client. |
+ | |||
+ | |||
+ | ===== STAFF_CLIENT_NAME ===== | ||
+ | |||
+ | If you wish to have a custom profile directory you can set the STAFF_CLIENT_NAME to something other than the default of STAFF_CLIENT_NAME=open_ils_staff_client. | ||
+ | |||
+ | From staff_client directory: | ||
+ | <code bash> | ||
+ | make STAFF_CLIENT_NAME='' | ||
+ | </ | ||
+ | ====== Branding Options ====== | ||
+ | |||
+ | Mainly for when you are making installers, windows installers in particular right now, you can set up branding for beta or release builds of Evergreen. This will change icons/ | ||
+ | |||
+ | This is done with the " | ||
+ | |||
+ | From staff_client directory (only run one): | ||
+ | <code bash> | ||
+ | make rigbeta | ||
+ | make rigrelease | ||
+ | </ | ||
+ | |||
+ | After running one or the other you should also build or [[# | ||
====== Advanced build options ====== | ====== Advanced build options ====== | ||
In addition to the basic options above there are a number of other options for building the staff client, pretty much all are make targets and thus require you to be building from the staff_client folder. | In addition to the basic options above there are a number of other options for building the staff client, pretty much all are make targets and thus require you to be building from the staff_client folder. | ||
+ | |||
+ | ===== Rebuild ===== | ||
+ | |||
+ | If run alone, or placed BEFORE any of the below options the staff client will be " | ||
+ | |||
+ | From the staff_client directory: | ||
+ | <code bash> | ||
+ | make rebuild | ||
+ | </ | ||
+ | |||
+ | ===== Initial Hostname ===== | ||
+ | |||
+ | To set an initial staff client hostname. | ||
+ | |||
+ | During making the staff client: | ||
+ | |||
+ | <code bash> | ||
+ | make INITIAL_HOST=hostname build | ||
+ | </ | ||
+ | |||
+ | During Evergreen configure: | ||
+ | |||
+ | <code bash> | ||
+ | ./configure --with-initialhost=hostname | ||
+ | </ | ||
===== Developer Build ===== | ===== Developer Build ===== | ||
Line 75: | Line 125: | ||
<code bash> | <code bash> | ||
make devbuild | make devbuild | ||
+ | </ | ||
+ | |||
+ | ===== Per-machine Registration Build ===== | ||
+ | |||
+ | A configuration variant for per-machine (instead of per-user) workstation registration and offline transaction storage can be built by replacing " | ||
+ | |||
+ | From the staff_client directory: | ||
+ | <code bash> | ||
+ | make permachine | ||
</ | </ | ||
Line 152: | Line 211: | ||
</ | </ | ||
+ | ==== Custom Install Directory ==== | ||
+ | If you wish to customize the install directory for your windows client. | ||
+ | want to run multiple staff clients on one machine without them interacting with each other. Edit the staff_client/ | ||
+ | |||
+ | < | ||
+ | ;!define /file PRODUCT_VERSION " | ||
+ | !define PRODUCT_TAG " | ||
+ | !define PRODUCT_INSTALL_TAG " | ||
+ | !define UI_IMAGESET " | ||
+ | ;!define UI_IMAGESET " | ||
+ | !define PRODUCT_NAME " | ||
+ | </ | ||
+ | |||
+ | Now the default install directory will be c: | ||
===== Linux Client ===== | ===== Linux Client ===== | ||
The linux client is merely a tar.bz2 file with xulrunner bundled with it. | The linux client is merely a tar.bz2 file with xulrunner bundled with it. | ||
- | The output file "evergreen_staff_client.tar.bz2" | + | If you build the 32-bit version, the output file "evergreen_staff_client_i686.tar.bz2" |
+ | for 64-bit version the output is " | ||
<code bash> | <code bash> | ||
- | make linux-client | + | make linux32-client |
+ | make linux64-client | ||
</ | </ | ||
Line 174: | Line 249: | ||
====== Staff Client Automatic Updates ====== | ====== Staff Client Automatic Updates ====== | ||
- | The staff client can be rigged to automatically update. | + | The staff client can be rigged to automatically update. In addition to the below you may wish to read [[mozilla-devel: |
===== WARNINGS ===== | ===== WARNINGS ===== | ||
Line 257: | Line 332: | ||
It may get confusing if you aren't careful, but you can log in to multiple evergreen servers at the same time, or a single evergreen server multiple times. In either case you will need to create an additional profile for each additional server or workstation you want to log in as (see previous tip). | It may get confusing if you aren't careful, but you can log in to multiple evergreen servers at the same time, or a single evergreen server multiple times. In either case you will need to create an additional profile for each additional server or workstation you want to log in as (see previous tip). | ||
- | Once you have done so, run xulrunner with the -no-remote command line option (in addition to -profilemanger or -P if neeeded). Instead of xulrunner opening a new login window on your existing session it will start a new session instead, which can then be logged in to a different server or workstation ID. | + | Once you have done so, run xulrunner with the -no-remote command line option (in addition to -profilemanger or -P if needed). Instead of xulrunner opening a new login window on your existing session it will start a new session instead, which can then be logged in to a different server or workstation ID. |
+ | |||
+ | |||
+ | ===== Building a Macintosh Staff Client ===== | ||
+ | |||
+ | - An app file is basically a folder. | ||
+ | * Evergreen.app | ||
+ | * Contents | ||
+ | * Frameworks | ||
+ | * Resources | ||
+ | * MacOS | ||
+ | eg: | ||
+ | <code sh> | ||
+ | mkdir -p Evergreen.app/ | ||
+ | mkdir -p Evergreen.app/ | ||
+ | mkdir -p Evergreen.app/ | ||
+ | </ | ||
+ | |||
+ | - Create a new file in Evergreen.app/ | ||
+ | <code xml> | ||
+ | <?xml version=" | ||
+ | < | ||
+ | <plist version=" | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | - Download and install an appropriate Mac OS package of XULRunner from the Mozilla website (you need xulrunner 14 for Evergreen 2.3+) | ||
+ | - Make a copy of / | ||
+ | * Evergreen.app/ | ||
+ | * Contents/ | ||
+ | * Frameworks/ | ||
+ | * XUL.Framework/ | ||
+ | * Versions/ | ||
+ | * Current -> 14.0.1 (symlink) | ||
+ | * 14.0.1/ | ||
+ | * XUL -> Versions/ | ||
+ | * libxpcom.dylib -> Versions/ | ||
+ | * xulrunner-bin -> Versions/ | ||
+ | - copy XUL.Framework/ | ||
+ | - Make Evergreen.app/ | ||
+ | * Evergreen.app/ | ||
+ | * Contents/ | ||
+ | * Resources/ | ||
+ | * BUILD_ID | ||
+ | * application.ini | ||
+ | * chrome/ | ||
+ | * components/ | ||
+ | * etc. | ||
+ | - Finally, Put a Mac format icon file named [[http:// | ||
+ | |||
+ | {{: | ||
+ | |||
+ | To stylize the installer, like the example below, [[http:// | ||
+ | {{: | ||
+ | {{: |
mozilla-devel/building_the_staff_client.1295545477.txt.gz · Last modified: 2022/02/10 13:33 (external edit)