From 02f92fc7f8a69618fcf91282222b8316ace9c4ae Mon Sep 17 00:00:00 2001 From: "Adam J. Stewart" Date: Wed, 18 Jan 2017 12:34:09 -0600 Subject: Massive conversion from Package to AutotoolsPackage (#2845) * Massive conversion from Package to AutotoolsPackage * Forgot to convert p4est to AutotoolsPackage * Fix typo * Fix broken link in docs --- lib/spack/docs/packaging_guide.rst | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) (limited to 'lib') diff --git a/lib/spack/docs/packaging_guide.rst b/lib/spack/docs/packaging_guide.rst index 8a39ee28e2..b09c677e0b 100644 --- a/lib/spack/docs/packaging_guide.rst +++ b/lib/spack/docs/packaging_guide.rst @@ -1490,7 +1490,7 @@ Additional hybrid dependency types are (note the lack of quotes): * ****: ``type`` assumed to be ``("build", "link")``. This is the common case for compiled language usage. - + """"""""""""""""""" Dependency Formulas """"""""""""""""""" @@ -2007,10 +2007,15 @@ The last element of a package is its ``install()`` method. This is where the real work of installation happens, and it's the main part of the package you'll need to customize for each piece of software. -.. literalinclude:: ../../../var/spack/repos/builtin/packages/mpfr/package.py - :pyobject: Mpfr.install +.. code-block:: python :linenos: + def install(self, spec prefix): + configure('--prefix={0}'.format(prefix)) + + make() + make('install') + ``install`` takes a ``spec``: a description of how the package should be built, and a ``prefix``: the path to the directory where the software should be installed. -- cgit v1.2.3-60-g2f50