Daniele Nicolodi

Which tools do look at the `$ARCHFLAGS` environment variable? AFAIK it is a setuptools invention. Therefore, if you are not building with setuptools, there is no reason to ever set...

I don't understand what you are trying to do, what the behavior you observe is, and what the behavior you want should be. Piecing together the information you provided, I...

> There is no archflag “PowerPC”. There is no machine value `ppc` or `ppc64`. Comparing these two is a meaningless endeavor: the condition of non-equality is always true, since these...

I will explain it once more, maybe I was not sufficiently clear before. There are two possibilities: you need to pass `-arch ppc` or `-arch ppc64` to the compiler, or...

I am tired of repeating myself. You seem to attribute some magic property to the `$ARCHFLAGS` environment variable, which are obviously not there. `$ARCHFLAGS` is the wrong solution for your...

> It will not work for FAT builds if one arch is of a different family meson-python does not support FAT or unified builds.

@erikbs cross compilation via the `$ARCHFLAGS` environment variable on macOS works just fine with meson-python for compiling aarch64 binaries on x86_64 systems and the other way around. Universal binaries in...

meson-python supports `$ARCHFLAGS` for compatibility with setuptools. It can work only for the very simple case where the only thing that is needed is to pass the `-arch` option to...

> I do believe this can and should be fixed on `meson-python` side, but obviously I am not making decisions here, it is up to the upstream. We don't have...

> It is still possible to hack around this bug and make it work correctly from Macports side. There is no bug to work around. You are using meson-python wrong....