Hi all,<br><br>I'm wondering if it would be possible to have CMake bypass IDEs altogether and just produce the final, installed results.<br><br>Right now, I do this:<br>1) download source<br>2) configure source<br>3) tweak settings<br>
4) configure source again<br>5) Probably configure a third time, depending on what CMake wants to make the 'generate' button show up<br>6) generate code<br>7) open IDE<br>8) select build style (debug, release, etc)<br>
9) build<br>10) build install<br>11) use libraries/exes/etc<br><br>Would it be possible to combine steps 6-10 with a single button in CMake? That is, have a CMake default flag that is 'build style', and have that be something like 'debug' (which corresponds to a set of compiler switches, etc), 'release' (other switches), and so forth. Have that show up as a simple option when configuring. Then, rather than having to go through all subsequent steps, just have a third button that is 'build and install', that just goes right to building and installing? <br>
<br>The idea is that if I need to set up a development environment on a new machine, or recover from a crash, or the like, I should be able to download the source and (ideally) press a single button to make it happen.<br>
<br>I've followed this style:<br><a href="http://www.joelonsoftware.com/articles/fog0000000043.html">http://www.joelonsoftware.com/articles/fog0000000043.html</a><br><br>for a while now, and having the one-button deployment really shows weaknesses in the process, as well as really helps have end users get to what they actually want, which is an installed, usable version of the code that they downloaded. It's like running ./configure; make; make install from the command line, but in delicious GUI form and allowing you to easily flip whatever switches you want in step 3 above.<br>
<br>Make sense? Good idea/bad idea?<br><br>Thanks,<br>Mark<br>