Next: ASIS-for-GNAT Warnings, Previous: Processing an Ada Library by an ASIS-Based Tool [Contents][Index]
If you have installed ASIS-for-GNAT as an Ada library and added the directory
containing all source, ALI and library files of this library to the values
of the ADA_INCLUDE_PATH
and ADA_OBJECTS_PATH
environment
variables (which is a recommended way to install ASIS-for-GNAT), you do not
need to supply any ASIS-specific options for gcc
or for gnatbind
when working with your ASIS applications.
However for gnatlink
you have to provide an additional parameter
-lasis:
$ gnatlink my_application -lasis
When using gnatmake
, you also have to provide this linker parameter
whenever a call to gnatmake
invokes gnatlink
:
$ gnatmake ... my_application -largs -lasis
You do not need these linker parameters if a call to gnatmake
is not
creating the executable:
$ gnatmake -c ... my_application
If you have installed ASIS-for-GNAT without building an ASIS library, then you have to do the following when working with your ASIS application code:
asis-[version#]-src/asis
and asis-[version#]-src/gnat
) in the
search path for the source files. You may do this either by the -I
option to gcc
or by adding these directories to the ADA_INCLUDE_PATH
environment variable.
asis-[version#]-src/obj
, if you followed the manual installation procedure
described in the top-level ASIS README file) in the search path for
gnatbind
. You can do this either with the -aO option to
gnatbind
or by
adding this directory to the ADA_OBJECTS_PATH
environment variable.
If you have added directories with ASIS-for-GNAT source, object and ALI files
to the values of the GNAT-specific environment variables, you do not
have to provide any ASIS-specific parameter when using gnatmake
for your
ASIS application.
Next: ASIS-for-GNAT Warnings, Previous: Processing an Ada Library by an ASIS-Based Tool [Contents][Index]