Skip to content

Commit 41b6886

Browse files
committed
Replace outdated docs in KB with a reference to infra doc
Signed-off-by: Michał Górny <mgorny@quansight.com>
1 parent 8001a1b commit 41b6886

File tree

1 file changed

+1
-29
lines changed

1 file changed

+1
-29
lines changed

docs/maintainer/knowledge_base.md

Lines changed: 1 addition & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -351,35 +351,7 @@ Batch syntax is a bit different from Bash and friends on Unix, so we have collec
351351

352352
### Compilers
353353

354-
Compilers are dependencies with a special syntax and are always added to `requirements/build`.
355-
356-
There are currently five supported compilers:
357-
358-
- C
359-
- cxx
360-
- Fortran
361-
- Go
362-
- Rust
363-
364-
A package that needs all five compilers would define
365-
366-
```yaml
367-
requirements:
368-
build:
369-
- {{ compiler('c') }}
370-
- {{ compiler('cxx') }}
371-
- {{ compiler('fortran') }}
372-
- {{ compiler('go') }}
373-
- {{ compiler('rust') }}
374-
```
375-
376-
:::note
377-
378-
Appropriate compiler runtime packages will be automatically added to the package's runtime requirements and therefore
379-
there's no need to specify `libgcc` or `libgfortran`. There are additional informations about how conda-build 3 treats
380-
compilers in the [conda docs](https://docs.conda.io/projects/conda-build/en/stable/resources/compiler-tools.html).
381-
382-
:::
354+
Dependencies on compilers are explained in detail in [Compilers and Runtimes](/docs/maintainer/infrastructure/#compilers-and-runtimes) infrastructure documentation.
383355

384356
<a id="cross-compilation"></a>
385357

0 commit comments

Comments
 (0)