On Sun, 1 Oct 2023 at 04:45, Jan Engelhardt wrote:
> >I didn't explain sufficiently. The submakes I'm talking about are my
> >doing, and I want to conditionalize them on whether
> >--enable-dependency-tracking is used.
> >
> >In for example both ntpq/Makefile.am and ntpd/Makefile.am I'm
>I didn't explain sufficiently. The submakes I'm talking about are my
>doing, and I want to conditionalize them on whether
>--enable-dependency-tracking is used.
>
>In for example both ntpq/Makefile.am and ntpd/Makefile.am I'm invoking:
>
>(cd ../libntp && make libntp.a)
Yes and if you didn't do
On Sun, 1 Oct 2023 at 00:59, Nick Bowler wrote:
> Suggestion 2) All explicit --enable-foo/--disable-foo arguments to
> a configure script are available in shell variables; in the case of
> --disable-dependency-tracking you can do something like this in
> configure.ac:
>
>
On 2023-09-30, Nick Bowler wrote:
> Two suggestions, one relying on Automake internals and one not:
>
> Suggestion 1)
> internal ... Automake conditional called AMDEP.
[...]
> Suggestion 2)
[...]
> AM_CONDITIONAL([NO_DEPS], [test x"$enable_dependency_tracking" = x"no"])
> Note that these
On 2023-09-29, Dave Hart wrote:
> I'm guessing someone has trod this ground before. I'd appreciate
> pointers to examples of how others have detected
> --disable-dependency-tracking to change their build behavior.
Two suggestions, one relying on Automake internals and one not:
Suggestion 1) It
On Sat, 30 Sept 2023 at 05:07, Jan Engelhardt wrote:
> On Saturday 2023-09-30 05:27, Dave Hart wrote:
>
> >I've added code to the ntp.org Makefile.am files to ensure the static
> >utility library libntp.a is up-to-date for each program that uses it, to
> >ensure the build is correct. When
On Sat, Sep 30, 2023, at 1:07 AM, Jan Engelhardt wrote:
> On Saturday 2023-09-30 05:27, Dave Hart wrote:
>
>>I've added code to the ntp.org Makefile.am files to ensure the static
>>utility library libntp.a is up-to-date for each program that uses it, to
>>ensure the build is correct. When
