diff options
Diffstat (limited to 'cpp')
| -rw-r--r-- | cpp/install/rpm/README.DEMOS | 91 | ||||
| -rw-r--r-- | cpp/install/rpm/README.RPM | 29 |
2 files changed, 62 insertions, 58 deletions
diff --git a/cpp/install/rpm/README.DEMOS b/cpp/install/rpm/README.DEMOS index cca621d0c36..ca460ff0009 100644 --- a/cpp/install/rpm/README.DEMOS +++ b/cpp/install/rpm/README.DEMOS @@ -2,45 +2,47 @@ Building the Ice Demos ====================== For your convenience, the Ice demo distribution includes all of the -demos included in the Ice source distributions. These demos may be +demos included in the Ice source distributions. These demos may be built against a pre-existing Ice distribution. If you installed Ice from RPM packages, you can build the demos by -visiting each demo directory (e.g. demo, demoj, democs) and running -'gmake' or 'ant' as appropriate. The Ice for Python demos do not need +visiting each demo directory (e.g., demo, demoj, democs) and running +'gmake' or 'ant' as appropriate. The Ice for Python demos do not need to be compiled. -If you installed Ice from an Ice binary distribution or for source +If you installed Ice from an Ice binary distribution or from source distributions by running 'gmake install', you must set the ICE_HOME -environment variable to the location you installed Ice. You must also +environment variable to the Ice installation directory. You must also tell your system where to find the Ice translators and shared libraries. -This is normally done through environment variables. On most systems +This is normally done through environment variables. On most systems the translators should be in a directory in your PATH environment -variable. The shared libraries should be in a directory in your -system's shared library search path. This is usually done through a -system specific environment variable, such as LD_LIBRARY_PATH (Linux and -other UNIX variants), SHLIB_PATH (32 bit HP-UX) and LIBPATH (IBM AIX). -You can test whether you have configured your system properly by running -a Slice translator that was installed on your system. For example: +variable, and the shared libraries should be in a directory in your +system's shared library search path. Shared libraries are located +using a system-specific environment variable, such as LD_LIBRARY_PATH +(Linux and other UNIX variants), SHLIB_PATH (32 bit HP-UX) and LIBPATH +(IBM AIX). You can test whether you have configured your system +properly by running a Slice translator that was installed on your +system. For example: myprompt> slice2cpp Without arguments, the translator will display some usage help -information. If you get a 'command not found' or 'libIce.so.2.1.0 not -found' or similar error, verify the files are in the expected location, -your environment variables are set properly and that you have the proper -permissions on these files. +information. If you get a 'command not found' or 'libIce.so.2.1.0 not +found' or similar error, verify that the files are in the expected +location, your environment variables are set properly and that you +have the proper permissions on these files. To verify ICE_HOME is set, simply echoing the environment variable works -on most systems. Assuming Ice is installed in /opt/Ice: +on most systems. Assuming Ice is installed in /opt/Ice: myprompt> echo $ICE_HOME /opt/Ice -Once you've verified that you have your environment configured -correctly, you can build the demos by visiting each demo directory and -running 'gmake' or 'ant' as appropriate. The Ice for Python demos do -not need to be compiled. +Once you have verified that your environment is configured correctly, +you can build the demos by visiting each demo directory and running +'gmake' or 'ant' as appropriate. The Ice for Python demos do not need +to be compiled. + Running the Ice Demos ===================== @@ -51,43 +53,44 @@ run the demos. Ice for C++ ----------- -The C++ demos the Ice runtime and tools as well as several third party -libraries. If you have managed to build the C++ demos, you already have -your environment set up properly for the Ice runtime. However, Ice uses -other third party libraries such as OpenSSL that should also be -accessible. +The C++ demos require the Ice runtime and tools as well as several third +party libraries. If you have managed to build the C++ demos, you already +have your environment set up properly for the Ice runtime. However, +Ice uses other third party libraries such as OpenSSL that should +also be accessible. Ice for Java ------------ -The Java demos require that you have the Ice.jar, the Ice ant tasks and -the Berkeley DB db.jar in your CLASSPATH. If Ice was installed from -RPMs, Ice.jar and the ant tasks are in /usr/lib/Ice-(the Ice version -number)/Ice.jar and /usr/lib/Ice-(the Ice version number)/ant, -respectively. Otherwise, Ice.jar and the ant tasks will be in the Ice +The Java demos require that you have the Ice.jar, the Ice ant tasks +and the Berkeley DB db.jar in your CLASSPATH. If Ice was installed +from RPMs, Ice.jar and the ant tasks are in /usr/lib/Ice-(the Ice +version number)/Ice.jar and /usr/lib/Ice-(the Ice version number)/ant, +respectively. Otherwise, Ice.jar and the ant tasks will be in the Ice installation's lib and ant directories, respectively. Ice for C# ---------- To run the C# demos under Mono, you must include the library directory -containing the icecs.dll in your MONO_PATH environment variable. In an +containing the icecs.dll in your MONO_PATH environment variable. In an RPM installation, the icecs.dll is installed in the /usr/lib directory. -It may otherwise be found in the lib directory in your Ice installation. +Otherwise, it can be found in the lib directory in your Ice +installation. Ice for Python -------------- To run the Python demos, the Ice Python modules and the Ice Python -extension must be in the PYTHONPATH environment variable. You also need -to configure the ICEPY_HOME environment variable to indicate your Ice -for Python installation. If you installed Ice for Python from a Ice -binary distribtion, it should be the same as your ICE_HOME environment -variable. If you installed Ice for Python from the source distrbution, -you may have installed it in a directory other than the ICE_HOME -directory. - -For RPM installations, the enviroment variables should be: +extension must be in the PYTHONPATH environment variable. You also +need to configure the ICEPY_HOME environment variable to indicate your +Ice for Python installation. If you installed Ice for Python from an +Ice binary distribution, it should be the same as your ICE_HOME +environment variable. If you installed Ice for Python from the source +distribution, you may have installed it in a directory other than the +ICE_HOME directory. + +For RPM installations, the environment variables should be: ICEPY_HOME=/usr PYTHONPATH=/usr/lib:/usr/lib/Ice-(the Ice version)/python:[other non-ice components] @@ -95,12 +98,12 @@ components] For non-RPM installations, the environment variables should be: ICEPY_HOME=/opt/IcePy-(the Ice version) -PYTHONPATH=/opt/IcePy-(the Ice version)/lib:/opt/IcePy-(the Ice version)python: +PYTHONPATH=/opt/IcePy-(the Ice version)/lib:/opt/IcePy-(the Ice version)/python: [other non-ice components] -- or -- ICEPY_HOME=/opt/Ice-(the Ice version) -PYTHONPATH=/opt/Ice-(the Ice version)/lib:/opt/Ice-(the Ice version)python: +PYTHONPATH=/opt/Ice-(the Ice version)/lib:/opt/Ice-(the Ice version)/python: [other non-ice components] diff --git a/cpp/install/rpm/README.RPM b/cpp/install/rpm/README.RPM index 5dd35d765a8..7cdce66a56b 100644 --- a/cpp/install/rpm/README.RPM +++ b/cpp/install/rpm/README.RPM @@ -2,18 +2,19 @@ Creating RPM packages for Ice ============================= As well as being able to download prebuilt RPM packages, Ice now -includes a sample RPM specification file that can be used to create your -own RPMs. Using this specification file and the Ice source and demo -distributions, you can create specialized RPMs with compiler settings, -remove or add components or even change the installation directory -structure to suit your needs. You can also use the specification file -to create your own source RPM package. +includes a sample RPM specification file that can be used to create +your own RPMs. Using this specification file and the Ice source and +demo distributions, you can create specialized RPMs with different +compiler settings, custom component configurations or even a +reorganized installation directory structure to suit your needs. You +can also use the specification file to create your own source RPM +package. -The sample specification file is for a complete set of Ice RPMs. In -order to properly build all of these packages, you need the full set of -system requirements for all of the packages. See each Ice distribution for -specific package and version requirements for this version of Ice. In -general you need: +The sample specification file is for a complete set of Ice RPMs. In +order to properly build all of these packages, you need the full set +of system requirements for all of the packages. See each Ice +distribution for specific package and version requirements for this +version of Ice. In general you need: * bzip2 * openssl @@ -24,8 +25,8 @@ general you need: * Python * Java Development Kit -In order to build the RPMs, you need to download each source distributon -and copy or move them to your system's RPM sources directory. For -example, /usr/src/redhat/SOURCES. +In order to build the RPMs, you need to download each source +distribution and copy or move them to your system's RPM sources +directory. For example, /usr/src/redhat/SOURCES. This RPM specification file was tested with RPM version 4.3.2. |