On 7/8/26 23:35, Martin Storsjö wrote:
On Wed, 8 Jul 2026, Jacek Caban via Mingw-w64-public wrote:
---
mingw-w64-crt/Makefile.am | 104 +++++++++++++++++++++++++++++++++-----
1 file changed, 91 insertions(+), 13 deletions(-)
This change is quite annoying... It does add a bunch of extra code
into many places, repeating the same logic all over the place.
Unfortunately, I don't really see any other good alternatives for it,
so I guess this has to be acceptable then...
Yes, it repeats the logic one more time, but this is still much less
repetition than we have for every other target. I think better solutions
exist, but they would require serious build-system changes. For example,
I do not feel like those lib*_lib*_CPPFLAGS variables make things any
easier or cleaner. I could imagine replacing them with our own custom
makefile rules instead.
Does a regular standalone arm64ec build, without arm64x, still work
correctly after this change? It would seem to me that those builds
would use %.aarch64.def files, which would be processed with
CPPFLAGSARM64NATIVE - but in such a standalone arm64ec build, that
would actually end up being arm64ec. So I think it would do the right
thing, but it's just the names/roles of the files that end up
unexpected there, right?
Oh, right, that naming could be confusing (and it does the right thing).
I originally used .gen.def instead of .aarch64.def. Maybe it's better if
I switch back to that.
Thanks,
Jacek
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
