source: releases/0.6.3/share/config.site

Last change on this file was 291, checked in by andreasw, 13 years ago

added description of configure options in config.site file

File size: 12.3 KB
Line 
1# This file contains site-specific settings for the configure scripts.
2# It can be used to specify options that are otherwise given to the
3# configure script as command line arguments or environment variables.
4#
5# This file must be located either in $prefix/share or $prefix/etc, where
6# prefix is the installation location.  For the COIN packages, this is
7# by default the directory where the configure of the main package is run,
8# unless the --prefix option was given to the configure script.
9# Alternatively, one can set the environment variable CONFIG_SITE to the full
10# path to this file.
11#
12# This template file also serves as documentation for many available
13# configure options for COIN-OR projects.  Please be aware of the following
14# conventions that translate the command line format into the one for the
15# config.site file:
16#
17#   Command line version                config.site version
18#
19#   --with-NAME1-NAME2                  with_NAME1_NAME2=yes
20#   --with-NAME1-NAME2="VALUE"          with_NAME1_NAME2="VALUE"
21#   --without-NAME1-NAME2               with_NAME1_NAME2=no
22#   --enable-NAME1-NAME2                enable_NAME1_NAME2=yes
23#   --enable-NAME1-NAME2="VALUE"        enable_NAME1_NAME2="VALUE"
24#   --disable-NAME1-NAME2               enable_NAME1_NAME2=no
25#
26# Here, "NAME1-NAME2" is some string corresponding to a particular option;
27# note that dashes (-) are converted into underscores(_).  VALUE is the
28# string that is the actual argument to an option.
29# Other variables that are directly assigned in the configure command line,
30# such as CXX=g++, are also written in this way in the config.site file.
31#
32# Note:  This is a /bin/sh script, setting variables.  There must be no
33# space between "=" and the value, and if required, a quotation must be
34# used.
35#
36# In the following we show some arguments for configure that can be used
37# for the COIN configure scripts.
38
39
40##########################################################################
41#                      C++ compiler choice and options                   #
42##########################################################################
43
44# C++ compiler name
45#CXX=g++
46
47# C++ compiler options, overwriting configure's default choice
48#CXXFLAGS='-O3 -pipe'
49
50# Additional C++ compiler options that are added to configure's default
51# choice
52#ADD_CXXFLAGS='-pg'
53
54# Additional preprocessor definitions for the C++ compiler
55#CXXDEFS='-DZEROFAULT'
56
57# Sometimes it is desirable to compile some projects in debug mode,
58# and some in default optimized mode (see also enable_debug_compile
59# below).  In those cases, you can set the separate C++ compiler
60# options for optimized and debug compilation using the following
61# variables:
62#OPT_CXXFLAGS='-O3 -pipe'
63#DBG_CXXFLAGS='-g -pipe'
64
65# If you are using MPI, it is best to specify the underlying C++
66# compiler for the configure script in CXX (so that it can figure out
67# the default compiler options and test them), but then to tell the
68# configure script the actual MPI compiler (wrapper) using the
69# following variable
70#MPICXX='mpiCC'
71
72# If a project's library is generated from C++, but the compilers used
73# for linking is a C or Fortran compiler, one has to provide this
74# compilers with the C++ runtime libraries.  This is done with the
75# following variable:
76#CXXLIBS='-lstdc++ -lm'
77
78
79##########################################################################
80#                       C compiler choice and options                    #
81##########################################################################
82
83# C compiler name
84#CC=gcc
85
86# C compiler options, overwriting configure's default choice
87#CFLAGS='-O3 -pipe'
88
89# Additional C compiler options that are added to configure's default choice
90#ADD_CFLAGS='-pg'
91
92# Additional preprocessor definitions for the C compiler
93#CDEFS='-DZEROFAULT'
94
95# Sometimes it is desirable to compile some projects in debug mode,
96# and some in default optimized mode (see also enable_debug_compile
97# below).  In those cases, you can set the separate C compiler
98# options for optimized and debug compilation using the following
99# variables:
100#OPT_CFLAGS='-O3 -pipe'
101#DBG_CFLAGS='-g -pipe'
102
103# If you are using MPI, it is best to specify the underlying C
104# compiler for the configure script in CC (so that it can figure out
105# the default compiler options and test them), but then to tell the
106# configure script the actual MPI compiler (wrapper) using the
107# following variable
108#MPICC='mpicc'
109
110
111##########################################################################
112#                   Fortran compiler choice and options                  #
113##########################################################################
114
115# Fortran compiler name
116#F77=gfortran
117
118# Fortran compiler options, overwriting configure's default choice
119#FFLAGS='-O3 -pipe'
120
121# Additional Fortran compiler options that are added to configure's default
122# choice
123#ADD_FFLAGS='-pg'
124
125# Sometimes it is desirable to compile some projects in debug mode,
126# and some in default optimized mode (see also enable_debug_compile
127# below).  In those cases, you can set the separate Fortran compiler
128# options for optimized and debug compilation using the following
129# variables:
130#OPT_FFLAGS='-O3 -pipe'
131#DBG_FFLAGS='-g -pipe'
132
133# If you are using MPI, it is best to specify the underlying Fortran
134# compiler for the configure script in F77 (so that it can figure out
135# the default compiler options and test them), but then to tell the
136# configure script the actual MPI compiler (wrapper) using the
137# following variable
138#MPIF77='mpif77'
139
140
141##########################################################################
142#                    Utility programs and their options                  #
143##########################################################################
144
145# Program for creating and extracting archives
146#AR=ar
147
148# Program for listing symbols in a binary
149#NM=nm
150
151
152##########################################################################
153#          Flags for setting compilation and configuration modes         #
154##########################################################################
155
156
157##### INSTALLATION LOCATION
158
159# This --prefix flag determines where the binaries etc. are going to
160# be installed.  By default, this is equal to the directory where
161# 'configure' is run, so that the 'bin/', 'lib/' etc. directories are
162# created as subdirectories there.  One could also choose other
163# destinations, but keep in mind that some COIN packages use the same
164# COIN "sub-projects", but possibly different and conflicting
165# versions.
166#prefix=$HOME/MyCOIN
167
168
169##### COMPILATION MODE UNDER CYGWIN
170
171# This options can only be used under Cygwin, and it has the following
172# possible choices:
173# - mingw (default): Use the GNU compilers to compile binaries that
174#          can be run independently of Cygwin (particularly without
175#          Cygwin1.dll)
176# - msvc: Use the "native" Windows compilers, such as cl, ifort
177# - no:   Use GNU compilers to generate Cygwin-specific binaries.
178#enable_doscompile=msvc
179
180
181##### SKIPPING CONFIGURATION AND COMPILATION OF SUBPROJECTS
182
183# It is possible to skip the configuration and compilation of COIN
184# projects in a package, even when the source code for the subproject
185# is there.  For this, list the directory names that are supposed to
186# be skipped in the variable
187#COIN_SKIP_PROJECTS="Bcp Couenne"
188
189
190##### DEBUG COMPILATION
191
192# Switch on debug compilation for all projects.  (Note that this will also
193# switch to the usage of static instead of shared libraries, see
194# enable_shared below)
195#enable_debug=yes
196
197# Switch on debug compilation only for a specific project is done with
198# the command line flag enable-debug-project, where "project" is the string
199# with the project name (say, Clp, for the example).
200#enable_debug_clp=yes
201
202# Similarly, if the global enable-debug is set, we can switch it off for a
203# particular project, using
204#enable_debug_clp=no
205
206# Each project can make use of a project-specific "checklevel".  It
207# depends on the project manager, if and how this is used.  The level
208# checklevel is specified with the --with-PROJECT-checklevel, where
209# PROJECT is the lower-case string of the project name.  For Ipopt,
210# this looks like
211#with_ipopt_checklevel=1
212
213# Each project can make use of a project-specific "verbosity" level.
214# It depends on the project manager, if and how this is used.  The
215# level checklevel is specified with the --with-PROJECT-verbosity,
216# where PROJECT is the lower-case string of the project name.  For
217# Ipopt, this looks like
218#with_ipopt_verbosity=1
219
220
221##### CREATING SHARED VS. STATIC LIBRARIES
222
223# By default, projects that are compiled in optimized mode, produce
224# shared libraries (if supported), and those compiled in debug mode,
225# produce static libraries.  This behavior can be changed using the
226# following options:
227
228# disable shared mode: compile every library as static
229#enable_shared=no
230
231# disable static mode: compile every library as shared
232#enable_static=no
233
234# enable shared mode: compile always a shared library (possibly in
235# addition to a static one)
236#enable_shared=yes
237
238# enable shared mode: compile always a static library (possibly in
239# addition to a shared one)
240#enable_static=yes
241
242##### MAINTAINER MODE
243
244# Project developers might want to make changes to the autotools files.
245# Using --enable-maintainer-mode enables a number of automatic updates,
246# including:
247#  - regeneration of Makefiles if Makefile.am is changes,
248#  - regeneration and rerunning of configure script if required
249#  - updating the svn externals if the Externals file has changed
250#enable_maintainer_mode
251
252
253##########################################################################
254#                      Third-Party Codes and Packages                    #
255##########################################################################
256
257##### GENERIC FLAGS
258
259# Use the following if we want to have configure check for GNU packages
260# (such as zlib, bzlib, and readline)
261#enable_gnu_packages=yes
262
263# To use some third-party libraries, such as LP solvers, one needs to
264# specify both the directory with all header files as well as the
265# linker flags for linking with the library.  This is done with the
266# --with-LIB-incdir and --with-LIB-lib configure flags, where "LIB" is
267# replaced by the lower-case short-form of the library.  A possibly
268# incomplete list of choices for LIB in the current COIN projects is:
269# cplex, glpk, gmpl, fortmp, mosek, mpi, osl, soplex, xpress.
270# For Cplex, one might set the following:
271#with_cplex_incdir='/usr/ilog/cplex90/include/ilcplex'
272#with_cplex_lib='-L/usr/ilog/cplex90/lib/static_pic -lcplex -lpthread'
273
274##### FLAGS FOR SPECIFIC LIBRARIES IN THIRDPARTY
275
276# For some third-party dependencies, COIN supports automatic build
277# procedures, for which the user can download the external source code
278# into appropriate subdirectories in a "ThirdParty" subdirectory.  But
279# the user might want to specify locations of already precompiled versions
280# of those dependencies.  Those flags are discussed next.
281
282### BLAS
283# Flag indicating where to find Blas.  If --with-blas is not used,
284# the configure script will try a few default locations of Blas, and
285# if it doesn't find Blas, it will test if the Blas source files are
286# in ThirdParty/Blas.  If so, those will be compiled, otherwise we
287# assume that Blas is not available.
288#
289# Specify precompiled Blas libraries via linker flags:
290#with_blas="-lf77blas -latlas /usr/lib64/libg2c.so"
291# Specify that Blas should be compiled within the
292#with_blas=BUILD
293# Specify that Blas should not be used
294#with_blas=no
295
296### LAPACK
297# Flag indicating where to find Lapack.  If --with-lapack is not used,
298# the configure script will try a few default locations of Lapack, and
299# if it doesn't find Lapack, it will test if the Lapack source files are
300# in ThirdParty/Lapack.  If so, those will be compiled, otherwise we
301# assume that Lapack is not available.
302#
303# Specify precompiled Lapack libraries via linker flags:
304#with_lapack="-L$HOME/lib -lmylapack"
305# Specify that Lapack should be compiled within the
306#with_lapack=BUILD
307# Specify that Lapack should not be used
308#with_lapack=no
309
310### ASL
311# Flag indicating where to find the AMPL Solver Library.  If --with-asldir
312# is not used, the configure script will test for the source code for ASL
313# in ThirdParty/ASL.  If this is found there, the ASL will be automatically
314# compiled and used, otherwise, it is assumed that ASL is unavailable.
315# If the user already has a precompiled version of the ASL, (s)he can use
316# this flag to specify the directory will all headers and the library:
317#with_asldir=$HOME/ampl/solvers
318
Note: See TracBrowser for help on using the repository browser.