On 18 September 2013 00:39, David <bouncingcats@gmail.com> wrote:
If filename whitespace is not an issue, either #2 or #3 should be sufficient to solve the problem. But if it is, I imagine 'find' would be a solution, it avoids the other issues provided one doesn't try to read its results into the makefile. But then, why use a makefile?
Responses upthread indicate I failed to express myself clearly. Where I wrote "But then, why use a makefile", it was not intended to convey "I have no clue what makefiles are for, please tell me", because I know 'make' very well. It was intended apply in the previous context of "But if it is [...] then why use a makefile". Sorry for not writing more clearly. Here is a rewrite of what I was trying to say there: Even if 'find' is used to find filenames containing whitespace, there is *no* way to use them as 'make' targets or prerequisites. Hence "why use a makefile"; ie. there's no point in trying to use 'make' with such files. Though I suppose it is possible that what 'find' finds could be written into a file that was managed by 'make'. But I will shut up now until Russell provides more info on exactly what he needs, or tells us that he has solved it himself.