From: Mike Gold Date: 2008-09-25T03:37:40+09:00 Subject: Re: Rake dependencies unknown prior to running tasks Joe Wę—¦lfel wrote: >> I don't see why it would be inefficient or require unnecessary >> rebuilding. > > The reason is because I have to build things before I know (or can > even determine programmatically) what other things need to be built. If you can't determine programmaticaly what is built, then how does a program build it? Even C/C++ dependencies, where you have no clue what g++ -MM is going to spit out, can be handled with 'import' and the makefile loader. If you are executing some other program which generates stuff, perhaps you can add a flag where the program outputs what it *would* generate. Capture that and 'import' it. And if you can't add that flag, or if you otherwise don't know what is being generated, then your hands are tied anyway. You can't know what's going to happen, so you can't do anything about it. The two graphs are worlds apart, and never the twain shall meet. In this case I wonder what solution you could have expected. -- Posted via http://www.ruby-forum.com/.