Driver File Locations; Reviewing Compiler And Linker Options - Dialogic Brooktrout Digital Board Installation And Configuration Manual

./dinstall -c 0 -1 16 32768 10240 0 1 1 1 1024000 0 0 1 0 0 0 0 0 0 0 0 0 0

Driver File Locations

Reviewing Compiler and Linker Options

March 2013
application histories 0
restrict physical channels
all default advanced parameters
Enter the following at the command line:
When using dinstall to configure the device driver, you need not
have all files from the distribution. However, the locations of files
used by the installation procedure relative to the directory from
which dinstall is being run must be the same as that in the normal
distribution.
Assuming a directory named install from which dinstall is being run,
the following files must be present:
install/dinstall
install/dinstlib
kernel/kvers/*
These files and directories appear in the standard distribution under
the directory driver/linux.
The kvers directory contains subdirectories named after each kernel
version for which binaries are available. The software supports the
standard uni and multiprocessor releases, as well as alternate
releases. See the Dialogic® Brooktrout® Release Notes for the
supported kernel versions.
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
Dialogic® Brooktrout® Bfv API applications. But for those who want
to change the set of options the compiler and linker use, the
Special Considerations
48