Joe Rickerby

You'll also need to add ARM64 to CIBW_ARCH, since this is a cross-compilation.

Rather than using BUILD, you can do `--only=cp311-win_arm64` if a single specific build is what you want. The CIBW_BUILD/CIBW_SKIP semantics are such that they can be set cross-platform. > and...

The reason for this is that until recently, we only supported running cibuildwheel in CI, so env vars are more convenient. I think there is an argument for `--build PATTERN`...

It's not something I'd like cibuildwheel to do by default - for small C extensions, including debug symbols is very nice so that users can supply crash reports. But it...

> The problem not stripping by default is that (almost) no one reads the docs unless there's a problem (like missing debug symbols). That's true, but I'm not sure it's...

I guess... I agree that there's some debate to be had here. cibuildwheel doesn't have a position on this though - Python (via `sysconfig`) is setting some defaults for CFLAGS...

Yes, an entry in the FAQ would be good, @henryiii. I guess it would be `CIBW_ENVIRONMENT: CFLAGS=-g0`?

Hm. Yeah. I have recreated this locally, here is the MWE: ```bash python -m test.test_projects test.test_0_basic.basic_project /tmp/basic_project (cd /tmp/basic_project && CIBW_BEFORE_BUILD="python -uc 'import sys; print(1, file=sys.stdout); print(2, file=sys.stderr)'" cibuildwheel --platform...

You _could_ be right on this, it's something that comes up relatively frequently. Previously we've discussed the possibility of allowing the user to [customise the whole pip wheel command](https://github.com/joerick/cibuildwheel/issues/151#issuecomment-509348047), but...

Thank you for this. I think I see why `CIBW_BEFORE_BUILD` coupled with build isolation is causing you problems. Couple questions (I'm not a Cython user so forgive me if these...