-
Notifications
You must be signed in to change notification settings - Fork 36
/
Copy pathconfigure.user
209 lines (188 loc) · 6.66 KB
/
configure.user
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
# configure.user
#
# This file contains additional input for 'configure'. It is read (sourced)
# during the configuration process. You are free to edit the settings in here.
#
# The settings in this file are all optional in the sense that they all
# have reasonable default values in the configure script.
#
#
# Edit here if you want to use a different compiler from the one autodetected
# by configure.
#
#CC=gcc
#CXX=g++
#
# Compiler optimization switches. There are two sets of switches,
# and the MODE variable ("debug" or "release") decides which one gets used.
# (Note: For maximum debugging info use switch -ggdb or -gstabs+3 when using gcc and gdb)
# With gcc, do NOT use --omit-frame-pointer (it crashes when coroutines and
# C++ exceptions (throw/catch) are used together)!
#
#CFLAGS_DEBUG='-g -Wall'
#CFLAGS_RELEASE='-O2 -DNDEBUG=1'
#
# Linker switches used for linking.
# For example use the -m64 switch to build 64 bit binaies on a 32bit operating system
# (only if the 64bit libraries are installed of course). You should add the -m64 flag
# to the CFLAGS_... variables too !!!
# NOTE: that not all 64 bit libraries may be present on your system (i.e. Tcl/Tk and other
# libraries may be missing. Use the NO_TCL=yes if you want to skip the Tcl/Tk based parts)
#
#LDFLAGS=""
#
# It is possible to have the Tcl files embedded into the compiled OMNeT++
# libraries and executables. This can be useful if you want to ship
# self-contained standalone executables which do not rely on external
# Tcl scripts. This option is available for Tkenv.
#
EMBED_TCL_CODE=yes
#
# Set to "yes" to enable simulation executables to load NED files dynamically.
#
WITH_NETBUILDER=yes
#
# Set to "yes" to enable the parallel distributed simulation feature.
#
WITH_PARSIM=yes
#
# Set to "yes" to enable SystemC support. (Available only in the commecial version (OMNEST))
# Please note that SystemC is not supported on MacOS and on the MinGW compiler on Windows.
#
SYSTEMC=no
#
# Set to no if you want to create static OMNeT++ libraries. Can be overriden
# with "make SHARED_LIBS=no" but then simulation models also need to be built
# with "make SHARED_LIBS=no"
#
SHARED_LIBS=yes
#
# Compiler and linker options for Tcl/Tk
#
# You can explicitly tell 'configure' which compile switches (TK_CFLAGS)
# and linker switches (TK_LIBS) are needed to build an application with Tcl/Tk.
# Normally these settings are autodetected by 'configure', so you only need to
# edit here if autodetection doesn't work.
#
# With gcc, settings typically look like this:
#
# exaple:TK_CFLAGS="-I/usr/local/include"
# example:TK_LIBS="-L/usr/local/lib -ltk8.4 -ltcl8.4"
#
# /usr/local/include should be replaced with the directory where tcl.h and tk.h
# live. If they are in two different directories, use two -I switches.
#
# /usr/local/lib should be replaced with the directory that contains the Tcl/Tk
# library files (something like libtcl84.so, libtk8.4.a etc; search for libtcl*
# and libtk* to find them.) The -l options contain the library names: the
# library file names, with the leading 'lib' and trailing '.so*' or '.a*' cut
# off. Sometimes you need to explicitly link with the X11 libraries too, in that
# case add -lX11 to TK_LIBS.
#
# With MinGW I use the following:
# Note that we are using the "bin" directory as the LIB dir.
# i.e. directly linking to the DLLs instead of the importlibs in the "lib" directory.
#
#TK_CFLAGS="-I/c/Tools/Tcl-8.4.11/include"
#TK_LIBS="-L/c/Tools/Tcl-8.4.11/bin -ltk84 -ltcl84"
# or:
#TK_CFLAGS="-I$MSYS/include/tcl8.4"
#TK_LIBS="-L$MSYS/bin -ltk84 -ltcl84"
#
# With Cygwin, you can try:
# examle:TK_CFLAGS=
# examle:TK_LIBS="-ltk84 -ltcl84"
#
# If commented out, the configure script will try to autodetect it
#
# If you don't have Tcl/Tk installed, adding
# NO_TCL=true
# below lets you build just the non-GUI components.
#
# BLT is a Tcl/Tk extension needed by the Tkenv component of OMNeT++.
# BLT 2.4z is required. BLT_LIBS should contain the -l flag for BLT.
# Default setting is:
# BLT_LIBS="-lBLT24"
#
#
#BLT_LIBS=
#
# ZLib is a compression library needed by libxml2 and Tkenv's png support.
#
# On MinGW we use the following (dynamically linking against the DLL)
#
#ZLIB_CFLAGS="-I/c/Tools/zlib-1.2.3/include"
#ZLIB_LIBS="-L/c/Tools/zlib-1.2.3/bin -lzlib1"
# or:
#ZLIB_CFLAGS="-I$MSYS/include"
#ZLIB_LIBS="-L$MSYS/lib -lz"
#
# Compiler flags used to compile JNI code.
# -fno-strict-aliasing is needed for gcc when using -O2 otherwise Java
# native calls don't work
#
#JAVA_CFLAGS=-fno-strict-aliasing
#
# Compiler and linker options for MPI (optional component).
# On LAM/MPI, typing `mpic++ -showme' can give you a hint about MPI_LIBS.
#
# If commented out, the configure script will try to autodetect it
#
#MPI_CFLAGS="-I /usr/include"
#MPI_LIBS="-pthread -llammpio -llammpi++ -llamf77mpi -lmpi -llam -laio -laio -lutil"
#MPI_LIBS="-lmpi++ -lmpi" #SGI
#
# Compiler and linker options for Expat (optional component)
#
# With MinGW I use the following:
# EXPAT_CFLAGS="-I/d/home/tools/expat-1.95.2/Source/lib"
# EXPAT_LIBS="-L/d/home/tools/expat-1.95.2/libs -lexpat"
# If commented out, the configure script will try to autodetect it
#
#EXPAT_CFLAGS=
#EXPAT_LIBS=
#
# Compiler and linker options for LIBXML (optional component)
#
# With MinGW I use the following:
# LIBXML_CFLAGS="-I/c/Tools/libxml2-2.6.20.win32/include -I/c/Tools/iconv-1.9.1.win32/include"
# LIBXML_LIBS="-L/c/Tools/libxml2-2.6.20.win32/bin -lxml2 -L/c/Tools/iconv-1.9.1.win32/lib -liconv"
# or:
# LIBXML_CFLAGS="-I$MSYS/include"
# LIBXML_LIBS="-L$MSYS/bin -lxml2 -L$MSYS/bin -liconv"
# If commented out, the configure script will try to autodetect it
#
#
# Compiler and linker options for Akaroa (optional component)
#
# With MinGW I use the following:
# AKAROA_CFLAGS="-I/d/home/tools/akaroa-2.7.4/include"
# AKAROA_LIBS="-L/d/home/tools/akaroa-2.7.4/lib -lakaroa"
# If commented out, the configure script will try to autodetect it
#
#AKAROA_CFLAGS=
#AKAROA_LIBS=
#
# The following OMNETPP_* variables don't need to be touched unless
# you want to relocate parts of the package (e.g. put libraries to
# /usr/lib, include files to /usr/include/omnetpp, and so on).
#
#OMNETPP_SRC_DIR="$OMNETPP_ROOT/src"
#OMNETPP_SAMPLES_DIR="$OMNETPP_ROOT/samples"
#OMNETPP_BIN_DIR="$OMNETPP_ROOT/bin"
#OMNETPP_INCL_DIR="$OMNETPP_ROOT/include"
#OMNETPP_LIB_DIR="$OMNETPP_ROOT/lib"
#
# Some more OMNeT++ variables. They select the programs opp_makemake-generated
# makefiles will use. (They get default values if commented out.)
#
#MSGC="$OMNETPP_BIN_DIR/opp_msgc"
#
#
# Override the following setting if you have additional icons somewhere else.
#
# OMNETPP_IMAGE_PATH="./images;./bitmaps;$OMNETPP_ROOT/images"
#
# On MinGW we use the following
#JDK=/c/Tools/jdk1.6.0
#SWIG=/c/Tools/swigwin-1.3.31/swig