Hello! Ralf Wildenhues <[email protected]> writes:
> Now I need to ask in more detail: do you actually need "newer" or just > "not older"? Because if the latter, then you could just let the rule to > install $(nodist_foobar_DATA) depend on the rule to install > $(dist_foobar_SOURCES), the latter of which I assume you still need to > write, and hook to install-data-local. Or you do something like > mod_DATA = $(dist_foobar_SOURCES) > ccache_DATA = $(nodist_foobar_DATA) > > The install rules then still have internal names > (install-nodist_foobarDATA or install-ccacheDATA or so) but at least the > right thing happens, as long as the same $(INSTALL_DATA) command is used > in both cases. > > And if you need "newer" then you could "sleep 1" as last bit of your > hand-written rule to install $(dist_foobar_SOURCES), or let the > install-ccacheDATA depend on a guile-install-sleep helper rule which > itself depends on the install-nodist_foobarDATA rule or so. > However, that doesn't help you when "install -C" is used. > > Now, there's one more technical complication for adding the dependency: > automake will not put out its own install-ccacheDATA rule if you use it > as target anywhere (on the grounds that it's the only method to override > an automake-provided target), which you don't want here; you can trick > automake by assigning the name to some variable though: > guile_install_ccacheDATA = install-ccacheDATA > $(guile_install_ccacheDATA): install-modDATA For the record, this was fixed along these lines. The auto-compile mtime checks were also changed to checked for >= instead of ==: http://git.savannah.gnu.org/cgit/guile.git/commit/?id=fefd60ba4ba751712c45c95362bbc2f858890678 Ralf: can you formally state that the rule names (‘install-ccacheDATA’, etc.) are not going to change? :-) Thank you! Ludo’.
