You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tutorial_packaging.rst
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -611,7 +611,7 @@ We also need to explicitly specify the ``build_system`` directive, and add condi
611
611
with when("build_system=autotools"):
612
612
depends_on("automake", type="build")
613
613
depends_on("autoconf", type="build")
614
-
depends_on("libtools", type="build")
614
+
depends_on("libtool", type="build")
615
615
616
616
As we saw with :ref:`tutorial-mpileaks <info_mpileaks>`, each spec has a ``build_system`` variant that specifies the build system it uses.
617
617
In most cases that variant has a single allowed value, inherited from the corresponding base package - so, usually, you don't have to think about it.
@@ -620,7 +620,7 @@ When your package supports more than one build system though, you have to explic
620
620
In the example above it's ``cmake`` for version 0.64 and higher and ``autotools`` for version 0.63 and lower.
621
621
622
622
The ``build_system`` variant can also be used to declare other properties which are conditional on the build system being selected.
623
-
For instance, above we use the ``when`` context manager to declare that ``autotools`` builds depend on ``automake``, ``autoconf``, and ``libtools`` being installed first.
623
+
For instance, above we use the ``when`` context manager to declare that ``autotools`` builds depend on ``automake``, ``autoconf``, and ``libtool`` being installed first.
624
624
625
625
The other relevant difference, compared to previous recipes we have seen so far, is that the code prescribing the installation procedure will live in two separate classes:
0 commit comments