Changes between Initial Version and Version 1 of Installation

Show
Ignore:
Timestamp:
09/23/11 11:53:49 (20 months ago)
Author:
mgalloy
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Installation

    v1 v1  
     1{{{ 
     2#!rst 
     3Building 
     4======== 
     5 
     6The development version of the GNU Readline library is required to be 
     7installed before building rIDL. Most UNIX-based system will only have the 
     8Readline binaries installed by default. 
     9 
     10rIDL uses CMake for its build system. CMake can be installed via your system 
     11package management system or downloaded from `the CMake website 
     12<http://cmake.org>`_. 
     13 
     14In most cases, the only steps for building will be:: 
     15 
     16  cmake . 
     17  make 
     18  make install 
     19 
     20If you want to install somewhere besides the default location, then the 
     21``cmake`` command would look like:: 
     22 
     23  cmake -DCMAKE_INSTALL_PREFIX=install . 
     24 
     25CMake allows the locations of the libraries it needs to be specified also. For 
     26example, to specify a different location for Readline:: 
     27 
     28  cmake -DReadline_INCLUDE_DIR=/usr/local/readline/6.1/include \ 
     29        -DReadline_LIBRARY=/usr/local/readline/6.1/lib/libreadline.dylib \ 
     30        -DCMAKE_INSTALL_PREFIX=install \ 
     31        . 
     32 
     33In any case, `make install` will locate all the files rIDL will need at 
     34runtime in the proper relative locations. 
     35 
     36 
     37Installation 
     38============ 
     39 
     40After rIDL is built, a few aspects of your environment need to be set for rIDL 
     41to work correctly. 
     42 
     43The `share/idl` directory of the installation should in your `IDL_PATH`. This 
     44can also be set via the IDL Workbench preferences or the `PREF_SET` command, 
     45at the user's preference. 
     46 
     47Set the `RIDL_EDITOR` or the `EDITOR` environment variable to specify the 
     48editor to use with the ``.edit command``. For example, under the Bash shell 
     49this would be:: 
     50 
     51  export RIDL_EDITOR="emacs -nw" 
     52 
     53 
     54Optional Makefile targets 
     55========================= 
     56 
     57There are several optional Makefile targets that can be built from the source. 
     58 
     59More useful for end users, the `docs` target produces a PDF manual and man 
     60page for rIDL. If you want the system `man` command to find your man pages, 
     61make sure to add the `$INSTALL_DIR/man` to the `MANPATH` environment variable. 
     62 
     63Also, the `onlinehelp` target parses the IDL online help to produce text-based 
     64help system from within rIDL. To produce the documentation, use:: 
     65 
     66  make onlinehelp  
     67  make install 
     68   
     69To test the online help, from the rIDL prompt, try checking the help for an 
     70IDL routine with the `:help` magic command:: 
     71 
     72  rIDL> :help congrid 
     73 
     74The `apidocs` and `capidocs` targets are primarily for developers of rIDL to 
     75create API documentation for the rIDL source code. The `apidocs` target 
     76requires IDLdoc to be installed and in IDL's path; the `capidocs` target 
     77requires Doxygen to be installed. 
     78 
     79 
     80More Information 
     81================ 
     82 
     83This information is also in the `README` file of the rIDL distribution. 
     84 
     85}}}