On 27/01/2014, at 7:10 PM, Jirka Daněk wrote:
> On Thursday, November 21, 2013 2:54:18 PM UTC+1, skaller wrote:
> On 21/11/2013, at 7:05 PM, Oren Ben-Kiki wrote:
> > And, sometimes the hoop is on fire... For example, if one uses Doxygen
>
> Thats a good example of where you cannot predict the outputs.
>
> I use Doxygen. What would you suggest I do?
>
> Currently I keep it out of my build. I also have an subproject that uses
> qmake, which together amounts to having three build systems. I am considering
> putting make on top to orchestrate them for me (with PHONY targets). Any
> thoughts?
I do that too (put make on top).
A common trick is to do something like this:
doxyout.stamp: dir1/*.[ch]
doxygen whatever
touch doxyout.stamp
So basically trick the build system into believing the target is just the stamp
file which represents the output of the build process, irrespective of what
files
are actually generated.
Personally I've given up on automatic build tools.
--
john skaller
[email protected]
http://felix-lang.org
--
--
tup-users mailing list
email: [email protected]
unsubscribe: [email protected]
options: http://groups.google.com/group/tup-users?hl=en
---
You received this message because you are subscribed to the Google Groups
"tup-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
