Skip to content

Commit 3404626

Browse files
committed
fix errors
1 parent cb3af4e commit 3404626

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

sphinx/src/maintainer/knowledge_base.rst

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -412,7 +412,7 @@ In the build script, it would need to update ``cmake`` call and guard any tests
412412
ctest
413413
fi
414414
415-
Similarly, with Meson:
415+
Similarly, with Meson, the ``meta.yaml`` needs:
416416

417417
.. code-block:: yaml
418418
@@ -423,6 +423,8 @@ Similarly, with Meson:
423423
- meson
424424
- make
425425
426+
And this in ``build.sh``:
427+
426428
.. code-block:: sh
427429
428430
# Pass ``MESON_ARGS`` to ``meson``
@@ -470,14 +472,14 @@ On conda-forge, there are two extra metadata bits that are needed in ``meta.yaml
470472
so they work better with the conda-build setup.
471473
- Copying some Python-related packages from ``host`` to ``build`` with a ``[build_platform !=
472474
target_platform]`` selector:
475+
473476
- ``python`` itself, to support ``crossenv``.
474477
- Non-pure Python packages (i.e. they ship compiled libraries) that need to be present while the
475478
package is being built, like ``cython`` and ``numpy``.
476479

477480
In the terms of the `PEP720 <https://peps.python.org/pep-0720/>`__, the conda-forge setup
478-
implements the "faking the target environment" approach. More specifically:
479-
480-
This will result in the following changes before the builds scripts run:
481+
implements the "faking the target environment" approach. More specifically, this will result in the
482+
following changes before the builds scripts run:
481483

482484
- A modified ``crossenv`` installation in ``$BUILD_PREFIX/venv``, mimicking the architecture of
483485
``$PREFIX``.

0 commit comments

Comments
 (0)