from the work or stage directory instead of a previously installed library.
In pseudo code:
s,PLUGIN_LIBS="$PLUGIN_LIBS -Lsrc -labiword",
PLUGIN_LIBS="src/libabiword.la $PLUGIN_LIBS",
s,foo_LIBS="$foo_LIBS $PLUGIN_LIBS",
foo_LIBS="$PLUGIN_LIBS $foo_LIBS",
The initial value of PLUGIN_LIBS may contain -L/usr/local/lib so it would
have to come after -Lsrc, but -Lsrc is not correct when libtool relinks
plugins during staging so use src/libabiword.la and let libtool figure out
what flags are needed. Secondly, switch around foo_LIBS and PLUGIN_LIBS
because foo_LIBS may contain -L/usr/local/lib.
This is the FreeBSD Ports Collection. For an easy to use
WEB-based interface to it, please see:
http://www.FreeBSD.org/ports
For general information on the Ports Collection, please see the
FreeBSD Handbook ports section which is available from:
http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/ports.html
for the latest official version
or:
The ports(7) manual page (man ports).
These will explain how to use ports and packages.
If you would like to search for a port, you can do so easily by
saying (in /usr/ports):
make search name="<name>"
or:
make search key="<keyword>"
which will generate a list of all ports matching <name> or <keyword>.
make search also supports wildcards, such as:
make search name="gtk*"
For information about contributing to FreeBSD ports, please see the Porter's
Handbook, available at:
http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/
NOTE: This tree will GROW significantly in size during normal usage!
The distribution tar files can and do accumulate in /usr/ports/distfiles,
and the individual ports will also use up lots of space in their work
subdirectories unless you remember to "make clean" after you're done
building a given port. /usr/ports/distfiles can also be periodically
cleaned without ill-effect.