Hi, On Mon, 2009-02-09 at 09:37 -0600, Dirk Reiners wrote: > Hi Gerrit, > > Gerrit Voss wrote: > > > > After looking around a little bit it seems the only solution suggested > > is to create a dummy file that gets modified if any of the compiler > > command line options change and that everything else depends on it > > so the rebuild is triggered correctly. > > does VS use timestamps for change tracking or something smarter? If the > latter > you could just dump the compiler options into a dummy file unconditionally in > cmake and only if they change a rebuild would be triggered. If it uses > timestamps you could dump into a second dummy file and copy over only if it's > different (not sure how to do that without a shell or at least some scripting > language though).
Not sure what VS uses and from it's unreliable history I would venture a guess that it ain't just plain old timestamps and that smarter isn't the only option that comes to mind ;-). Your second method is trivial and OSGConfigured.h is already handled this way so we don't rebuild all the time we rerun cmake ;-). Actually cmake should do this automatically for configure files but it somehow did not when I first tried (might have been my mistake). 'cmake -E copy_if_different' comes in quite handy ;-) kind regards, gerrit ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Opensg-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-core
