@@ -412,7 +412,7 @@ In the build script, it would need to update ``cmake`` call and guard any tests
412
412
ctest
413
413
fi
414
414
415
- Similarly, with Meson:
415
+ Similarly, with Meson, the `` meta.yaml `` needs :
416
416
417
417
.. code-block :: yaml
418
418
@@ -423,6 +423,8 @@ Similarly, with Meson:
423
423
- meson
424
424
- make
425
425
426
+ And this in ``build.sh ``:
427
+
426
428
.. code-block :: sh
427
429
428
430
# Pass ``MESON_ARGS`` to ``meson``
@@ -470,14 +472,14 @@ On conda-forge, there are two extra metadata bits that are needed in ``meta.yaml
470
472
so they work better with the conda-build setup.
471
473
- Copying some Python-related packages from ``host `` to ``build `` with a ``[build_platform !=
472
474
target_platform] `` selector:
475
+
473
476
- ``python `` itself, to support ``crossenv ``.
474
477
- Non-pure Python packages (i.e. they ship compiled libraries) that need to be present while the
475
478
package is being built, like ``cython `` and ``numpy ``.
476
479
477
480
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:
481
483
482
484
- A modified ``crossenv `` installation in ``$BUILD_PREFIX/venv ``, mimicking the architecture of
483
485
``$PREFIX ``.
0 commit comments