Am 19.01.2026 um 12:04 schrieb LIU Hao:
在 2026-1-18 23:15, Markus Mützel via Mingw-w64-public 写道:
Hi,
This patch series allows to run the following commands in the root
directory of the repository and it should do something reasonable:
```
mkdir -p build
cd build
../configure
make all
make check
```
Using these commands, generated headers should be used to build the
CRT. And the built CRT should be used in the tests.
There's a dependency of CRT on headers, so if you are using recursive
make, how would you ensure that CRT is only built after headers?
Wouldn't `make` do that automatically? With the patch, I see, e.g., the
following in `mingw-w64-crt/crt/.deps/lib32_libmingw32_a-mingw_custom.Po`:
```
crt/lib32_libmingw32_a-mingw_custom.o: \
../../mingw-w64-crt/crt/mingw_custom.c ../mingw-w64-headers/crt/_mingw.h \
../../mingw-w64-crt/../mingw-w64-headers/crt/_mingw_mac.h \
../../mingw-w64-crt/../mingw-w64-headers/crt/_mingw_secapi.h \
../../mingw-w64-crt/../mingw-w64-headers/crt/vadefs.h \
../mingw-w64-headers/crt/sdks/_mingw_ddk.h \
../../mingw-w64-crt/crt/../revstamp.h
../mingw-w64-headers/crt/_mingw.h:
../../mingw-w64-crt/../mingw-w64-headers/crt/_mingw_mac.h:
../../mingw-w64-crt/../mingw-w64-headers/crt/_mingw_secapi.h:
../../mingw-w64-crt/../mingw-w64-headers/crt/vadefs.h:
../mingw-w64-headers/crt/sdks/_mingw_ddk.h:
../../mingw-w64-crt/crt/../revstamp.h:
```
Most of these files are headers in the `mingw-w64-headers` directory of
the *source tree*. But there is also `sdks/_mingw_ddk.h` from the *build
tree*.
`make` should rebuild the object whenever it finds that one of these
files changed. Whether it was updated manually (in the source tree) or
regenerated (in the build tree) shouldn't make a difference, does it?
Markus
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public