- more about installing when automake is used by developers

- minor improvements
This commit is contained in:
wrobell 2002-03-27 23:23:52 +00:00
parent 742003e20e
commit 194596fc77
2 changed files with 42 additions and 10 deletions

View File

@ -67,10 +67,25 @@
</itemizedlist> </itemizedlist>
</para> </para>
<para> <para>
<application>Automake</application> 1.5 introduced Python
support. Developers want to use the same tool for
their projects written in Python or C and
<application>automake</application> gives such possibility to them.
</para>
<para>
Installing Python modules can be done the same way
as installing other applications or libraries, which
authors use <application>automake</application>.
Just remember to pass <envar>$RPM_BUILD_ROOT</envar>
to <envar>DESTDIR</envar>, so
<application>make</application> will install source files
(*.py), byte compiled (*.pyc) and optimized byte compiled
(*.pyo) files under <envar>$RPM_BUILD_ROOT</envar>
hierarchy.
<example> <example>
<title> <title>
Installing Python modules with Installing Python modules with Makefile files
<application>automake</application> Makefile files. created with <application>automake</application>.
</title> </title>
<screen> <screen>
%{__make} install DESTDIR=$RPM_BUILD_ROOT %{__make} install DESTDIR=$RPM_BUILD_ROOT
@ -82,10 +97,11 @@
has ability to install optimized and has ability to install optimized and
normal byte compiled files. It can be done with normal byte compiled files. It can be done with
<command>setup.py</command> script option <command>setup.py</command> script option
<parameter>--optimize</parameter>. Installed files <parameter>--optimize</parameter>.
Option <parameter>--root</parameter> should
be used too, because installed files
should be put in <envar>$RPM_BUILD_ROOT</envar> should be put in <envar>$RPM_BUILD_ROOT</envar>
directory and option <parameter>--root</parameter> can directory.
be used.
<example> <example>
<title> <title>
Installing Python modules in <application>RPM</application> install section Installing Python modules in <application>RPM</application> install section

View File

@ -67,10 +67,25 @@
</itemizedlist> </itemizedlist>
</para> </para>
<para> <para>
<application>Automake</application> 1.5 introduced Python
support. Developers want to use the same tool for
their projects written in Python or C and
<application>automake</application> gives such possibility to them.
</para>
<para>
Installing Python modules can be done the same way
as installing other applications or libraries, which
authors use <application>automake</application>.
Just remember to pass <envar>$RPM_BUILD_ROOT</envar>
to <envar>DESTDIR</envar>, so
<application>make</application> will install source files
(*.py), byte compiled (*.pyc) and optimized byte compiled
(*.pyo) files under <envar>$RPM_BUILD_ROOT</envar>
hierarchy.
<example> <example>
<title> <title>
Installing Python modules with Installing Python modules with Makefile files
<application>automake</application> Makefile files. created with <application>automake</application>.
</title> </title>
<screen> <screen>
%{__make} install DESTDIR=$RPM_BUILD_ROOT %{__make} install DESTDIR=$RPM_BUILD_ROOT
@ -82,10 +97,11 @@
has ability to install optimized and has ability to install optimized and
normal byte compiled files. It can be done with normal byte compiled files. It can be done with
<command>setup.py</command> script option <command>setup.py</command> script option
<parameter>--optimize</parameter>. Installed files <parameter>--optimize</parameter>.
Option <parameter>--root</parameter> should
be used too, because installed files
should be put in <envar>$RPM_BUILD_ROOT</envar> should be put in <envar>$RPM_BUILD_ROOT</envar>
directory and option <parameter>--root</parameter> can directory.
be used.
<example> <example>
<title> <title>
Installing Python modules in <application>RPM</application> install section Installing Python modules in <application>RPM</application> install section