On Thu, 2012-12-06 at 13:35 -0500, Andrew Stitcher wrote: > On Thu, 2012-12-06 at 13:24 -0500, Rafael Schloming wrote: > > ... > > > The best way to cater to the developer scenario you mention is to simply > > look at install_manifest.txt. This file is generated whenever you type make > > install and will provide a much more accurate check on whether the install > > is behaving as it should, and because this is generated automatically by > > cmake, it will in pretty much any conceivable scheme as long as we don't > > write our own install macro. > > Does it work where "make install" fails? If not it isn't useful in > exactly the cases I care about!
To reply to myself: install_manifest.txt is a *result* of a *successful* "make install" so is not useful to the developer case. As that fails in your proposed world stopping the file being created at all. > > Andrew > >
