/bin/sh ../mkinstalldirs /usr/local/lib
/bin/sh ../libtool --mode=install /bin/install -c libgig.la /usr/local/lib/libgig.la
/bin/install -c .libs/libgig.dll.a /usr/local/lib/libgig.dll.a
base_file=`basename ${file}`
dlpath=`/bin/sh 2>&1 -c '. .libs/'${base_file}'i;echo $dlname'`
dldir=/usr/local/lib/`dirname $dlpath`
test -d $dldir || mkdir -p $dldir
/bin/install -c .libs/libgig-6.dll $dldir/libgig-6.dll
/bin/install -c .libs/libgig.lai /usr/local/lib/libgig.la
===--===--===-- everything from here to the end does not have anything
===--=== to do with how dynamic linking works on Windows (AFAIK)
===--===--===-- ... there's no "ld" to run on ms windows.
----------------------------------------------------------------------
Libraries have been installed in:
/usr/local/lib
If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.