Use tabs for v0/v1 recipes

Signed-off-by: Michał Górny <[email protected]>

Author: mgorny

docs/how-to/advanced/cross-compilation.md …cs/how-to/advanced/cross-compilation.mdxdocs/how-to/advanced/cross-compilation.md renamed to docs/how-to/advanced/cross-compilation.mdx docs/how-to/advanced/cross-compilation.md renamed to docs/how-to/advanced/cross-compilation.mdx

@@ -2,6 +2,9 @@
 title: 'Cross-compilation'
 ---
 
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
 Cross-compiling means building a package for a different architecture than the one the build process
 is running on. It is a common way of obtaining packages for an architecture that conda-forge does
 not provide any runners for (the other available technique is
@@ -117,6 +120,9 @@ are a few examples.
 
 A simple C library using autotools for cross-compilation might look like this:
 
+<Tabs groupId="recipe">
+
+<TabItem label="v0 (meta.yaml)" value="v0">
 ```yaml
 requirements:
   build:
@@ -128,6 +134,23 @@ requirements:
   host:
     - libogg
 ```
+</TabItem>
+
+<TabItem label="v1 (recipe.yaml)" value="v1">
+```yaml
+requirements:
+  build:
+    - ${{ compiler("c") }}
+    - ${{ stdlib("c") }}
+    - make
+    - pkg-config
+    - gnuconfig
+  host:
+    - libogg
+```
+</TabItem>
+
+</Tabs>
 
 In the build script, it would need to update the config files and guard any tests when
 cross-compiling:
@@ -149,6 +172,9 @@ fi
 
 A simple C++ library using CMake for cross-compilation might look like this:
 
+<Tabs groupId="recipe">
+
+<TabItem label="v0 (meta.yaml)" value="v0">
 ```yaml
 requirements:
   build:
@@ -159,6 +185,22 @@ requirements:
   host:
     - libboost-devel
 ```
+</TabItem>
+
+<TabItem label="v1 (recipe.yaml)" value="v1">
+```yaml
+requirements:
+  build:
+    - ${{ compiler("cxx") }}
+    - ${{ stdlib("c") }}
+    - cmake
+    - ninja
+  host:
+    - libboost-devel
+```
+</TabItem>
+
+</Tabs>
 
 In the build script, it would need to update `cmake` call and guard any tests when cross-compiling:
 
@@ -177,6 +219,9 @@ fi
 
 Similarly, with Meson, the `meta.yaml` needs:
 
+<Tabs groupId="recipe">
+
+<TabItem label="v0 (meta.yaml)" value="v0">
 ```yaml
 requirements:
   build:
@@ -188,6 +233,23 @@ requirements:
   host:
     - libogg
 ```
+</TabItem>
+
+<TabItem label="v1 (recipe.yaml)" value="v1">
+```yaml
+requirements:
+  build:
+    - ${{ compiler("c") }}
+    - ${{ compiler("cxx") }}
+    - ${{ stdlib("c") }}
+    - meson
+    - pkg-config
+  host:
+    - libogg
+```
+</TabItem>
+
+</Tabs>
 
 And this in `build.sh`:
 
@@ -201,6 +263,9 @@ meson compile
 
 A simple Python extension using Cython and NumPy's C API would look like so:
 
+<Tabs groupId="recipe">
+
+<TabItem label="v0 (meta.yaml)" value="v0">
 ```yaml
 requirements:
   build:
@@ -218,13 +283,41 @@ requirements:
   run:
     - python
 ```
+</TabItem>
+
+<TabItem label="v1 (recipe.yaml)" value="v1">
+```yaml
+requirements:
+  build:
+    - ${{ compiler("c") }}
+    - ${{ stdlib("c") }}
+    - if: build_platform != target_platform
+      then:
+        - cross-python_{{ target_platform }}
+        - python
+        - cython
+        - numpy
+  host:
+    - python
+    - pip
+    - cython
+    - numpy
+  run:
+    - python
+```
+</TabItem>
+
+</Tabs>
 
 For more details about NumPy see [Building against NumPy](/docs/maintainer/knowledge_base/#building-against-numpy).
 
 ### MPI
 
 With MPI, openmpi is required for the build platform as the compiler wrappers are binaries, but mpich is not required as the compiler wrappers are scripts (see [example](https://github.com/conda-forge/mpi4py-feedstock/blob/743d379c4a04/recipe/meta.yaml#L37)):
 
+<Tabs groupId="recipe">
+
+<TabItem label="v0 (meta.yaml)" value="v0">
 ```yaml
 requirements:
   build:
@@ -234,6 +327,22 @@ requirements:
   run:
     - {{ mpi }}
 ```
+</TabItem>
+
+<TabItem label="v1 (recipe.yaml)" value="v1">
+```yaml
+requirements:
+  build:
+    - if: build_platform != target_platform and mpi == "openmpi"
+      then: ${{ mpi }}
+  host:
+    - ${{ mpi }}
+  run:
+    - ${{ mpi }}
+```
+</TabItem>
+
+</Tabs>
 
 In the build script, openmpi compiler wrappers can use host libraries by setting the environmental variable `OPAL_PREFIX` to `$PREFIX`.