Hallo Larry, On Tuesday, January 3, 2017, 7:15:29 PM, you wrote:
> Nice. I'm not 100% sure how this helps -- Does it simply save a > step, so you don't have to first use CMake to generate a VS project > file? Or does it mean that future VS will have CMake built in so a > separate CMake install step is no longer a prerequisite? Or is there more to > it? To be fair, I know no more than what is presented on that page. Basically though, the CMake file will be a part of the VS solution, but no separate step is required. You can even configure the CMake project within VS (using a .json file) and the targets show up as normal VS targets. For building as well as debugging. Plus you get all the auto-complete functionality in the editor both for CMakeLists.txt as well as the CMakeSettings.json file. It certainly looks like a very comprehensive solution. >> On Jan 3, 2017, at 6:35 AM, Michael Wolf <[email protected]> wrote: >> >> One thing to consider is that the next version of Visual Studio will support >> CMake natively: >> https://blogs.msdn.microsoft.com/vcblog/2016/10/05/cmake-support-in-visual-studio/ -- db&w Bornemann und Wolf GbR Seyfferstr. 34 70197 Stuttgart Deutschland [email protected] http://www.db-w.com tel: +49 (711) 664 525-3 fax: +49 (711) 664 525-1 mob: +49 (173) 66 37 652 skype: lupus_lux msn: [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
