glfs/basicnet/netprogs/ncftp/ncftp-inst.xml
Igor Živković af986b5e0a updated to ncftp-3.1.7
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@1740 af4574ff-66df-0310-9fd7-8a98e5e911e0
2004-01-31 22:57:24 +00:00

35 lines
1.6 KiB
XML

<sect2>
<title>Installation of <application>Nc<acronym>FTP</acronym></application></title>
<para>There are two ways to build <application>Nc<acronym>FTP</acronym></application>. The first
(and optimal) way builds most of the functionality as a shared library and
then builds and installs the program linked against this library. The second
method simply links all of the functionality into the binary statically. This
doesn't make the dynamic library available for linking by other
applications. You need to choose which method best suits you. Note
that the second method does <emphasis>not</emphasis> create an entirely
statically linked binary; only the <filename class="libraryfile">libncftp</filename> parts are
statically linked in, in this case. Be aware that building and using the shared
library is covered by the Clarified Artistic License; however, developing
applications that utilize the shared library is subject to a different license.
</para>
<para>To install <application>Nc<acronym>FTP</acronym></application> using the first (and optimal)
method, run the following commands:</para>
<screen><userinput><command>./configure --prefix=/usr &amp;&amp;
make -C libncftp shared &amp;&amp;
make -C libncftp soinstall &amp;&amp;
make &amp;&amp;
make install</command></userinput></screen>
<para>To install <application>Nc<acronym>FTP</acronym></application> using the second method (with
the <filename class="libraryfile">libncftp</filename> functionality linked in statically) run the
following commands:</para>
<screen><userinput><command>./configure --prefix=/usr &amp;&amp;
make &amp;&amp;
make install</command></userinput></screen>
</sect2>