Changes between Version 1 and Version 2 of CompilationGuide/Generic


Ignore:
Timestamp:
Dec 23, 2013, 11:15:43 AM (4 years ago)
Author:
saste
Comment:

add section about environment variables

Legend:

Unmodified
Added
Removed
Modified
  • CompilationGuide/Generic

    v1 v2  
    4141 
    4242Using a prefix like {{{/opt/PROJECT/}}}, the project will be installed in a dedicated directory, and to remove from the system you can simply remove the {{{/opt/PREFIX}}} path. On the other hand, such installation will require to edit all the environment variables to point to the custom path. 
     43 
     44 
     45== Environment variables == 
     46 
     47Several variables defined in the environment affect your package install. In particular, depending on your installation prefix, you may need to update some of these variables in order to make sure that the installed components can be found by the system tools. 
     48 
     49The list of environment variables can be shown through the command {{{env}}}. 
     50 
     51A list of the affected variables follows: 
     52 
     53* PATH: defines the list of :-separated paths where the system looks for binaries. For example if you install your package in {{{/usr/local/}}}, you should update the PATH so that it will contain {{{/usr/local/bin}}}. This can be done for example through the command {{{export PATH=/usr/local/bin:$PATH}}}. 
     54* LD_LIBRARY_PATH: contains the :-separated paths where the system looks for libraries. For example if you install your package in {{{/usr/local/}}}, you should update the LD_LIBRARY_PATH so that it will contain {{{/usr/local/lib}}}. This can be done for example through the command {{{export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH}}}. This variable is sometimes deprecated in favor of the use of ldconfig. 
     55* CFLAGS 
     56* LDFLAGS 
     57* PKG_CONFIG_PATH