Skip to content

Commit 1401a86

Browse files
committed
Replace the MinGW note with a ABI incompat. warning
As suggested by @isuruf. Signed-off-by: Michał Górny <mgorny@quansight.com>
1 parent 401c11d commit 1401a86

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/maintainer/infrastructure.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -546,7 +546,7 @@ requirements:
546546
Our default compiler stack is made up very differently on each platform; each platform
547547
has its own default compiler, with its own set of feedstocks that provide them.
548548
However, it is often possible to use a different compiler if necessary. For example,
549-
to use Clang 21 as the C and C++ compiler *on all platforms* (and not just macOS), one would additionally specify
549+
to use Clang 21 as the C and C++ compiler _on all platforms_ (and not just macOS), one would additionally specify
550550
in `recipe/conda_build_config.yaml`:
551551

552552
```yaml
@@ -655,9 +655,9 @@ There exists an alternative, MinGW-based, compiler stack on Windows:
655655

656656
Along with these compilers, `stdlib('m2w64_c')` needs to be used.
657657

658-
However, this stack is falling out of use now that most projects will natively
659-
support compilation also with MSVC, in addition to several complications
660-
arising from mixing compiler stacks.
658+
Please note that the MinGW C++ and Fortran compilers are not ABI-compatible
659+
with the default stack, and therefore special care needs to be taken when
660+
performing cross-library calls.
661661

662662
### Compiler ABI stability policy
663663

0 commit comments

Comments
 (0)