Let's keep things calm, reasonable, rational here on the CMake mailing list. It's a discussion. Some discussions require more patience than others... :-)<div><br></div><div>Olaf, clearly you have an idea that you are passionate about.</div>
<div><br></div><div>Just as clearly, most of the other responders to this topic have reasons to be biased against the idea of automatic library name decoration.</div><div><br></div><div>Here are the facts, as I see them:</div>
<div>- It would be possible to add automatic opt-in (not enabled by default) library name decoration rules to CMake</div><div>- It would NOT be possible to come up with a naming scheme that is acceptable to everyone</div>
<div>- Some people love auto-linking from header files, some people hate it<br><br></div><div>- If the CMake team were to implement such a feature:</div><div>-- it would save Olaf from having to do it himself</div><div>-- it would take the CMake team a boat-load of time and money and effort to implement the feature</div>
<div><br></div><div>For those reasons, I do not see this feature happening anytime soon unless somebody steps up to the plate with:</div><div>- a reasonable design for it, acceptable by the consensus of folks right here on this mailing list</div>
<div>- an implementation patch, fully tested **or** a contract with somebody (Kitware, cough, cough) to pay them to implement it</div><div><br></div><div>I truly hope this clarifies things for you Olaf.</div><div><br></div>
<div>It's not that we are absolutely opposed to such a feature. But please recognize that it's a large amount of effort to implement it, make sure it's tested and works on all platforms, and keep it working moving forward. Especially hard to achieve without consensus...</div>
<div><br></div><div><br></div><div>Thanks,</div><div>David Cole</div><div>Kitware, Inc.<br><div class="gmail_quote"><br></div><div class="gmail_quote"><br></div><div class="gmail_quote">On Fri, Jul 30, 2010 at 9:08 AM, Michael Wild <span dir="ltr"><<a href="mailto:themiwi@gmail.com">themiwi@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br>
On 30. Jul, 2010, at 14:46 , Olaf van der Spek wrote:<br>
<br>
> On Fri, Jul 30, 2010 at 2:42 PM, Michael Wild <<a href="mailto:themiwi@gmail.com">themiwi@gmail.com</a>> wrote:<br>
>> Oh, it IS library specific. Where do you think all these BOOST_MSVC and what not come from? It is very specific to Boost. No other project will be able to use this without heavy reworking.<br>
><br>
> That's just the MSVC version, available as _MSC_VER by default.<br>
<br>
</div>Oh bugger, you really are immune to reason...<br>
<br>
1. This is not the only macro.<br>
2. A library project wanting to distribute a similar file has to do a lot of work to adapt it to its own requirements.<br>
3. It is a maintenance nightmare, because e.g. _MSC_VER is combined from the major and minor version number of the compiler, so for VS 2010 it is 1600. This requires that for every new version you'll be adding a new branch in the #if ... #elif ... #endif maze, translating that number into a readable name. Now, imagine other compilers starting to adopt this "magic", this file would just explode (and compilation would probably slow down to a crawl).<br>
<div class="im"><br>
><br>
>>>> For every new version of MSVC, Xcode etc. you have to update the file. Usually you will be lagging behind, and your users even more so. And then they will complain. To you.<br>
><br>
> Only if you include the toolset in the name.<br>
<br>
</div>This is really wearing my patience right now. I suggest we stop this absolutely futile discussion and let Olaf come up with something constructive for once (such as a patch). At least I will.<br>
<font color="#888888"><br>
Michael<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</div></div></blockquote></div><br></div>