Date: Mon, 4 Nov 2024 15:44:51 +0200
On Mon, 4 Nov 2024 at 15:01, Boris Kolpackov <boris_at_[hidden]> wrote:
>
> Ville Voutilainen via SG15 <sg15_at_[hidden]> writes:
>
> > But that also doesn't necessarily mean dynamic build graph nodes. I'm
> > not a build system expert, but I do know how to construct my (CMake)
> > builds so that the generative build is done before the builds that
> > need its results, so that the generation results are there when the
> > next step is configured as part of an overall build (the build, not
> > the configure-step of the overall build), and it then feeds Ninja a
> > perfectly static build graph.
>
> How would you handle the Apache Thrift example I mentioned in a
> sibling reply? Do you expect the user to re-run CMake every time
> they change their IDL file?
No, I don't expect that. I will write the CMake build so that its
build tool reruns CMake
for the relevant parts of the overall project.
>
> Ville Voutilainen via SG15 <sg15_at_[hidden]> writes:
>
> > But that also doesn't necessarily mean dynamic build graph nodes. I'm
> > not a build system expert, but I do know how to construct my (CMake)
> > builds so that the generative build is done before the builds that
> > need its results, so that the generation results are there when the
> > next step is configured as part of an overall build (the build, not
> > the configure-step of the overall build), and it then feeds Ninja a
> > perfectly static build graph.
>
> How would you handle the Apache Thrift example I mentioned in a
> sibling reply? Do you expect the user to re-run CMake every time
> they change their IDL file?
No, I don't expect that. I will write the CMake build so that its
build tool reruns CMake
for the relevant parts of the overall project.
Received on 2024-11-04 13:45:07