Igor, I just said about native support from Visual Studio, not from cmake itself.
Modern cmake can generate projects even for Visual Studio 2008 [1] [1] -- https://cmake.org/cmake/help/v3.16/generator/Visual%20Studio%209%202008.html вт, 26 мая 2020 г. в 16:16, Igor Sapego <isap...@apache.org>: > Nikolay, removing support for a certain build system is a breaking change. > > Ivan, in C++ world there are companies that still use VS 2012 or even 2010. > > Best Regards, > Igor > > > On Tue, May 26, 2020 at 4:08 PM Ivan Daschinskiy <ivanda...@gmail.com> > wrote: > > > Guys, thank you all for support > > > > >> The only concern I have is that it is one more build system > > to support. Should we get rid of autotools in 3.0? > > > > I'd suggest leave CMake as an only build system. Cmake could generate VS > > projects more than 12 years ago flawlessly, moreover, VS since 2017 has > > native support of CMake, so even this step (generation of project) is no > > more necessary. > > > > > > On 26.05.2020 16:02, Igor Sapego wrote: > > > Great! > > > > > > Let's start with creating a TC suite for it. > > > > > > The only concern I have is that it is one more build system > > > to support. Should we get rid of autotools in 3.0? > > > > > > Best Regards, > > > Igor > > > > > > > > > On Tue, May 26, 2020 at 2:44 PM Alexey Kukushkin < > > kukushkinale...@gmail.com> > > > wrote: > > > > > >> +1. I recently completed a cross-IDE (MS Visual Studio & GCC/GDB) > Ignite > > >> C++ project and CMake in Ignite C++ would save me a day of effort. > > >> > > >> вт, 26 мая 2020 г. в 12:09, Pavel Tupitsyn <ptupit...@apache.org>: > > >> > > >>> +1 > > >>> > > >>> On Tue, May 26, 2020 at 12:02 PM Zhenya Stanilovsky > > >>> <arzamas...@mail.ru.invalid> wrote: > > >>> > > >>>> Ivan huge +1 with your proposal. > > >>>> I had some problems with odbc tests building too, looks like cmake > > will > > >>>> make it more easy. > > >>>>> Hello Igniters. > > >>>>> > > >>>>> I’d like to discuss porting build process of Ignite.C++. I think > that > > >>>> there is time to change it. > > >>>>> *Motivation* > > >>>>> Currently, it is hard to build Ignite.C++. Different build process > > for > > >>>> windows and linux, lack of building support on Mac OS X (quite > popular > > >> OS > > >>>> among developers), absolutely not IDE support, except windows and > only > > >>>> Visual Studio is supported. > > >>>>> *Suggestion* > > >>>>> I’d suggest to migrate to CMake build system. It is very popular > > among > > >>>> open source projects, and in Apache Software Foundation too. Notable > > >>> user: > > >>>> Apache Mesos, Apache Zookeeper (C client offers CMake as an > > alternative > > >>> to > > >>>> autoconf and only option on windows), Apache Kafka (librdkafka - > C/C++ > > >>>> client), Apache Thrift. Popular column-oriented database ClickHouse > > >> also > > >>>> uses CMake. > > >>>>> CMake is widely supported in many IDE’s on various platforms, > notably > > >>>> Visual Studio, CLion, Xcode, QtCreator, KDevelop. > > >>>>> *Current status* > > >>>>> > > >>>>> Currently, the most of work is done (see [1]) and tested on Mac OS > X > > >>>> 10.15 (some C++ porting). All tests are run without any flaws, > > >> including > > >>>> odbc (unixodbc), ssl, thin and thick client, installation, IDE > > >>> integration > > >>>> (CLion). Next steps is to test linux and windows. > > >>>>> But full migration isn’t possible without agreement and help of > > >>>> community. Even if most of all you agree, migration requires > > additional > > >>>> efforts in TC agents tuning and so on (event though test running > fully > > >>>> automated by CMake CTest). > > >>>>> Lets discuss my proposition and idea. > > >>>>> > > >>>>> [1] - https://github.com/apache/ignite/pull/7845 > > >>>>> > > >>>>> > > >>>>> > > >>>> > > >>>> > > >>>> > > >> > > >> -- > > >> Best regards, > > >> Alexey > > >> > > > -- Sincerely yours, Ivan Daschinskiy
