<div class="gmail_quote">On Mon, Mar 30, 2009 at 9:27 PM, Philip Lowman <span dir="ltr"><<a href="mailto:philip@yhbt.com">philip@yhbt.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div class="im">On Mon, Mar 30, 2009 at 4:09 PM, Darren Weber <span dir="ltr"><<a href="mailto:darren.weber.lists@gmail.com" target="_blank">darren.weber.lists@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Can we automatically extract an equivalent cmake command line after running ccmake?<br><br>Take care, Darren</blockquote></div><div><br>If you're using the Makefile generator you can simply type "make edit_cache" in your build tree after you've initially generated.<br>
<br>If this doesn't solve your problem you likely can look towards finding the source directory in the CMakeCache.txt file.<br></div></div></blockquote></div><br>I think he wants to run ccmake and configure things how he likes and then get a command line that would produce the equivalent configuration without ccmake (i.e. cmake -DSOMEVAR:BOOL=ON -DPATH_TO_SOME_EXE:PATH=/path/to/some.exe). This way, he can configure a new build in one easy step.<br>
<br>I don't believe this feature exists, though you could get something close by doing the following.<br><br>1. Create a build directory and run cmake <path to source>. This is your default configuration.<br>2. Copy CMakeCache.txt some where safe.<br>
3. Configure you system with ccmake.<br>4. Diff the old CMakeCache.txt and the new CMakeCache.txt. The differences should show you a superset of the options you will need (depending on if some options are automatically generated when you turn others on).<br>
<br>James<br>