<br><br>
<div class="gmail_quote">On Mon, Mar 22, 2010 at 7:46 AM, <span dir="ltr"><<a href="mailto:Aaron_Wright@selinc.com">Aaron_Wright@selinc.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote"><font size="2" face="sans-serif">You mean in the case of a master CMakelists.txt file I assume? That does work, and I like that functionality. The same kind of thing works for Visual Studio solutions as well. I just don't think this fits the usual paradigm of building my developers and I are used to. </font><br>
<br><font size="2" face="sans-serif">For example, if they want to work on a library, they would instinctively go to that library and make a build folder and run CMake. They would not think to go to the top of the directory tree, create a build folder in a location they never make folders or files or do any work, and then progress down the build folder's directory path to the library they want to build. Which is in a completely different location than the source files of the library, which they'll soon be modifying.</font> <br>
<br><font size="2" face="sans-serif">This would all work though, so it is a valid solution.</font> <br><br></blockquote>
<div> </div>
<div>Ya, I'm about to face this too... I've previously setup Makefiles to be able to build at any sub part of the tree so you can just work there.. otherwise I end up having to maintain several consoles, one in the output, one in the source, and one in the specific part of the tree built by cmake, else having to remake the whole thing over and over which is taking up to minutes.</div>
<div> </div>
<div>I also notice that building with cmake triggers excecutions of make much more than my previous Make only solution did... so it's kidna slow even in building a single source library, and a 2 second build for 100 tiny libraries adds a LOT of time. I Would think that cmake would be able to generate a master makefile that contained all rules and targets, and basically invoke the make once instead of once per file or library to buildl.</div>
<div> </div>
<div>Maybe CMake 4.0 will do this :) But that's just a dream.</div>
<div> </div>
<div>I've also started running cmake from entirely outside the source tree, which adds the benefit that I can mass compare source trees which are not corrupted by additional build products.</div>
<div> </div>
<div> </div>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote"><font size="2" face="sans-serif">-------------------------------------------------------------<br>Aaron Wright</font> <br>
<br><br><br></blockquote></div>