There's nothing wrong with that approach, per se, it simply "doesn't feel natural" to Xcode and Visual Studio users.
Xcode and Visual Studio users building modern apps for multiple targeted platforms (phone, tablet, simulated phone/tablet, desktop, other) are used to switching the target platform in the IDE somewhere **within a single project file** for non-CMake-generated project files. Forcing them to have multiple Xcode or VS project files, one each for each of their platforms (and configs) feels like a lot of work somehow. The only thing "wrong" with your approach is you have to spend a lot of time convincing people that CMake is worth it, when all they want to do is open a project file and build. They don't want to have to manage a slew of build trees and project files, when it seems like it ought to be "done already" with what's readily available in the UI... I totally understand this, and get it. And I still love CMake despite this particular shortcoming. ;-) David C. On Tue, Aug 4, 2015 at 5:10 PM, Tamás Kenéz <tamas.ke...@gmail.com> wrote: > On 2015-07-30 11:51:54 GMT, Nagy-Egri Máté Ferenc via CMake wrote: > >> how on Earth am I going to build x86/x64/ARM targets from one VS solution? >> [...] >> the way how CMake has been designed immediately rules it out from ~75% of >> application development going on in the world in the future (mobile app >> devel) > > Well, we are building Android and iOS projects with CMake and we simply > configure separate build dirs for each architecture. We even need to > configure seperate dirs for Debug and Release builds for the makefile > generators. > > It doesn't feel like a problem for us. We simply adapt our workflows to it. > Is there anything wrong with this approach we don't recognize? > > Tamas Kenez > > > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
