Reviewing Compiler And Linker Options - Dialogic Brooktrout Digital Board Installation And Configuration Manual

Reviewing Compiler and Linker Options

March 2013
The makefiles contained in the app.src and bapp.src directories
provide a number of command line options to the compiler and linker.
Using these options, the compiler and linker produce object files and
executables compatible with the Bfv API library.
Dialogic strongly recommends that you use these options for all your
Bfv API applications. But for those who want to change the set of
options the compiler and linker use, the following is a list of the
nonstandard options and their functions. The options used for
compilation are marked with (C) and those for linking are marked
with (L).
The makefile uses the standard $(cflags) from ntwin32.mak and
$(cvarsdll)for the dynamically-linked C runtime libraries. It uses
the standard $(conlflags) for linking.
$(cflags)
$(cvarsdll)
$(conlflags)
-nologo
-DWINNT
-UMSDOS,-U_MSDOS
-DMILL_DLL
libcpmt.lib
NODEBUG=1
Reviewing Compiler and Linker Options
(C) Options for CFLAGS.
(C) Options defining dynamic runtime library.
(L) Options for linking console mode program.
(C) Do not print logos.
(C) Defines a symbol that identifies the
environment.
(C) Undefines symbols that the compiler might
define that can cause problems at compilation.
(C) Defines a symbol that is required when
using the DLL Bfv API library.
(L) C++ libraries. Required when new call
control is used.
This is a makefile line, not a compilation
Note:
or link flag.
This line is needed in the makefile when
compiling with certain versions of Visual Studio
to prevent it from automatically compiling for
debugging and producing inappropriate
warning messages.
118