One other very good reason, too:<br>Same target may have two source files of the exact same name, but they exist in different directories (Abc/Object.cxx and Def/Object.cxx). In that case, the object files will be further hidden in subdirectories to avoid two files in the "object files directory" from having a name collision.
<br><br><br><div><span class="gmail_quote">On 12/19/07, <b class="gmail_sendername">Alexander Neundorf</b> <<a href="mailto:a.neundorf-work@gmx.net">a.neundorf-work@gmx.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wednesday 19 December 2007, you wrote:<br>...<br>> Yeah, you could even create one static library per executable...<br>> Awesome! What was the problem with putting all the object files in the<br>> same directory, again? Shouldn't that be an option, at least? It would
<br>> be SO much easier than all the dirty hacks I'm being proposed...<br><br>Different targets may be compiled with different compiler flags, defines, etc.<br>So the object files for the same source files can differ. This is used in
<br>some projects.<br><br>Alex<br>_______________________________________________<br>CMake mailing list<br><a href="mailto:CMake@cmake.org">CMake@cmake.org</a><br><a href="http://www.cmake.org/mailman/listinfo/cmake">http://www.cmake.org/mailman/listinfo/cmake
</a><br></blockquote></div><br>