tech-toolchain archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

make .ORDER

Is there a sane way to have target A built before target B without having 
B depend on A? Is .ORDER A B guaranteed to do that? The description of .ORDER 
says "The ordering imposed by .ORDER is only relevant for parallel makes." 
Does that mean it only imposes the ordering restrictions for parallel makes 
or the author of the manpage couldn't think of an example other that parallel 
makes where you will want a particular order without a dependency?

In my case, A is a directory containing B. The rules for A install -d and 
the rules for B install /dev/null. With B depending on A, B will be wiped out 
whenever you touch another file in directory A.

Probably there's a more elegant way to acheive the same thing.

Home | Main Index | Thread Index | Old Index