User Tools

Site Tools


mozilla-devel:building_the_staff_client

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
mozilla-devel:building_the_staff_client [2012/09/11 10:46] – Adding Mac App Directions mrpetersmozilla-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 is built as part of the "make install" process in a normal load. One can also build one by going to the Open-ILS/xul/staff_client directory and typing "make build". There are a number of options that can be specified, either during "make install" or "make build".+The staff client server side components are built as part of the "make install" process in a normal load. One can also build them by going to the Open-ILS/xul/staff_client directory and typing "make build". There are a number of options that can be specified, either during "make install" or "make build"
 + 
 +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
 </code> </code>
  
Line 62: Line 64:
 </code> </code>
  
-This replaces older STAFF_CLIENT_BUILD_ID='' instructions for creating such a client.+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.  This can be useful if you want to install multiple clients on one machine and not share preferences between the versions.
 +
 +From staff_client directory:
 +<code bash>
 +make STAFF_CLIENT_NAME='' build
 +</code>
 ====== Branding Options ====== ====== Branding Options ======
  
Line 89: Line 100:
 <code bash> <code bash>
 make rebuild make rebuild
 +</code>
 +
 +===== Initial Hostname =====
 +
 +To set an initial staff client hostname.
 +
 +During making the staff client:
 +
 +<code bash>
 +make INITIAL_HOST=hostname build
 +</code>
 +
 +During Evergreen configure:
 +
 +<code bash>
 +./configure --with-initialhost=hostname
 </code> </code>
  
Line 184: Line 211:
 </code> </code>
  
 +==== Custom Install Directory ====
 +If you wish to customize the install directory for your windows client.  This can be useful if you 
 +want to run multiple staff clients on one machine without them interacting with each other. Edit the staff_client/windowssetup.nsi file and change the PRODUCT_TAG to a custom value.
 +
 +<code>
 +;!define /file PRODUCT_VERSION "client/VERSION"
 +!define PRODUCT_TAG "Test-2.8"
 +!define PRODUCT_INSTALL_TAG "${PRODUCT_TAG}"
 +!define UI_IMAGESET "beta"
 +;!define UI_IMAGESET "release"
 +!define PRODUCT_NAME "Evergreen Staff Client ${PRODUCT_TAG}"
 +</code>
 +
 +Now the default install directory will be c:\%PROGRAMFILES(x86)%\Evergreen Staff Client Test-2.8.  Build the staff client after this change is made to activate it.
 ===== 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" will be created.+If you build the 32-bit version, the output file "evergreen_staff_client_i686.tar.bz2" will be created
 +for 64-bit version the output is "evergreen_staff_client_x86_64.tar.bz2"
  
 <code bash> <code bash>
-make linux-client+make linux32-client 
 +make linux64-client
 </code> </code>
  
Line 289: 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.
  
  
Line 316: Line 359:
         <string>xulrunner</string>         <string>xulrunner</string>
         <key>CFBundleGetInfoString</key>         <key>CFBundleGetInfoString</key>
-        <string>OpenILS open_ils_staff_client rel_1_6_0_0</string>+        <string>OpenILS open_ils_staff_client rel_2_7_5</string>
         <key>CFBundleInfoDictionaryVersion</key>         <key>CFBundleInfoDictionaryVersion</key>
         <string>6.0</string>         <string>6.0</string>
Line 324: Line 367:
         <string>APPL</string>         <string>APPL</string>
         <key>CFBundleShortVersionString</key>         <key>CFBundleShortVersionString</key>
-        <string>rel_1_6_0_0</string>+        <string>rel_2_7_5</string>
         <key>CFBundleVersion</key>         <key>CFBundleVersion</key>
-        <string>rel_1_6_0_0.rel_1_6_0_0</string>+        <string>rel_2_7_5.rel_2_7_5</string>
         <key>NSAppleScriptEnabled</key>         <key>NSAppleScriptEnabled</key>
         <true/>         <true/>
- <key>CFBundleTypeIconFile</key>+ <key>CFBundleIconFile</key>
         <string>Evergreen.icns</string>         <string>Evergreen.icns</string>
 +        <key>CFBundleIdentifier</key>
 +        <string>org.evergreen-ils.Evergreen</string>
 </dict> </dict>
 </plist> </plist>
 </code> </code>
  
-  - Download and install an appropriate Mac OS package of XULRunner from the Mozilla website (This varies from version to 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 /Library/Frameworks/XUL.Framework inside your app file, it should look something like this:   - Make a copy of /Library/Frameworks/XUL.Framework inside your app file, it should look something like this:
     * Evergreen.app/     * Evergreen.app/
Line 342: Line 387:
           * XUL.Framework/           * XUL.Framework/
             * Versions/             * Versions/
-              * Current -> 1.9.2.28 (symlink) +              * Current -> 14.0.(symlink) 
-              * 1.9.2.28/+              * 14.0.1/
             * XUL -> Versions/Current/XUL             * XUL -> Versions/Current/XUL
             * libxpcom.dylib -> Versions/Current/libxpcom.dylib             * libxpcom.dylib -> Versions/Current/libxpcom.dylib
             * xulrunner-bin -> Versions/Current/xulrunner-bin             * xulrunner-bin -> Versions/Current/xulrunner-bin
-  - copy XUL.Framework/Versions/Current/xulrunner into Evergreen.app/MacOS (do not symlink, copy the file)+  - copy XUL.Framework/Versions/Current/xulrunner into Evergreen.app/Contents/MacOS (do not symlink, copy the file)
   - Make Evergreen.app/Resources the root of your Evergreen application files like this:   - Make Evergreen.app/Resources the root of your Evergreen application files like this:
     * Evergreen.app/     * Evergreen.app/
Line 357: Line 402:
           * components/           * components/
           * etc.           * etc.
 +   - Finally, Put a Mac format icon file named [[http://evergreen-ils.org/~csharp/Evergreen.icns|Evergreen.icns]] in Resources 
  
-  Put a Mac format icon file named Evergreen.icns in Resources  +{{:mozilla-devel:structure.png?300|}}
-  - To stylize the installer, like the example below, [[http://mac101.net/content/how-to/how-to-create-dmg-art-for-fancy-application-installations/]] has great information on styling, and ultimately compressing the installer image.  The Evergreen background is provided below, as well.+
  
 +To stylize the installer, like the example below, [[http://mac101.net/content/how-to/how-to-create-dmg-art-for-fancy-application-installations/]] has great information on styling, and ultimately compressing the installer image.  The Evergreen background is provided below, as well.
  
 +{{:mozilla-devel:installer.png?300|}}
 +{{:mozilla-devel:background.png|}}
mozilla-devel/building_the_staff_client.1347374768.txt.gz · Last modified: 2022/02/10 13:33 (external edit)

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.