On Wed, Jun 16, 2010 at 1:26 AM, Micha Renner <span dir="ltr"><<a href="mailto:Micha.Renner@t-online.de">Micha.Renner@t-online.de</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
There still some problems with the Express version of VS<br>
I started the gui-version of CMake and generated the solution files<br>
(empty build directory). No errors.<br>
<br>
First run in the IDE generates a lot of CMake errors (see appendix).<br></blockquote><div><br></div><div>CMake should not have to re-run during a build like this... Is your project available as open source so that we can download it and try it here? Or could you send me a zip of your source tree off-list, if possible? There must be something else going on with the CMake files in this project to see a result like this.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Another hit on the F7 key: Most errors are gone.<br>
Okay, I can live with this, others may be not.<br>
<br>
A bad point is what happens, if there is change in the script files.<br>
- the IDE saves all files (ok)<br>
- CMake starts (ok)<br>
- the compiler/linker starts and works with the old solution files<br>
- the new generated solution files are loaded in the IDE (too late).<br>
<br>
The problems with the filter-files are gone, very good, but there are<br>
still the problems with the reloading of solution files if they are not<br>
changed. I know this is an old problem, but it still exists.<br></blockquote><div><br></div><div>Since Visual Studio Express does not support macros, the auto-reload-during-build macros that CMake supplies are not involved in this scenario. Because of this fact, the workflow of "staying in the native build tool" after the first CMake run is never going to work well with the Express editions of VS. This old problem is still going to exist, and it's just going to get older.</div>
<div><br></div><div>Therefore, I would strongly recommend exiting VS Express prior to running CMake, running cmake or cmake-gui standalone without VS Express running, and then re-launching VS Express to build.</div><div><br>
</div><div>Or: upgrade to a paid version of VS so that the macros have a chance to work.</div><div><br></div><div><br></div><div>HTH,</div><div>David</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Greetings<br>
<font color="#888888"><br>
Micha<br>
<br>
</font><br>_______________________________________________<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></blockquote></div><br>