solidDB Help : Programming : Deploying SMA and LLA applications : Deploying LLA applications : Linking the application to the LLA library
  
Linking the application to the LLA library
When you use Linked Library Access (LLA), you link your application to the appropriate LLA library, see LLA components.
Link your application to the LLA library file that is specific to your operating system (where ver is the solidDB version number):
For Windows:
Static library: ssolidacver.dll
Dynamic library: solidimpac.lib (an import library file that gives you access to the .dll file).
For example, in the makefile example below, the solidimpac.lib library is used.
# compiler
CC =cl
compiler flags CFLAGS = -I. -DSS_WINDOWS -DSS_WINNT
linker flags and directives
SYSLIBS = libcmt.lib kernel32.lib advapi32.lib netapi32.lib user32.lib oldnames.lib gdi32.lib
LFLAGS = ..\solidimpac.lib
OUTFILE = -Fe

# MyApp building
all: myapp

myapp: myapp.c
 $(CC) $(CFLAGS) $(OUTFILE)myapp myapp.c /link$(LFLAGS)
/NODEFAULTLIB:libc.lib
For Linux, Solaris, and AIX:
Static library: solidac.a
Shared library: libssolidacver.so (a symbolic link that gives you access to the .a file).
For details about the location of these files, see solidDB directory structure and contents.
See
Linking a Java application to the LLA library
Go up to
Deploying LLA applications