Re: [DISCUSSION] Ignite.C++ and CMake

[Ilya Kasnacheev]

Hello!

Ivan, you really really need to move these two dots as a first argument in
your example, instead of a last one, or people will going to hit this issue
every time they try CMake.

Regards,
-- 
Ilya Kasnacheev


ср, 1 июл. 2020 г. в 06:18, Ivan Daschinsky :

> Pavel, pay attention to two dots at the end. All build files should stay at
> current dir, and cmake-build-release is supposed to be a build root. And
> this directory is added to gitignore. Actually, build directory can be
> everywhere, but you should pass path to dir, that contains root
> CMakeLists.txt. Usually it is parent directory of cmake-build-release, so
> double dot is used. It is so common pattern of usage and I simply cannot
> understand why it is misleading.
>
> ср, 1 июл. 2020 г., 0:48 Pavel Tupitsyn :
>
> > This is awesome, thanks everyone!
> >
> > I've tried following the instructions, and the following two steps seem
> to
> > be misleading:
> > * mkdir cmake-build-[release|debug]
> > * cd ./cmake-build-[release|debug]
> >
> > When I run cmake in the newly created cmake-build-debug dir, I get:
> > CMake Error: The source directory
> > "/home/pavel/w/ignite/modules/platforms/cpp/cmake-build-release" does not
> > appear to contain CMakeLists.txt.
> >
> > If I skip those 2 steps, I can build Ignite C++ and run tests with ctest
> on
> > Ubuntu 20.04.
> >
> >
> > Another observation: building the project produces untracked git files.
> > Should we update gitignore accordingly?
> >
> >
> > Thanks,
> > Pavel
> >
> >
> > On Tue, Jun 30, 2020 at 9:33 PM Ivan Daschinsky 
> > wrote:
> >
> > > Ok, CMake now is the only option to build C++ on non-windows platforms.
> > > Autotools is removed from master.
> > >
> > > Many thanks to Igor Sapego, Zhenya Stanilovsky, Nickolay Izhikov and
> Ilya
> > > Kasnacheev for review, testing and suggestions.
> > >
> > > вт, 23 июн. 2020 г. в 18:42, Ivan Daschinsky :
> > >
> > > > I suppose, that removal of autotools from source code is a question
> of
> > a
> > > > week. There is no need to support it.
> > > >
> > > > вт, 23 июн. 2020 г., 18:38 Ilya Kasnacheev <
> ilya.kasnach...@gmail.com
> > >:
> > > >
> > > >> Hello!
> > > >>
> > > >> Once you do that, I think it would make sense to remove autotools
> > > >> invocation from artifact build process. In the future we may choose
> to
> > > >> remove autotools support entirely.
> > > >>
> > > >> Regards,
> > > >> --
> > > >> Ilya Kasnacheev
> > > >>
> > > >>
> > > >> вт, 23 июн. 2020 г. в 18:00, Petr Ivanov :
> > > >>
> > > >> > That host was down for some time and got up only recently.
> > > >> > Installed cmake there also.
> > > >> >
> > > >> >
> > > >> >
> > > >> > > On 23 Jun 2020, at 17:39, Ivan Daschinsky 
> > > >> wrote:
> > > >> > >
> > > >> > > Petr, I see, that cmake is missing on aitc10_05 but it is in
> pool
> > > and
> > > >> > > trying to run build.
> > > >> > >
> > > >> > > [1] --
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformCPPCMakeLinux/5412025
> > > >> > >
> > > >> > > вт, 23 июн. 2020 г. в 17:33, Ivan Daschinsky <
> ivanda...@gmail.com
> > >:
> > > >> > >
> > > >> >  For the sake of discretion, I'd purpose to remove old suites
> > from
> > > >> Run
> > > >> > >> All and archive or pause them for some time before removal.
> > > >> > >> Agree, I was talking about removal from RunAll chain, complete
> > > >> removal
> > > >> > is
> > > >> > >> not necessary.
> > > >> > >> But after private discussion with Igor Sapego, me and he
> decided
> > to
> > > >> wait
> > > >> > >> for a week before exclusion of these suites from RunAll.
> > > >> > >>
> > > >> > >> вт, 23 июн. 2020 г. в 17:21, Petr Ivanov  >:
> > > >> > >>
> > > >> > >>> For the sake of discretion, I'd purpose to remove old suites
> > from
> > > >> Run
> > > >> > All
> > > >> > >>> and archive or pause them for some time before removal.
> > > >> > >>>
> > > >> > >>>
> > > >> >  On 23 Jun 2020, at 13:26, Nikolay Izhikov <
> nizhi...@apache.org
> > >
> > > >> > wrote:
> > > >> > 
> > > >> > > So, folks, is it ok to remove old suites from build chain
> > > >> > 
> > > >> >  +1 from me.
> > > >> > 
> > > >> > 
> > > >> > > 23 июня 2020 г., в 13:15, Ivan Daschinsky <
> > ivanda...@gmail.com>
> > > >> > >>> написал(а):
> > > >> > >
> > > >> > > Well, new suites added to RunAll and all seems to be ok.
> > > >> > >
> > > >> > > I think it is time to remove old suites.
> > > >> > > WDYT?
> > > >> > >
> > > >> > > Also, I created patch with removal of autotools, but old
> > suites
> > > >> > should
> > > >> > >>> be
> > > >> > > removed first.
> > > >> > >
> > > >> > > So, folks, is it ok to remove old suites from build chain?
> > > >> > >
> > > >> > > вт, 23 июн. 2020 г. в 10:36, Ivan Daschinsky <
> > > ivanda...@gmail.com
> > > >> >:
> > > >> > >
> > > >> > >> Ok, I changed agents requirements to builds and add them to
> > > >> 

Re: [DISCUSSION] Ignite.C++ and CMake

[Pavel Tupitsyn]

I think we could add a script or two, like cmake-build.sh and ctest.sh,
which work right away and can be used as a reference.

This is useful for Igniters like me who need to check some C++ related
things quickly,
but do that rarely enough to forget the build system quirks.

On Wed, Jul 1, 2020 at 10:53 AM Ivan Daschinsky  wrote:

> No, I am really curious if this instruction complete or not. Actually, Ilya
> Kasnacheev asked me about the same thing as you. And may be instruction is
> not so obvious and should be reworked. You know, that developers are not
> usually great in writing documentation.
>
> ср, 1 июл. 2020 г., 10:37 Pavel Tupitsyn :
>
> > Ivan,
> >
> > Thank you for such a detailed explanation!
> > I am sorry if I upset you.
> >
> > I just wanted to make sure that instructions are correct,
> > and I simply missed those 2 dots. Now it all works perfectly.
> >
> > Pavel
> >
> > On Wed, Jul 1, 2020 at 8:09 AM Ivan Daschinsky 
> > wrote:
> >
> > > Let me explain with details.
> > >
> > > CMake is unusual from other build systems, that it can separate build
> > root
> > > and source root. Moreover, it is strongly discouraged to mix them.
> > > Benefits:
> > > 1. You can have many build with different options using same source.
> > > 2. You can build project with different toolchain using same source.
> > > 3. You can build project for different platforms using same source
> > > (cross-compilation, docker, etc.)
> > >
> > > Common patter is:
> > > 1. Create build root.
> > > 2. Change current dir to build root.
> > > 3. Invoke cmake in build root, pointing to source root.
> > >
> > > Usually build root is subdirectory, of source root. So, as it mentioned
> > in
> > > DEVNOTES.txt, usual steps are:
> > > 1. mdkir  (usually named
> > cmake-build-[-]
> > > 2. cd 
> > > 3. cmake [-DOPTION1=VALUE1 -DOPTION2=VALUE2 ... ] .. (NB! This double
> > dots
> > > are important, they points to source root)
> > >
> > > This is so common, that you can hardly find any tutorial about CMake in
> > > google without thes double dots. This is basic of CMake.
> > >
> > > So if you think that we should explain for C++ developers basics of the
> > > most common build system (CMake is really very popular and nowadays
> > usually
> > > must for new projects),
> > > we can add this to DEVNOTES.txt. But I think that is not necessary at
> > all.
> > > For example, we don't explain basics of maven, though it is not obvious
> > at
> > > all as it seems to us, Ignite developers.
> > >
> > > ср, 1 июл. 2020 г. в 06:18, Ivan Daschinsky :
> > >
> > > > Pavel, pay attention to two dots at the end. All build files should
> > stay
> > > > at current dir, and cmake-build-release is supposed to be a build
> root.
> > > And
> > > > this directory is added to gitignore. Actually, build directory can
> be
> > > > everywhere, but you should pass path to dir, that contains root
> > > > CMakeLists.txt. Usually it is parent directory of
> cmake-build-release,
> > so
> > > > double dot is used. It is so common pattern of usage and I simply
> > cannot
> > > > understand why it is misleading.
> > > >
> > > > ср, 1 июл. 2020 г., 0:48 Pavel Tupitsyn :
> > > >
> > > >> This is awesome, thanks everyone!
> > > >>
> > > >> I've tried following the instructions, and the following two steps
> > seem
> > > to
> > > >> be misleading:
> > > >> * mkdir cmake-build-[release|debug]
> > > >> * cd ./cmake-build-[release|debug]
> > > >>
> > > >> When I run cmake in the newly created cmake-build-debug dir, I get:
> > > >> CMake Error: The source directory
> > > >> "/home/pavel/w/ignite/modules/platforms/cpp/cmake-build-release"
> does
> > > not
> > > >> appear to contain CMakeLists.txt.
> > > >>
> > > >> If I skip those 2 steps, I can build Ignite C++ and run tests with
> > ctest
> > > >> on
> > > >> Ubuntu 20.04.
> > > >>
> > > >>
> > > >> Another observation: building the project produces untracked git
> > files.
> > > >> Should we update gitignore accordingly?
> > > >>
> > > >>
> > > >> Thanks,
> > > >> Pavel
> > > >>
> > > >>
> > > >> On Tue, Jun 30, 2020 at 9:33 PM Ivan Daschinsky <
> ivanda...@gmail.com>
> > > >> wrote:
> > > >>
> > > >> > Ok, CMake now is the only option to build C++ on non-windows
> > > platforms.
> > > >> > Autotools is removed from master.
> > > >> >
> > > >> > Many thanks to Igor Sapego, Zhenya Stanilovsky, Nickolay Izhikov
> and
> > > >> Ilya
> > > >> > Kasnacheev for review, testing and suggestions.
> > > >> >
> > > >> > вт, 23 июн. 2020 г. в 18:42, Ivan Daschinsky  >:
> > > >> >
> > > >> > > I suppose, that removal of autotools from source code is a
> > question
> > > >> of a
> > > >> > > week. There is no need to support it.
> > > >> > >
> > > >> > > вт, 23 июн. 2020 г., 18:38 Ilya Kasnacheev <
> > > ilya.kasnach...@gmail.com
> > > >> >:
> > > >> > >
> > > >> > >> Hello!
> > > >> > >>
> > > >> > >> Once you do that, I think it would make sense to remove
> autotools
> > > >> > >> invocation from artifact build process. In the future we 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

No, I am really curious if this instruction complete or not. Actually, Ilya
Kasnacheev asked me about the same thing as you. And may be instruction is
not so obvious and should be reworked. You know, that developers are not
usually great in writing documentation.

ср, 1 июл. 2020 г., 10:37 Pavel Tupitsyn :

> Ivan,
>
> Thank you for such a detailed explanation!
> I am sorry if I upset you.
>
> I just wanted to make sure that instructions are correct,
> and I simply missed those 2 dots. Now it all works perfectly.
>
> Pavel
>
> On Wed, Jul 1, 2020 at 8:09 AM Ivan Daschinsky 
> wrote:
>
> > Let me explain with details.
> >
> > CMake is unusual from other build systems, that it can separate build
> root
> > and source root. Moreover, it is strongly discouraged to mix them.
> > Benefits:
> > 1. You can have many build with different options using same source.
> > 2. You can build project with different toolchain using same source.
> > 3. You can build project for different platforms using same source
> > (cross-compilation, docker, etc.)
> >
> > Common patter is:
> > 1. Create build root.
> > 2. Change current dir to build root.
> > 3. Invoke cmake in build root, pointing to source root.
> >
> > Usually build root is subdirectory, of source root. So, as it mentioned
> in
> > DEVNOTES.txt, usual steps are:
> > 1. mdkir  (usually named
> cmake-build-[-]
> > 2. cd 
> > 3. cmake [-DOPTION1=VALUE1 -DOPTION2=VALUE2 ... ] .. (NB! This double
> dots
> > are important, they points to source root)
> >
> > This is so common, that you can hardly find any tutorial about CMake in
> > google without thes double dots. This is basic of CMake.
> >
> > So if you think that we should explain for C++ developers basics of the
> > most common build system (CMake is really very popular and nowadays
> usually
> > must for new projects),
> > we can add this to DEVNOTES.txt. But I think that is not necessary at
> all.
> > For example, we don't explain basics of maven, though it is not obvious
> at
> > all as it seems to us, Ignite developers.
> >
> > ср, 1 июл. 2020 г. в 06:18, Ivan Daschinsky :
> >
> > > Pavel, pay attention to two dots at the end. All build files should
> stay
> > > at current dir, and cmake-build-release is supposed to be a build root.
> > And
> > > this directory is added to gitignore. Actually, build directory can be
> > > everywhere, but you should pass path to dir, that contains root
> > > CMakeLists.txt. Usually it is parent directory of cmake-build-release,
> so
> > > double dot is used. It is so common pattern of usage and I simply
> cannot
> > > understand why it is misleading.
> > >
> > > ср, 1 июл. 2020 г., 0:48 Pavel Tupitsyn :
> > >
> > >> This is awesome, thanks everyone!
> > >>
> > >> I've tried following the instructions, and the following two steps
> seem
> > to
> > >> be misleading:
> > >> * mkdir cmake-build-[release|debug]
> > >> * cd ./cmake-build-[release|debug]
> > >>
> > >> When I run cmake in the newly created cmake-build-debug dir, I get:
> > >> CMake Error: The source directory
> > >> "/home/pavel/w/ignite/modules/platforms/cpp/cmake-build-release" does
> > not
> > >> appear to contain CMakeLists.txt.
> > >>
> > >> If I skip those 2 steps, I can build Ignite C++ and run tests with
> ctest
> > >> on
> > >> Ubuntu 20.04.
> > >>
> > >>
> > >> Another observation: building the project produces untracked git
> files.
> > >> Should we update gitignore accordingly?
> > >>
> > >>
> > >> Thanks,
> > >> Pavel
> > >>
> > >>
> > >> On Tue, Jun 30, 2020 at 9:33 PM Ivan Daschinsky 
> > >> wrote:
> > >>
> > >> > Ok, CMake now is the only option to build C++ on non-windows
> > platforms.
> > >> > Autotools is removed from master.
> > >> >
> > >> > Many thanks to Igor Sapego, Zhenya Stanilovsky, Nickolay Izhikov and
> > >> Ilya
> > >> > Kasnacheev for review, testing and suggestions.
> > >> >
> > >> > вт, 23 июн. 2020 г. в 18:42, Ivan Daschinsky :
> > >> >
> > >> > > I suppose, that removal of autotools from source code is a
> question
> > >> of a
> > >> > > week. There is no need to support it.
> > >> > >
> > >> > > вт, 23 июн. 2020 г., 18:38 Ilya Kasnacheev <
> > ilya.kasnach...@gmail.com
> > >> >:
> > >> > >
> > >> > >> Hello!
> > >> > >>
> > >> > >> Once you do that, I think it would make sense to remove autotools
> > >> > >> invocation from artifact build process. In the future we may
> choose
> > >> to
> > >> > >> remove autotools support entirely.
> > >> > >>
> > >> > >> Regards,
> > >> > >> --
> > >> > >> Ilya Kasnacheev
> > >> > >>
> > >> > >>
> > >> > >> вт, 23 июн. 2020 г. в 18:00, Petr Ivanov :
> > >> > >>
> > >> > >> > That host was down for some time and got up only recently.
> > >> > >> > Installed cmake there also.
> > >> > >> >
> > >> > >> >
> > >> > >> >
> > >> > >> > > On 23 Jun 2020, at 17:39, Ivan Daschinsky <
> ivanda...@gmail.com
> > >
> > >> > >> wrote:
> > >> > >> > >
> > >> > >> > > Petr, I see, that cmake is missing on aitc10_05 but it is in
> > pool
> > >> > and
> > >> > >> > > 

Re: [DISCUSSION] Ignite.C++ and CMake

[Pavel Tupitsyn]

Ivan,

Thank you for such a detailed explanation!
I am sorry if I upset you.

I just wanted to make sure that instructions are correct,
and I simply missed those 2 dots. Now it all works perfectly.

Pavel

On Wed, Jul 1, 2020 at 8:09 AM Ivan Daschinsky  wrote:

> Let me explain with details.
>
> CMake is unusual from other build systems, that it can separate build root
> and source root. Moreover, it is strongly discouraged to mix them.
> Benefits:
> 1. You can have many build with different options using same source.
> 2. You can build project with different toolchain using same source.
> 3. You can build project for different platforms using same source
> (cross-compilation, docker, etc.)
>
> Common patter is:
> 1. Create build root.
> 2. Change current dir to build root.
> 3. Invoke cmake in build root, pointing to source root.
>
> Usually build root is subdirectory, of source root. So, as it mentioned in
> DEVNOTES.txt, usual steps are:
> 1. mdkir  (usually named cmake-build-[-]
> 2. cd 
> 3. cmake [-DOPTION1=VALUE1 -DOPTION2=VALUE2 ... ] .. (NB! This double dots
> are important, they points to source root)
>
> This is so common, that you can hardly find any tutorial about CMake in
> google without thes double dots. This is basic of CMake.
>
> So if you think that we should explain for C++ developers basics of the
> most common build system (CMake is really very popular and nowadays usually
> must for new projects),
> we can add this to DEVNOTES.txt. But I think that is not necessary at all.
> For example, we don't explain basics of maven, though it is not obvious at
> all as it seems to us, Ignite developers.
>
> ср, 1 июл. 2020 г. в 06:18, Ivan Daschinsky :
>
> > Pavel, pay attention to two dots at the end. All build files should stay
> > at current dir, and cmake-build-release is supposed to be a build root.
> And
> > this directory is added to gitignore. Actually, build directory can be
> > everywhere, but you should pass path to dir, that contains root
> > CMakeLists.txt. Usually it is parent directory of cmake-build-release, so
> > double dot is used. It is so common pattern of usage and I simply cannot
> > understand why it is misleading.
> >
> > ср, 1 июл. 2020 г., 0:48 Pavel Tupitsyn :
> >
> >> This is awesome, thanks everyone!
> >>
> >> I've tried following the instructions, and the following two steps seem
> to
> >> be misleading:
> >> * mkdir cmake-build-[release|debug]
> >> * cd ./cmake-build-[release|debug]
> >>
> >> When I run cmake in the newly created cmake-build-debug dir, I get:
> >> CMake Error: The source directory
> >> "/home/pavel/w/ignite/modules/platforms/cpp/cmake-build-release" does
> not
> >> appear to contain CMakeLists.txt.
> >>
> >> If I skip those 2 steps, I can build Ignite C++ and run tests with ctest
> >> on
> >> Ubuntu 20.04.
> >>
> >>
> >> Another observation: building the project produces untracked git files.
> >> Should we update gitignore accordingly?
> >>
> >>
> >> Thanks,
> >> Pavel
> >>
> >>
> >> On Tue, Jun 30, 2020 at 9:33 PM Ivan Daschinsky 
> >> wrote:
> >>
> >> > Ok, CMake now is the only option to build C++ on non-windows
> platforms.
> >> > Autotools is removed from master.
> >> >
> >> > Many thanks to Igor Sapego, Zhenya Stanilovsky, Nickolay Izhikov and
> >> Ilya
> >> > Kasnacheev for review, testing and suggestions.
> >> >
> >> > вт, 23 июн. 2020 г. в 18:42, Ivan Daschinsky :
> >> >
> >> > > I suppose, that removal of autotools from source code is a question
> >> of a
> >> > > week. There is no need to support it.
> >> > >
> >> > > вт, 23 июн. 2020 г., 18:38 Ilya Kasnacheev <
> ilya.kasnach...@gmail.com
> >> >:
> >> > >
> >> > >> Hello!
> >> > >>
> >> > >> Once you do that, I think it would make sense to remove autotools
> >> > >> invocation from artifact build process. In the future we may choose
> >> to
> >> > >> remove autotools support entirely.
> >> > >>
> >> > >> Regards,
> >> > >> --
> >> > >> Ilya Kasnacheev
> >> > >>
> >> > >>
> >> > >> вт, 23 июн. 2020 г. в 18:00, Petr Ivanov :
> >> > >>
> >> > >> > That host was down for some time and got up only recently.
> >> > >> > Installed cmake there also.
> >> > >> >
> >> > >> >
> >> > >> >
> >> > >> > > On 23 Jun 2020, at 17:39, Ivan Daschinsky  >
> >> > >> wrote:
> >> > >> > >
> >> > >> > > Petr, I see, that cmake is missing on aitc10_05 but it is in
> pool
> >> > and
> >> > >> > > trying to run build.
> >> > >> > >
> >> > >> > > [1] --
> >> > >> > >
> >> > >> >
> >> > >>
> >> >
> >>
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformCPPCMakeLinux/5412025
> >> > >> > >
> >> > >> > > вт, 23 июн. 2020 г. в 17:33, Ivan Daschinsky <
> >> ivanda...@gmail.com>:
> >> > >> > >
> >> > >> >  For the sake of discretion, I'd purpose to remove old suites
> >> from
> >> > >> Run
> >> > >> > >> All and archive or pause them for some time before removal.
> >> > >> > >> Agree, I was talking about removal from RunAll chain, complete
> >> > >> removal
> >> > >> > is
> >> > >> > >> not 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

Let me explain with details.

CMake is unusual from other build systems, that it can separate build root
and source root. Moreover, it is strongly discouraged to mix them.
Benefits:
1. You can have many build with different options using same source.
2. You can build project with different toolchain using same source.
3. You can build project for different platforms using same source
(cross-compilation, docker, etc.)

Common patter is:
1. Create build root.
2. Change current dir to build root.
3. Invoke cmake in build root, pointing to source root.

Usually build root is subdirectory, of source root. So, as it mentioned in
DEVNOTES.txt, usual steps are:
1. mdkir  (usually named cmake-build-[-]
2. cd 
3. cmake [-DOPTION1=VALUE1 -DOPTION2=VALUE2 ... ] .. (NB! This double dots
are important, they points to source root)

This is so common, that you can hardly find any tutorial about CMake in
google without thes double dots. This is basic of CMake.

So if you think that we should explain for C++ developers basics of the
most common build system (CMake is really very popular and nowadays usually
must for new projects),
we can add this to DEVNOTES.txt. But I think that is not necessary at all.
For example, we don't explain basics of maven, though it is not obvious at
all as it seems to us, Ignite developers.

ср, 1 июл. 2020 г. в 06:18, Ivan Daschinsky :

> Pavel, pay attention to two dots at the end. All build files should stay
> at current dir, and cmake-build-release is supposed to be a build root. And
> this directory is added to gitignore. Actually, build directory can be
> everywhere, but you should pass path to dir, that contains root
> CMakeLists.txt. Usually it is parent directory of cmake-build-release, so
> double dot is used. It is so common pattern of usage and I simply cannot
> understand why it is misleading.
>
> ср, 1 июл. 2020 г., 0:48 Pavel Tupitsyn :
>
>> This is awesome, thanks everyone!
>>
>> I've tried following the instructions, and the following two steps seem to
>> be misleading:
>> * mkdir cmake-build-[release|debug]
>> * cd ./cmake-build-[release|debug]
>>
>> When I run cmake in the newly created cmake-build-debug dir, I get:
>> CMake Error: The source directory
>> "/home/pavel/w/ignite/modules/platforms/cpp/cmake-build-release" does not
>> appear to contain CMakeLists.txt.
>>
>> If I skip those 2 steps, I can build Ignite C++ and run tests with ctest
>> on
>> Ubuntu 20.04.
>>
>>
>> Another observation: building the project produces untracked git files.
>> Should we update gitignore accordingly?
>>
>>
>> Thanks,
>> Pavel
>>
>>
>> On Tue, Jun 30, 2020 at 9:33 PM Ivan Daschinsky 
>> wrote:
>>
>> > Ok, CMake now is the only option to build C++ on non-windows platforms.
>> > Autotools is removed from master.
>> >
>> > Many thanks to Igor Sapego, Zhenya Stanilovsky, Nickolay Izhikov and
>> Ilya
>> > Kasnacheev for review, testing and suggestions.
>> >
>> > вт, 23 июн. 2020 г. в 18:42, Ivan Daschinsky :
>> >
>> > > I suppose, that removal of autotools from source code is a question
>> of a
>> > > week. There is no need to support it.
>> > >
>> > > вт, 23 июн. 2020 г., 18:38 Ilya Kasnacheev > >:
>> > >
>> > >> Hello!
>> > >>
>> > >> Once you do that, I think it would make sense to remove autotools
>> > >> invocation from artifact build process. In the future we may choose
>> to
>> > >> remove autotools support entirely.
>> > >>
>> > >> Regards,
>> > >> --
>> > >> Ilya Kasnacheev
>> > >>
>> > >>
>> > >> вт, 23 июн. 2020 г. в 18:00, Petr Ivanov :
>> > >>
>> > >> > That host was down for some time and got up only recently.
>> > >> > Installed cmake there also.
>> > >> >
>> > >> >
>> > >> >
>> > >> > > On 23 Jun 2020, at 17:39, Ivan Daschinsky 
>> > >> wrote:
>> > >> > >
>> > >> > > Petr, I see, that cmake is missing on aitc10_05 but it is in pool
>> > and
>> > >> > > trying to run build.
>> > >> > >
>> > >> > > [1] --
>> > >> > >
>> > >> >
>> > >>
>> >
>> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformCPPCMakeLinux/5412025
>> > >> > >
>> > >> > > вт, 23 июн. 2020 г. в 17:33, Ivan Daschinsky <
>> ivanda...@gmail.com>:
>> > >> > >
>> > >> >  For the sake of discretion, I'd purpose to remove old suites
>> from
>> > >> Run
>> > >> > >> All and archive or pause them for some time before removal.
>> > >> > >> Agree, I was talking about removal from RunAll chain, complete
>> > >> removal
>> > >> > is
>> > >> > >> not necessary.
>> > >> > >> But after private discussion with Igor Sapego, me and he
>> decided to
>> > >> wait
>> > >> > >> for a week before exclusion of these suites from RunAll.
>> > >> > >>
>> > >> > >> вт, 23 июн. 2020 г. в 17:21, Petr Ivanov :
>> > >> > >>
>> > >> > >>> For the sake of discretion, I'd purpose to remove old suites
>> from
>> > >> Run
>> > >> > All
>> > >> > >>> and archive or pause them for some time before removal.
>> > >> > >>>
>> > >> > >>>
>> > >> >  On 23 Jun 2020, at 13:26, Nikolay Izhikov <
>> nizhi...@apache.org>
>> > >> > 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

Pavel, pay attention to two dots at the end. All build files should stay at
current dir, and cmake-build-release is supposed to be a build root. And
this directory is added to gitignore. Actually, build directory can be
everywhere, but you should pass path to dir, that contains root
CMakeLists.txt. Usually it is parent directory of cmake-build-release, so
double dot is used. It is so common pattern of usage and I simply cannot
understand why it is misleading.

ср, 1 июл. 2020 г., 0:48 Pavel Tupitsyn :

> This is awesome, thanks everyone!
>
> I've tried following the instructions, and the following two steps seem to
> be misleading:
> * mkdir cmake-build-[release|debug]
> * cd ./cmake-build-[release|debug]
>
> When I run cmake in the newly created cmake-build-debug dir, I get:
> CMake Error: The source directory
> "/home/pavel/w/ignite/modules/platforms/cpp/cmake-build-release" does not
> appear to contain CMakeLists.txt.
>
> If I skip those 2 steps, I can build Ignite C++ and run tests with ctest on
> Ubuntu 20.04.
>
>
> Another observation: building the project produces untracked git files.
> Should we update gitignore accordingly?
>
>
> Thanks,
> Pavel
>
>
> On Tue, Jun 30, 2020 at 9:33 PM Ivan Daschinsky 
> wrote:
>
> > Ok, CMake now is the only option to build C++ on non-windows platforms.
> > Autotools is removed from master.
> >
> > Many thanks to Igor Sapego, Zhenya Stanilovsky, Nickolay Izhikov and Ilya
> > Kasnacheev for review, testing and suggestions.
> >
> > вт, 23 июн. 2020 г. в 18:42, Ivan Daschinsky :
> >
> > > I suppose, that removal of autotools from source code is a question of
> a
> > > week. There is no need to support it.
> > >
> > > вт, 23 июн. 2020 г., 18:38 Ilya Kasnacheev  >:
> > >
> > >> Hello!
> > >>
> > >> Once you do that, I think it would make sense to remove autotools
> > >> invocation from artifact build process. In the future we may choose to
> > >> remove autotools support entirely.
> > >>
> > >> Regards,
> > >> --
> > >> Ilya Kasnacheev
> > >>
> > >>
> > >> вт, 23 июн. 2020 г. в 18:00, Petr Ivanov :
> > >>
> > >> > That host was down for some time and got up only recently.
> > >> > Installed cmake there also.
> > >> >
> > >> >
> > >> >
> > >> > > On 23 Jun 2020, at 17:39, Ivan Daschinsky 
> > >> wrote:
> > >> > >
> > >> > > Petr, I see, that cmake is missing on aitc10_05 but it is in pool
> > and
> > >> > > trying to run build.
> > >> > >
> > >> > > [1] --
> > >> > >
> > >> >
> > >>
> >
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformCPPCMakeLinux/5412025
> > >> > >
> > >> > > вт, 23 июн. 2020 г. в 17:33, Ivan Daschinsky  >:
> > >> > >
> > >> >  For the sake of discretion, I'd purpose to remove old suites
> from
> > >> Run
> > >> > >> All and archive or pause them for some time before removal.
> > >> > >> Agree, I was talking about removal from RunAll chain, complete
> > >> removal
> > >> > is
> > >> > >> not necessary.
> > >> > >> But after private discussion with Igor Sapego, me and he decided
> to
> > >> wait
> > >> > >> for a week before exclusion of these suites from RunAll.
> > >> > >>
> > >> > >> вт, 23 июн. 2020 г. в 17:21, Petr Ivanov :
> > >> > >>
> > >> > >>> For the sake of discretion, I'd purpose to remove old suites
> from
> > >> Run
> > >> > All
> > >> > >>> and archive or pause them for some time before removal.
> > >> > >>>
> > >> > >>>
> > >> >  On 23 Jun 2020, at 13:26, Nikolay Izhikov  >
> > >> > wrote:
> > >> > 
> > >> > > So, folks, is it ok to remove old suites from build chain
> > >> > 
> > >> >  +1 from me.
> > >> > 
> > >> > 
> > >> > > 23 июня 2020 г., в 13:15, Ivan Daschinsky <
> ivanda...@gmail.com>
> > >> > >>> написал(а):
> > >> > >
> > >> > > Well, new suites added to RunAll and all seems to be ok.
> > >> > >
> > >> > > I think it is time to remove old suites.
> > >> > > WDYT?
> > >> > >
> > >> > > Also, I created patch with removal of autotools, but old
> suites
> > >> > should
> > >> > >>> be
> > >> > > removed first.
> > >> > >
> > >> > > So, folks, is it ok to remove old suites from build chain?
> > >> > >
> > >> > > вт, 23 июн. 2020 г. в 10:36, Ivan Daschinsky <
> > ivanda...@gmail.com
> > >> >:
> > >> > >
> > >> > >> Ok, I changed agents requirements to builds and add them to
> > >> runAll
> > >> > >>
> > >> > >> пн, 22 июн. 2020 г. в 22:39, Petr Ivanov <
> mr.wei...@gmail.com
> > >:
> > >> > >>
> > >> > >>> Cmake is installed on all agents (except 10 which is
> currently
> > >> down
> > >> > >>> and
> > >> > >>> will be updated later).
> > >> > >>>
> > >> > >>>
> > >> >  On 22 Jun 2020, at 21:03, Ivan Daschinsky <
> > ivanda...@gmail.com
> > >> >
> > >> > >>> wrote:
> > >> > 
> > >> >  Well, patch is merged. Thank a lot to Igor Sapego for
> review.
> > >> > 
> > >> >  Peter, well, cmake now can be installed on all agent.
> > >> > 
> > >> > 

Re: [DISCUSSION] Ignite.C++ and CMake

[Pavel Tupitsyn]

This is awesome, thanks everyone!

I've tried following the instructions, and the following two steps seem to
be misleading:
* mkdir cmake-build-[release|debug]
* cd ./cmake-build-[release|debug]

When I run cmake in the newly created cmake-build-debug dir, I get:
CMake Error: The source directory
"/home/pavel/w/ignite/modules/platforms/cpp/cmake-build-release" does not
appear to contain CMakeLists.txt.

If I skip those 2 steps, I can build Ignite C++ and run tests with ctest on
Ubuntu 20.04.


Another observation: building the project produces untracked git files.
Should we update gitignore accordingly?


Thanks,
Pavel


On Tue, Jun 30, 2020 at 9:33 PM Ivan Daschinsky  wrote:

> Ok, CMake now is the only option to build C++ on non-windows platforms.
> Autotools is removed from master.
>
> Many thanks to Igor Sapego, Zhenya Stanilovsky, Nickolay Izhikov and Ilya
> Kasnacheev for review, testing and suggestions.
>
> вт, 23 июн. 2020 г. в 18:42, Ivan Daschinsky :
>
> > I suppose, that removal of autotools from source code is a question of a
> > week. There is no need to support it.
> >
> > вт, 23 июн. 2020 г., 18:38 Ilya Kasnacheev :
> >
> >> Hello!
> >>
> >> Once you do that, I think it would make sense to remove autotools
> >> invocation from artifact build process. In the future we may choose to
> >> remove autotools support entirely.
> >>
> >> Regards,
> >> --
> >> Ilya Kasnacheev
> >>
> >>
> >> вт, 23 июн. 2020 г. в 18:00, Petr Ivanov :
> >>
> >> > That host was down for some time and got up only recently.
> >> > Installed cmake there also.
> >> >
> >> >
> >> >
> >> > > On 23 Jun 2020, at 17:39, Ivan Daschinsky 
> >> wrote:
> >> > >
> >> > > Petr, I see, that cmake is missing on aitc10_05 but it is in pool
> and
> >> > > trying to run build.
> >> > >
> >> > > [1] --
> >> > >
> >> >
> >>
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformCPPCMakeLinux/5412025
> >> > >
> >> > > вт, 23 июн. 2020 г. в 17:33, Ivan Daschinsky :
> >> > >
> >> >  For the sake of discretion, I'd purpose to remove old suites from
> >> Run
> >> > >> All and archive or pause them for some time before removal.
> >> > >> Agree, I was talking about removal from RunAll chain, complete
> >> removal
> >> > is
> >> > >> not necessary.
> >> > >> But after private discussion with Igor Sapego, me and he decided to
> >> wait
> >> > >> for a week before exclusion of these suites from RunAll.
> >> > >>
> >> > >> вт, 23 июн. 2020 г. в 17:21, Petr Ivanov :
> >> > >>
> >> > >>> For the sake of discretion, I'd purpose to remove old suites from
> >> Run
> >> > All
> >> > >>> and archive or pause them for some time before removal.
> >> > >>>
> >> > >>>
> >> >  On 23 Jun 2020, at 13:26, Nikolay Izhikov 
> >> > wrote:
> >> > 
> >> > > So, folks, is it ok to remove old suites from build chain
> >> > 
> >> >  +1 from me.
> >> > 
> >> > 
> >> > > 23 июня 2020 г., в 13:15, Ivan Daschinsky 
> >> > >>> написал(а):
> >> > >
> >> > > Well, new suites added to RunAll and all seems to be ok.
> >> > >
> >> > > I think it is time to remove old suites.
> >> > > WDYT?
> >> > >
> >> > > Also, I created patch with removal of autotools, but old suites
> >> > should
> >> > >>> be
> >> > > removed first.
> >> > >
> >> > > So, folks, is it ok to remove old suites from build chain?
> >> > >
> >> > > вт, 23 июн. 2020 г. в 10:36, Ivan Daschinsky <
> ivanda...@gmail.com
> >> >:
> >> > >
> >> > >> Ok, I changed agents requirements to builds and add them to
> >> runAll
> >> > >>
> >> > >> пн, 22 июн. 2020 г. в 22:39, Petr Ivanov  >:
> >> > >>
> >> > >>> Cmake is installed on all agents (except 10 which is currently
> >> down
> >> > >>> and
> >> > >>> will be updated later).
> >> > >>>
> >> > >>>
> >> >  On 22 Jun 2020, at 21:03, Ivan Daschinsky <
> ivanda...@gmail.com
> >> >
> >> > >>> wrote:
> >> > 
> >> >  Well, patch is merged. Thank a lot to Igor Sapego for review.
> >> > 
> >> >  Peter, well, cmake now can be installed on all agent.
> >> > 
> >> >  I think it's time to add cmake suites to runAll and exclude
> old
> >> > >>> suites
> >> > >>> from
> >> >  it.
> >> > 
> >> >  Patch with removing autotools I Will submit in few days.
> >> > 
> >> >  пн, 22 июн. 2020 г., 20:25 Ivan Daschinsky <
> >> ivanda...@gmail.com>:
> >> > 
> >> > > Hi folks!
> >> > >
> >> > > Good news -- I successfully created 2 CMake suites [1] [2]
> and
> >> > they
> >> > >>> works
> >> > > as a charm.
> >> > > Many thanks to Ilya Kasnacheev for giving me permissions and
> >> to
> >> > >>> Peter
> >> > > Ivanov for installing cmake and giving a whole agent for
> >> testing.
> >> > >
> >> > > [1] --
> >> > >
> >> > >>>
> >> > >>>
> >> >
> >>
> 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

Ok, CMake now is the only option to build C++ on non-windows platforms.
Autotools is removed from master.

Many thanks to Igor Sapego, Zhenya Stanilovsky, Nickolay Izhikov and Ilya
Kasnacheev for review, testing and suggestions.

вт, 23 июн. 2020 г. в 18:42, Ivan Daschinsky :

> I suppose, that removal of autotools from source code is a question of a
> week. There is no need to support it.
>
> вт, 23 июн. 2020 г., 18:38 Ilya Kasnacheev :
>
>> Hello!
>>
>> Once you do that, I think it would make sense to remove autotools
>> invocation from artifact build process. In the future we may choose to
>> remove autotools support entirely.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> вт, 23 июн. 2020 г. в 18:00, Petr Ivanov :
>>
>> > That host was down for some time and got up only recently.
>> > Installed cmake there also.
>> >
>> >
>> >
>> > > On 23 Jun 2020, at 17:39, Ivan Daschinsky 
>> wrote:
>> > >
>> > > Petr, I see, that cmake is missing on aitc10_05 but it is in pool and
>> > > trying to run build.
>> > >
>> > > [1] --
>> > >
>> >
>> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformCPPCMakeLinux/5412025
>> > >
>> > > вт, 23 июн. 2020 г. в 17:33, Ivan Daschinsky :
>> > >
>> >  For the sake of discretion, I'd purpose to remove old suites from
>> Run
>> > >> All and archive or pause them for some time before removal.
>> > >> Agree, I was talking about removal from RunAll chain, complete
>> removal
>> > is
>> > >> not necessary.
>> > >> But after private discussion with Igor Sapego, me and he decided to
>> wait
>> > >> for a week before exclusion of these suites from RunAll.
>> > >>
>> > >> вт, 23 июн. 2020 г. в 17:21, Petr Ivanov :
>> > >>
>> > >>> For the sake of discretion, I'd purpose to remove old suites from
>> Run
>> > All
>> > >>> and archive or pause them for some time before removal.
>> > >>>
>> > >>>
>> >  On 23 Jun 2020, at 13:26, Nikolay Izhikov 
>> > wrote:
>> > 
>> > > So, folks, is it ok to remove old suites from build chain
>> > 
>> >  +1 from me.
>> > 
>> > 
>> > > 23 июня 2020 г., в 13:15, Ivan Daschinsky 
>> > >>> написал(а):
>> > >
>> > > Well, new suites added to RunAll and all seems to be ok.
>> > >
>> > > I think it is time to remove old suites.
>> > > WDYT?
>> > >
>> > > Also, I created patch with removal of autotools, but old suites
>> > should
>> > >>> be
>> > > removed first.
>> > >
>> > > So, folks, is it ok to remove old suites from build chain?
>> > >
>> > > вт, 23 июн. 2020 г. в 10:36, Ivan Daschinsky > >:
>> > >
>> > >> Ok, I changed agents requirements to builds and add them to
>> runAll
>> > >>
>> > >> пн, 22 июн. 2020 г. в 22:39, Petr Ivanov :
>> > >>
>> > >>> Cmake is installed on all agents (except 10 which is currently
>> down
>> > >>> and
>> > >>> will be updated later).
>> > >>>
>> > >>>
>> >  On 22 Jun 2020, at 21:03, Ivan Daschinsky > >
>> > >>> wrote:
>> > 
>> >  Well, patch is merged. Thank a lot to Igor Sapego for review.
>> > 
>> >  Peter, well, cmake now can be installed on all agent.
>> > 
>> >  I think it's time to add cmake suites to runAll and exclude old
>> > >>> suites
>> > >>> from
>> >  it.
>> > 
>> >  Patch with removing autotools I Will submit in few days.
>> > 
>> >  пн, 22 июн. 2020 г., 20:25 Ivan Daschinsky <
>> ivanda...@gmail.com>:
>> > 
>> > > Hi folks!
>> > >
>> > > Good news -- I successfully created 2 CMake suites [1] [2] and
>> > they
>> > >>> works
>> > > as a charm.
>> > > Many thanks to Ilya Kasnacheev for giving me permissions and
>> to
>> > >>> Peter
>> > > Ivanov for installing cmake and giving a whole agent for
>> testing.
>> > >
>> > > [1] --
>> > >
>> > >>>
>> > >>>
>> >
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinuxClang_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
>> > > [2] --
>> > >
>> > >>>
>> > >>>
>> >
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinux_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
>> > >
>> > > пн, 22 июн. 2020 г. в 12:03, Ilya Kasnacheev <
>> > >>> ilya.kasnach...@gmail.com>:
>> > >
>> > >> Hello!
>> > >>
>> > >> I think you should contact Peter Ivanov if you want anything
>> to
>> > be
>> > >> installed on agents.
>> > >>
>> > >> Regards,
>> > >> --
>> > >> Ilya Kasnacheev
>> > >>
>> > >>
>> > >> пн, 22 июн. 2020 г. в 12:00, Ivan Daschinsky <
>> > ivanda...@gmail.com
>> >  :
>> > >>
>> > >>> Actually, I'm going to create 2 new suites based on existing
>> > >>> ones:
>> > >>> 1. Platform C++ CMake 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

I suppose, that removal of autotools from source code is a question of a
week. There is no need to support it.

вт, 23 июн. 2020 г., 18:38 Ilya Kasnacheev :

> Hello!
>
> Once you do that, I think it would make sense to remove autotools
> invocation from artifact build process. In the future we may choose to
> remove autotools support entirely.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 23 июн. 2020 г. в 18:00, Petr Ivanov :
>
> > That host was down for some time and got up only recently.
> > Installed cmake there also.
> >
> >
> >
> > > On 23 Jun 2020, at 17:39, Ivan Daschinsky  wrote:
> > >
> > > Petr, I see, that cmake is missing on aitc10_05 but it is in pool and
> > > trying to run build.
> > >
> > > [1] --
> > >
> >
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformCPPCMakeLinux/5412025
> > >
> > > вт, 23 июн. 2020 г. в 17:33, Ivan Daschinsky :
> > >
> >  For the sake of discretion, I'd purpose to remove old suites from
> Run
> > >> All and archive or pause them for some time before removal.
> > >> Agree, I was talking about removal from RunAll chain, complete removal
> > is
> > >> not necessary.
> > >> But after private discussion with Igor Sapego, me and he decided to
> wait
> > >> for a week before exclusion of these suites from RunAll.
> > >>
> > >> вт, 23 июн. 2020 г. в 17:21, Petr Ivanov :
> > >>
> > >>> For the sake of discretion, I'd purpose to remove old suites from Run
> > All
> > >>> and archive or pause them for some time before removal.
> > >>>
> > >>>
> >  On 23 Jun 2020, at 13:26, Nikolay Izhikov 
> > wrote:
> > 
> > > So, folks, is it ok to remove old suites from build chain
> > 
> >  +1 from me.
> > 
> > 
> > > 23 июня 2020 г., в 13:15, Ivan Daschinsky 
> > >>> написал(а):
> > >
> > > Well, new suites added to RunAll and all seems to be ok.
> > >
> > > I think it is time to remove old suites.
> > > WDYT?
> > >
> > > Also, I created patch with removal of autotools, but old suites
> > should
> > >>> be
> > > removed first.
> > >
> > > So, folks, is it ok to remove old suites from build chain?
> > >
> > > вт, 23 июн. 2020 г. в 10:36, Ivan Daschinsky  >:
> > >
> > >> Ok, I changed agents requirements to builds and add them to runAll
> > >>
> > >> пн, 22 июн. 2020 г. в 22:39, Petr Ivanov :
> > >>
> > >>> Cmake is installed on all agents (except 10 which is currently
> down
> > >>> and
> > >>> will be updated later).
> > >>>
> > >>>
> >  On 22 Jun 2020, at 21:03, Ivan Daschinsky 
> > >>> wrote:
> > 
> >  Well, patch is merged. Thank a lot to Igor Sapego for review.
> > 
> >  Peter, well, cmake now can be installed on all agent.
> > 
> >  I think it's time to add cmake suites to runAll and exclude old
> > >>> suites
> > >>> from
> >  it.
> > 
> >  Patch with removing autotools I Will submit in few days.
> > 
> >  пн, 22 июн. 2020 г., 20:25 Ivan Daschinsky  >:
> > 
> > > Hi folks!
> > >
> > > Good news -- I successfully created 2 CMake suites [1] [2] and
> > they
> > >>> works
> > > as a charm.
> > > Many thanks to Ilya Kasnacheev for giving me permissions and to
> > >>> Peter
> > > Ivanov for installing cmake and giving a whole agent for
> testing.
> > >
> > > [1] --
> > >
> > >>>
> > >>>
> >
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinuxClang_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
> > > [2] --
> > >
> > >>>
> > >>>
> >
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinux_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
> > >
> > > пн, 22 июн. 2020 г. в 12:03, Ilya Kasnacheev <
> > >>> ilya.kasnach...@gmail.com>:
> > >
> > >> Hello!
> > >>
> > >> I think you should contact Peter Ivanov if you want anything
> to
> > be
> > >> installed on agents.
> > >>
> > >> Regards,
> > >> --
> > >> Ilya Kasnacheev
> > >>
> > >>
> > >> пн, 22 июн. 2020 г. в 12:00, Ivan Daschinsky <
> > ivanda...@gmail.com
> >  :
> > >>
> > >>> Actually, I'm going to create 2 new suites based on existing
> > >>> ones:
> > >>> 1. Platform C++ CMake (Linux)
> > >>> 2. Platform C++ CMake (Linux Clang)
> > >>>
> > >>> Ilya, thank you very much. But, despite the fact, that I have
> > >> permissions,
> > >>> it seems that it's impossible to install something (namely,
> > >>> CMake) on
> > >>> agents.
> > >>> How can I do this obviously essential task?
> > >>>
> > >>> пн, 22 июн. 2020 г. в 11:30, Ilya Kasnacheev <
> > >>> 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ilya Kasnacheev]

Hello!

Once you do that, I think it would make sense to remove autotools
invocation from artifact build process. In the future we may choose to
remove autotools support entirely.

Regards,
-- 
Ilya Kasnacheev


вт, 23 июн. 2020 г. в 18:00, Petr Ivanov :

> That host was down for some time and got up only recently.
> Installed cmake there also.
>
>
>
> > On 23 Jun 2020, at 17:39, Ivan Daschinsky  wrote:
> >
> > Petr, I see, that cmake is missing on aitc10_05 but it is in pool and
> > trying to run build.
> >
> > [1] --
> >
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformCPPCMakeLinux/5412025
> >
> > вт, 23 июн. 2020 г. в 17:33, Ivan Daschinsky :
> >
>  For the sake of discretion, I'd purpose to remove old suites from Run
> >> All and archive or pause them for some time before removal.
> >> Agree, I was talking about removal from RunAll chain, complete removal
> is
> >> not necessary.
> >> But after private discussion with Igor Sapego, me and he decided to wait
> >> for a week before exclusion of these suites from RunAll.
> >>
> >> вт, 23 июн. 2020 г. в 17:21, Petr Ivanov :
> >>
> >>> For the sake of discretion, I'd purpose to remove old suites from Run
> All
> >>> and archive or pause them for some time before removal.
> >>>
> >>>
>  On 23 Jun 2020, at 13:26, Nikolay Izhikov 
> wrote:
> 
> > So, folks, is it ok to remove old suites from build chain
> 
>  +1 from me.
> 
> 
> > 23 июня 2020 г., в 13:15, Ivan Daschinsky 
> >>> написал(а):
> >
> > Well, new suites added to RunAll and all seems to be ok.
> >
> > I think it is time to remove old suites.
> > WDYT?
> >
> > Also, I created patch with removal of autotools, but old suites
> should
> >>> be
> > removed first.
> >
> > So, folks, is it ok to remove old suites from build chain?
> >
> > вт, 23 июн. 2020 г. в 10:36, Ivan Daschinsky :
> >
> >> Ok, I changed agents requirements to builds and add them to runAll
> >>
> >> пн, 22 июн. 2020 г. в 22:39, Petr Ivanov :
> >>
> >>> Cmake is installed on all agents (except 10 which is currently down
> >>> and
> >>> will be updated later).
> >>>
> >>>
>  On 22 Jun 2020, at 21:03, Ivan Daschinsky 
> >>> wrote:
> 
>  Well, patch is merged. Thank a lot to Igor Sapego for review.
> 
>  Peter, well, cmake now can be installed on all agent.
> 
>  I think it's time to add cmake suites to runAll and exclude old
> >>> suites
> >>> from
>  it.
> 
>  Patch with removing autotools I Will submit in few days.
> 
>  пн, 22 июн. 2020 г., 20:25 Ivan Daschinsky :
> 
> > Hi folks!
> >
> > Good news -- I successfully created 2 CMake suites [1] [2] and
> they
> >>> works
> > as a charm.
> > Many thanks to Ilya Kasnacheev for giving me permissions and to
> >>> Peter
> > Ivanov for installing cmake and giving a whole agent for testing.
> >
> > [1] --
> >
> >>>
> >>>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinuxClang_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
> > [2] --
> >
> >>>
> >>>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinux_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
> >
> > пн, 22 июн. 2020 г. в 12:03, Ilya Kasnacheev <
> >>> ilya.kasnach...@gmail.com>:
> >
> >> Hello!
> >>
> >> I think you should contact Peter Ivanov if you want anything to
> be
> >> installed on agents.
> >>
> >> Regards,
> >> --
> >> Ilya Kasnacheev
> >>
> >>
> >> пн, 22 июн. 2020 г. в 12:00, Ivan Daschinsky <
> ivanda...@gmail.com
>  :
> >>
> >>> Actually, I'm going to create 2 new suites based on existing
> >>> ones:
> >>> 1. Platform C++ CMake (Linux)
> >>> 2. Platform C++ CMake (Linux Clang)
> >>>
> >>> Ilya, thank you very much. But, despite the fact, that I have
> >> permissions,
> >>> it seems that it's impossible to install something (namely,
> >>> CMake) on
> >>> agents.
> >>> How can I do this obviously essential task?
> >>>
> >>> пн, 22 июн. 2020 г. в 11:30, Ilya Kasnacheev <
> >>> ilya.kasnach...@gmail.com
> >>> :
> >>>
>  Hello!
> 
>  I have assigned roles on TC, you can now work on these builds.
> 
>  Please describe your changes on development list so that
> people
> >>> understand
>  what is going on.
> 
>  Regards,
>  --
>  Ilya Kasnacheev
> 
> 
>  вс, 21 июн. 2020 г. в 17:35, 

Re: [DISCUSSION] Ignite.C++ and CMake

[Petr Ivanov]

That host was down for some time and got up only recently.
Installed cmake there also.



> On 23 Jun 2020, at 17:39, Ivan Daschinsky  wrote:
> 
> Petr, I see, that cmake is missing on aitc10_05 but it is in pool and
> trying to run build.
> 
> [1] --
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformCPPCMakeLinux/5412025
> 
> вт, 23 июн. 2020 г. в 17:33, Ivan Daschinsky :
> 
 For the sake of discretion, I'd purpose to remove old suites from Run
>> All and archive or pause them for some time before removal.
>> Agree, I was talking about removal from RunAll chain, complete removal is
>> not necessary.
>> But after private discussion with Igor Sapego, me and he decided to wait
>> for a week before exclusion of these suites from RunAll.
>> 
>> вт, 23 июн. 2020 г. в 17:21, Petr Ivanov :
>> 
>>> For the sake of discretion, I'd purpose to remove old suites from Run All
>>> and archive or pause them for some time before removal.
>>> 
>>> 
 On 23 Jun 2020, at 13:26, Nikolay Izhikov  wrote:
 
> So, folks, is it ok to remove old suites from build chain
 
 +1 from me.
 
 
> 23 июня 2020 г., в 13:15, Ivan Daschinsky 
>>> написал(а):
> 
> Well, new suites added to RunAll and all seems to be ok.
> 
> I think it is time to remove old suites.
> WDYT?
> 
> Also, I created patch with removal of autotools, but old suites should
>>> be
> removed first.
> 
> So, folks, is it ok to remove old suites from build chain?
> 
> вт, 23 июн. 2020 г. в 10:36, Ivan Daschinsky :
> 
>> Ok, I changed agents requirements to builds and add them to runAll
>> 
>> пн, 22 июн. 2020 г. в 22:39, Petr Ivanov :
>> 
>>> Cmake is installed on all agents (except 10 which is currently down
>>> and
>>> will be updated later).
>>> 
>>> 
 On 22 Jun 2020, at 21:03, Ivan Daschinsky 
>>> wrote:
 
 Well, patch is merged. Thank a lot to Igor Sapego for review.
 
 Peter, well, cmake now can be installed on all agent.
 
 I think it's time to add cmake suites to runAll and exclude old
>>> suites
>>> from
 it.
 
 Patch with removing autotools I Will submit in few days.
 
 пн, 22 июн. 2020 г., 20:25 Ivan Daschinsky :
 
> Hi folks!
> 
> Good news -- I successfully created 2 CMake suites [1] [2] and they
>>> works
> as a charm.
> Many thanks to Ilya Kasnacheev for giving me permissions and to
>>> Peter
> Ivanov for installing cmake and giving a whole agent for testing.
> 
> [1] --
> 
>>> 
>>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinuxClang_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
> [2] --
> 
>>> 
>>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinux_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
> 
> пн, 22 июн. 2020 г. в 12:03, Ilya Kasnacheev <
>>> ilya.kasnach...@gmail.com>:
> 
>> Hello!
>> 
>> I think you should contact Peter Ivanov if you want anything to be
>> installed on agents.
>> 
>> Regards,
>> --
>> Ilya Kasnacheev
>> 
>> 
>> пн, 22 июн. 2020 г. в 12:00, Ivan Daschinsky >>> :
>> 
>>> Actually, I'm going to create 2 new suites based on existing
>>> ones:
>>> 1. Platform C++ CMake (Linux)
>>> 2. Platform C++ CMake (Linux Clang)
>>> 
>>> Ilya, thank you very much. But, despite the fact, that I have
>> permissions,
>>> it seems that it's impossible to install something (namely,
>>> CMake) on
>>> agents.
>>> How can I do this obviously essential task?
>>> 
>>> пн, 22 июн. 2020 г. в 11:30, Ilya Kasnacheev <
>>> ilya.kasnach...@gmail.com
>>> :
>>> 
 Hello!
 
 I have assigned roles on TC, you can now work on these builds.
 
 Please describe your changes on development list so that people
>>> understand
 what is going on.
 
 Regards,
 --
 Ilya Kasnacheev
 
 
 вс, 21 июн. 2020 г. в 17:35, Ivan Daschinsky <
>>> ivanda...@gmail.com>:
 
> Hi folks.
> 
> Patch is rigorously tested and with Igor Sapego help it is
>>> possible
>> to
> build with cmake Ignite.C++  even on windows.
> But, it's required to make some TC suites and tune them, in
>>> order
>>> to
 patch
> be merged.
> Unfortunately, I am not a commiter and I doesn't have rights to
>> create
> suites. Also, AFAIK, 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

Petr, I see, that cmake is missing on aitc10_05 but it is in pool and
trying to run build.

[1] --
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformCPPCMakeLinux/5412025

вт, 23 июн. 2020 г. в 17:33, Ivan Daschinsky :

> >> For the sake of discretion, I'd purpose to remove old suites from Run
> All and archive or pause them for some time before removal.
> Agree, I was talking about removal from RunAll chain, complete removal is
> not necessary.
> But after private discussion with Igor Sapego, me and he decided to wait
> for a week before exclusion of these suites from RunAll.
>
> вт, 23 июн. 2020 г. в 17:21, Petr Ivanov :
>
>> For the sake of discretion, I'd purpose to remove old suites from Run All
>> and archive or pause them for some time before removal.
>>
>>
>> > On 23 Jun 2020, at 13:26, Nikolay Izhikov  wrote:
>> >
>> >> So, folks, is it ok to remove old suites from build chain
>> >
>> > +1 from me.
>> >
>> >
>> >> 23 июня 2020 г., в 13:15, Ivan Daschinsky 
>> написал(а):
>> >>
>> >> Well, new suites added to RunAll and all seems to be ok.
>> >>
>> >> I think it is time to remove old suites.
>> >> WDYT?
>> >>
>> >> Also, I created patch with removal of autotools, but old suites should
>> be
>> >> removed first.
>> >>
>> >> So, folks, is it ok to remove old suites from build chain?
>> >>
>> >> вт, 23 июн. 2020 г. в 10:36, Ivan Daschinsky :
>> >>
>> >>> Ok, I changed agents requirements to builds and add them to runAll
>> >>>
>> >>> пн, 22 июн. 2020 г. в 22:39, Petr Ivanov :
>> >>>
>>  Cmake is installed on all agents (except 10 which is currently down
>> and
>>  will be updated later).
>> 
>> 
>> > On 22 Jun 2020, at 21:03, Ivan Daschinsky 
>> wrote:
>> >
>> > Well, patch is merged. Thank a lot to Igor Sapego for review.
>> >
>> > Peter, well, cmake now can be installed on all agent.
>> >
>> > I think it's time to add cmake suites to runAll and exclude old
>> suites
>>  from
>> > it.
>> >
>> > Patch with removing autotools I Will submit in few days.
>> >
>> > пн, 22 июн. 2020 г., 20:25 Ivan Daschinsky :
>> >
>> >> Hi folks!
>> >>
>> >> Good news -- I successfully created 2 CMake suites [1] [2] and they
>>  works
>> >> as a charm.
>> >> Many thanks to Ilya Kasnacheev for giving me permissions and to
>> Peter
>> >> Ivanov for installing cmake and giving a whole agent for testing.
>> >>
>> >> [1] --
>> >>
>> 
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinuxClang_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
>> >> [2] --
>> >>
>> 
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinux_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
>> >>
>> >> пн, 22 июн. 2020 г. в 12:03, Ilya Kasnacheev <
>>  ilya.kasnach...@gmail.com>:
>> >>
>> >>> Hello!
>> >>>
>> >>> I think you should contact Peter Ivanov if you want anything to be
>> >>> installed on agents.
>> >>>
>> >>> Regards,
>> >>> --
>> >>> Ilya Kasnacheev
>> >>>
>> >>>
>> >>> пн, 22 июн. 2020 г. в 12:00, Ivan Daschinsky > >:
>> >>>
>>  Actually, I'm going to create 2 new suites based on existing
>> ones:
>>  1. Platform C++ CMake (Linux)
>>  2. Platform C++ CMake (Linux Clang)
>> 
>>  Ilya, thank you very much. But, despite the fact, that I have
>> >>> permissions,
>>  it seems that it's impossible to install something (namely,
>> CMake) on
>>  agents.
>>  How can I do this obviously essential task?
>> 
>>  пн, 22 июн. 2020 г. в 11:30, Ilya Kasnacheev <
>>  ilya.kasnach...@gmail.com
>>  :
>> 
>> > Hello!
>> >
>> > I have assigned roles on TC, you can now work on these builds.
>> >
>> > Please describe your changes on development list so that people
>>  understand
>> > what is going on.
>> >
>> > Regards,
>> > --
>> > Ilya Kasnacheev
>> >
>> >
>> > вс, 21 июн. 2020 г. в 17:35, Ivan Daschinsky <
>> ivanda...@gmail.com>:
>> >
>> >> Hi folks.
>> >>
>> >> Patch is rigorously tested and with Igor Sapego help it is
>> possible
>> >>> to
>> >> build with cmake Ignite.C++  even on windows.
>> >> But, it's required to make some TC suites and tune them, in
>> order
>>  to
>> > patch
>> >> be merged.
>> >> Unfortunately, I am not a commiter and I doesn't have rights to
>> >>> create
>> >> suites. Also, AFAIK, Igor currently is quite busy and doesn't
>> have
>> >>> much
>> >> time to do this task by himself.
>> >> So I need some help from community. Is it possible to grant me
>> some
>> > rights
>> >> to 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

>> For the sake of discretion, I'd purpose to remove old suites from Run
All and archive or pause them for some time before removal.
Agree, I was talking about removal from RunAll chain, complete removal is
not necessary.
But after private discussion with Igor Sapego, me and he decided to wait
for a week before exclusion of these suites from RunAll.

вт, 23 июн. 2020 г. в 17:21, Petr Ivanov :

> For the sake of discretion, I'd purpose to remove old suites from Run All
> and archive or pause them for some time before removal.
>
>
> > On 23 Jun 2020, at 13:26, Nikolay Izhikov  wrote:
> >
> >> So, folks, is it ok to remove old suites from build chain
> >
> > +1 from me.
> >
> >
> >> 23 июня 2020 г., в 13:15, Ivan Daschinsky 
> написал(а):
> >>
> >> Well, new suites added to RunAll and all seems to be ok.
> >>
> >> I think it is time to remove old suites.
> >> WDYT?
> >>
> >> Also, I created patch with removal of autotools, but old suites should
> be
> >> removed first.
> >>
> >> So, folks, is it ok to remove old suites from build chain?
> >>
> >> вт, 23 июн. 2020 г. в 10:36, Ivan Daschinsky :
> >>
> >>> Ok, I changed agents requirements to builds and add them to runAll
> >>>
> >>> пн, 22 июн. 2020 г. в 22:39, Petr Ivanov :
> >>>
>  Cmake is installed on all agents (except 10 which is currently down
> and
>  will be updated later).
> 
> 
> > On 22 Jun 2020, at 21:03, Ivan Daschinsky 
> wrote:
> >
> > Well, patch is merged. Thank a lot to Igor Sapego for review.
> >
> > Peter, well, cmake now can be installed on all agent.
> >
> > I think it's time to add cmake suites to runAll and exclude old
> suites
>  from
> > it.
> >
> > Patch with removing autotools I Will submit in few days.
> >
> > пн, 22 июн. 2020 г., 20:25 Ivan Daschinsky :
> >
> >> Hi folks!
> >>
> >> Good news -- I successfully created 2 CMake suites [1] [2] and they
>  works
> >> as a charm.
> >> Many thanks to Ilya Kasnacheev for giving me permissions and to
> Peter
> >> Ivanov for installing cmake and giving a whole agent for testing.
> >>
> >> [1] --
> >>
> 
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinuxClang_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
> >> [2] --
> >>
> 
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinux_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
> >>
> >> пн, 22 июн. 2020 г. в 12:03, Ilya Kasnacheev <
>  ilya.kasnach...@gmail.com>:
> >>
> >>> Hello!
> >>>
> >>> I think you should contact Peter Ivanov if you want anything to be
> >>> installed on agents.
> >>>
> >>> Regards,
> >>> --
> >>> Ilya Kasnacheev
> >>>
> >>>
> >>> пн, 22 июн. 2020 г. в 12:00, Ivan Daschinsky  >:
> >>>
>  Actually, I'm going to create 2 new suites based on existing ones:
>  1. Platform C++ CMake (Linux)
>  2. Platform C++ CMake (Linux Clang)
> 
>  Ilya, thank you very much. But, despite the fact, that I have
> >>> permissions,
>  it seems that it's impossible to install something (namely,
> CMake) on
>  agents.
>  How can I do this obviously essential task?
> 
>  пн, 22 июн. 2020 г. в 11:30, Ilya Kasnacheev <
>  ilya.kasnach...@gmail.com
>  :
> 
> > Hello!
> >
> > I have assigned roles on TC, you can now work on these builds.
> >
> > Please describe your changes on development list so that people
>  understand
> > what is going on.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > вс, 21 июн. 2020 г. в 17:35, Ivan Daschinsky <
> ivanda...@gmail.com>:
> >
> >> Hi folks.
> >>
> >> Patch is rigorously tested and with Igor Sapego help it is
> possible
> >>> to
> >> build with cmake Ignite.C++  even on windows.
> >> But, it's required to make some TC suites and tune them, in
> order
>  to
> > patch
> >> be merged.
> >> Unfortunately, I am not a commiter and I doesn't have rights to
> >>> create
> >> suites. Also, AFAIK, Igor currently is quite busy and doesn't
> have
> >>> much
> >> time to do this task by himself.
> >> So I need some help from community. Is it possible to grant me
> some
> > rights
> >> to TC agents?
> >>
> >> ср, 3 июн. 2020 г. в 18:03, Nikolay Izhikov <
> nizhi...@apache.org>:
> >>
> >>> Hello.
> >>>
> >>> I will do review of this changes.
> >>>
>  1 июня 2020 г., в 13:21, Ivan Daschinsky  >
> >>> написал(а):
> 
>  Igor, could you please check my PR?
> 
>  пт, 

Re: [DISCUSSION] Ignite.C++ and CMake

[Petr Ivanov]

For the sake of discretion, I'd purpose to remove old suites from Run All and 
archive or pause them for some time before removal.


> On 23 Jun 2020, at 13:26, Nikolay Izhikov  wrote:
> 
>> So, folks, is it ok to remove old suites from build chain
> 
> +1 from me.
> 
> 
>> 23 июня 2020 г., в 13:15, Ivan Daschinsky  написал(а):
>> 
>> Well, new suites added to RunAll and all seems to be ok.
>> 
>> I think it is time to remove old suites.
>> WDYT?
>> 
>> Also, I created patch with removal of autotools, but old suites should be
>> removed first.
>> 
>> So, folks, is it ok to remove old suites from build chain?
>> 
>> вт, 23 июн. 2020 г. в 10:36, Ivan Daschinsky :
>> 
>>> Ok, I changed agents requirements to builds and add them to runAll
>>> 
>>> пн, 22 июн. 2020 г. в 22:39, Petr Ivanov :
>>> 
 Cmake is installed on all agents (except 10 which is currently down and
 will be updated later).
 
 
> On 22 Jun 2020, at 21:03, Ivan Daschinsky  wrote:
> 
> Well, patch is merged. Thank a lot to Igor Sapego for review.
> 
> Peter, well, cmake now can be installed on all agent.
> 
> I think it's time to add cmake suites to runAll and exclude old suites
 from
> it.
> 
> Patch with removing autotools I Will submit in few days.
> 
> пн, 22 июн. 2020 г., 20:25 Ivan Daschinsky :
> 
>> Hi folks!
>> 
>> Good news -- I successfully created 2 CMake suites [1] [2] and they
 works
>> as a charm.
>> Many thanks to Ilya Kasnacheev for giving me permissions and to Peter
>> Ivanov for installing cmake and giving a whole agent for testing.
>> 
>> [1] --
>> 
 https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinuxClang_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
>> [2] --
>> 
 https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinux_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
>> 
>> пн, 22 июн. 2020 г. в 12:03, Ilya Kasnacheev <
 ilya.kasnach...@gmail.com>:
>> 
>>> Hello!
>>> 
>>> I think you should contact Peter Ivanov if you want anything to be
>>> installed on agents.
>>> 
>>> Regards,
>>> --
>>> Ilya Kasnacheev
>>> 
>>> 
>>> пн, 22 июн. 2020 г. в 12:00, Ivan Daschinsky :
>>> 
 Actually, I'm going to create 2 new suites based on existing ones:
 1. Platform C++ CMake (Linux)
 2. Platform C++ CMake (Linux Clang)
 
 Ilya, thank you very much. But, despite the fact, that I have
>>> permissions,
 it seems that it's impossible to install something (namely, CMake) on
 agents.
 How can I do this obviously essential task?
 
 пн, 22 июн. 2020 г. в 11:30, Ilya Kasnacheev <
 ilya.kasnach...@gmail.com
 :
 
> Hello!
> 
> I have assigned roles on TC, you can now work on these builds.
> 
> Please describe your changes on development list so that people
 understand
> what is going on.
> 
> Regards,
> --
> Ilya Kasnacheev
> 
> 
> вс, 21 июн. 2020 г. в 17:35, Ivan Daschinsky :
> 
>> Hi folks.
>> 
>> Patch is rigorously tested and with Igor Sapego help it is possible
>>> to
>> build with cmake Ignite.C++  even on windows.
>> But, it's required to make some TC suites and tune them, in order
 to
> patch
>> be merged.
>> Unfortunately, I am not a commiter and I doesn't have rights to
>>> create
>> suites. Also, AFAIK, Igor currently is quite busy and doesn't have
>>> much
>> time to do this task by himself.
>> So I need some help from community. Is it possible to grant me some
> rights
>> to TC agents?
>> 
>> ср, 3 июн. 2020 г. в 18:03, Nikolay Izhikov :
>> 
>>> Hello.
>>> 
>>> I will do review of this changes.
>>> 
 1 июня 2020 г., в 13:21, Ivan Daschinsky 
>>> написал(а):
 
 Igor, could you please check my PR?
 
 пт, 29 мая 2020 г. в 15:28, Ivan Daschinsky <
>>> ivanda...@gmail.com>:
 
> Thanks you all. Run patch (I've changed some code also) on TC
>>> --
 all
>> CPP
> suites are green (GCC, CLang, Win64)
> 
> пт, 29 мая 2020 г. в 15:02, Zhenya Stanilovsky
>>> > :
> 
>> 
>> 
>> Ivan besides documentation [1]
>> -s no —  no works
>> -- catch_system_errors =no — works properly well, tests are
 passed.
>> 
>> boost 1.65
>> 
>> [1]
>> 
>>> 
>> 

Re: [DISCUSSION] Ignite.C++ and CMake

[Nikolay Izhikov]

> So, folks, is it ok to remove old suites from build chain

+1 from me.


> 23 июня 2020 г., в 13:15, Ivan Daschinsky  написал(а):
> 
> Well, new suites added to RunAll and all seems to be ok.
> 
> I think it is time to remove old suites.
> WDYT?
> 
> Also, I created patch with removal of autotools, but old suites should be
> removed first.
> 
> So, folks, is it ok to remove old suites from build chain?
> 
> вт, 23 июн. 2020 г. в 10:36, Ivan Daschinsky :
> 
>> Ok, I changed agents requirements to builds and add them to runAll
>> 
>> пн, 22 июн. 2020 г. в 22:39, Petr Ivanov :
>> 
>>> Cmake is installed on all agents (except 10 which is currently down and
>>> will be updated later).
>>> 
>>> 
 On 22 Jun 2020, at 21:03, Ivan Daschinsky  wrote:
 
 Well, patch is merged. Thank a lot to Igor Sapego for review.
 
 Peter, well, cmake now can be installed on all agent.
 
 I think it's time to add cmake suites to runAll and exclude old suites
>>> from
 it.
 
 Patch with removing autotools I Will submit in few days.
 
 пн, 22 июн. 2020 г., 20:25 Ivan Daschinsky :
 
> Hi folks!
> 
> Good news -- I successfully created 2 CMake suites [1] [2] and they
>>> works
> as a charm.
> Many thanks to Ilya Kasnacheev for giving me permissions and to Peter
> Ivanov for installing cmake and giving a whole agent for testing.
> 
> [1] --
> 
>>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinuxClang_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
> [2] --
> 
>>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinux_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
> 
> пн, 22 июн. 2020 г. в 12:03, Ilya Kasnacheev <
>>> ilya.kasnach...@gmail.com>:
> 
>> Hello!
>> 
>> I think you should contact Peter Ivanov if you want anything to be
>> installed on agents.
>> 
>> Regards,
>> --
>> Ilya Kasnacheev
>> 
>> 
>> пн, 22 июн. 2020 г. в 12:00, Ivan Daschinsky :
>> 
>>> Actually, I'm going to create 2 new suites based on existing ones:
>>> 1. Platform C++ CMake (Linux)
>>> 2. Platform C++ CMake (Linux Clang)
>>> 
>>> Ilya, thank you very much. But, despite the fact, that I have
>> permissions,
>>> it seems that it's impossible to install something (namely, CMake) on
>>> agents.
>>> How can I do this obviously essential task?
>>> 
>>> пн, 22 июн. 2020 г. в 11:30, Ilya Kasnacheev <
>>> ilya.kasnach...@gmail.com
>>> :
>>> 
 Hello!
 
 I have assigned roles on TC, you can now work on these builds.
 
 Please describe your changes on development list so that people
>>> understand
 what is going on.
 
 Regards,
 --
 Ilya Kasnacheev
 
 
 вс, 21 июн. 2020 г. в 17:35, Ivan Daschinsky :
 
> Hi folks.
> 
> Patch is rigorously tested and with Igor Sapego help it is possible
>> to
> build with cmake Ignite.C++  even on windows.
> But, it's required to make some TC suites and tune them, in order
>>> to
 patch
> be merged.
> Unfortunately, I am not a commiter and I doesn't have rights to
>> create
> suites. Also, AFAIK, Igor currently is quite busy and doesn't have
>> much
> time to do this task by himself.
> So I need some help from community. Is it possible to grant me some
 rights
> to TC agents?
> 
> ср, 3 июн. 2020 г. в 18:03, Nikolay Izhikov :
> 
>> Hello.
>> 
>> I will do review of this changes.
>> 
>>> 1 июня 2020 г., в 13:21, Ivan Daschinsky 
>> написал(а):
>>> 
>>> Igor, could you please check my PR?
>>> 
>>> пт, 29 мая 2020 г. в 15:28, Ivan Daschinsky <
>> ivanda...@gmail.com>:
>>> 
 Thanks you all. Run patch (I've changed some code also) on TC
>> --
>>> all
> CPP
 suites are green (GCC, CLang, Win64)
 
 пт, 29 мая 2020 г. в 15:02, Zhenya Stanilovsky
>>  :
 
> 
> 
> Ivan besides documentation [1]
> -s no —  no works
> -- catch_system_errors =no — works properly well, tests are
>>> passed.
> 
> boost 1.65
> 
> [1]
> 
>> 
> 
 
>>> 
>> 
>>> https://www.boost.org/doc/libs/1_65_0/libs/test/doc/html/boost_test/utf_reference/rt_param_reference/catch_system.html
> 
>> Hello!
>> 
>> I didn't check tests since I don't develop AI C++, merely
>> use it
 as
>> user.
>> That's where we 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

Well, new suites added to RunAll and all seems to be ok.

I think it is time to remove old suites.
WDYT?

Also, I created patch with removal of autotools, but old suites should be
removed first.

So, folks, is it ok to remove old suites from build chain?

вт, 23 июн. 2020 г. в 10:36, Ivan Daschinsky :

> Ok, I changed agents requirements to builds and add them to runAll
>
> пн, 22 июн. 2020 г. в 22:39, Petr Ivanov :
>
>> Cmake is installed on all agents (except 10 which is currently down and
>> will be updated later).
>>
>>
>> > On 22 Jun 2020, at 21:03, Ivan Daschinsky  wrote:
>> >
>> > Well, patch is merged. Thank a lot to Igor Sapego for review.
>> >
>> > Peter, well, cmake now can be installed on all agent.
>> >
>> > I think it's time to add cmake suites to runAll and exclude old suites
>> from
>> > it.
>> >
>> > Patch with removing autotools I Will submit in few days.
>> >
>> > пн, 22 июн. 2020 г., 20:25 Ivan Daschinsky :
>> >
>> >> Hi folks!
>> >>
>> >> Good news -- I successfully created 2 CMake suites [1] [2] and they
>> works
>> >> as a charm.
>> >> Many thanks to Ilya Kasnacheev for giving me permissions and to Peter
>> >> Ivanov for installing cmake and giving a whole agent for testing.
>> >>
>> >> [1] --
>> >>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinuxClang_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
>> >> [2] --
>> >>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinux_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
>> >>
>> >> пн, 22 июн. 2020 г. в 12:03, Ilya Kasnacheev <
>> ilya.kasnach...@gmail.com>:
>> >>
>> >>> Hello!
>> >>>
>> >>> I think you should contact Peter Ivanov if you want anything to be
>> >>> installed on agents.
>> >>>
>> >>> Regards,
>> >>> --
>> >>> Ilya Kasnacheev
>> >>>
>> >>>
>> >>> пн, 22 июн. 2020 г. в 12:00, Ivan Daschinsky :
>> >>>
>>  Actually, I'm going to create 2 new suites based on existing ones:
>>  1. Platform C++ CMake (Linux)
>>  2. Platform C++ CMake (Linux Clang)
>> 
>>  Ilya, thank you very much. But, despite the fact, that I have
>> >>> permissions,
>>  it seems that it's impossible to install something (namely, CMake) on
>>  agents.
>>  How can I do this obviously essential task?
>> 
>>  пн, 22 июн. 2020 г. в 11:30, Ilya Kasnacheev <
>> ilya.kasnach...@gmail.com
>>  :
>> 
>> > Hello!
>> >
>> > I have assigned roles on TC, you can now work on these builds.
>> >
>> > Please describe your changes on development list so that people
>>  understand
>> > what is going on.
>> >
>> > Regards,
>> > --
>> > Ilya Kasnacheev
>> >
>> >
>> > вс, 21 июн. 2020 г. в 17:35, Ivan Daschinsky :
>> >
>> >> Hi folks.
>> >>
>> >> Patch is rigorously tested and with Igor Sapego help it is possible
>> >>> to
>> >> build with cmake Ignite.C++  even on windows.
>> >> But, it's required to make some TC suites and tune them, in order
>> to
>> > patch
>> >> be merged.
>> >> Unfortunately, I am not a commiter and I doesn't have rights to
>> >>> create
>> >> suites. Also, AFAIK, Igor currently is quite busy and doesn't have
>> >>> much
>> >> time to do this task by himself.
>> >> So I need some help from community. Is it possible to grant me some
>> > rights
>> >> to TC agents?
>> >>
>> >> ср, 3 июн. 2020 г. в 18:03, Nikolay Izhikov :
>> >>
>> >>> Hello.
>> >>>
>> >>> I will do review of this changes.
>> >>>
>>  1 июня 2020 г., в 13:21, Ivan Daschinsky 
>> >>> написал(а):
>> 
>>  Igor, could you please check my PR?
>> 
>>  пт, 29 мая 2020 г. в 15:28, Ivan Daschinsky <
>> >>> ivanda...@gmail.com>:
>> 
>> > Thanks you all. Run patch (I've changed some code also) on TC
>> >>> --
>>  all
>> >> CPP
>> > suites are green (GCC, CLang, Win64)
>> >
>> > пт, 29 мая 2020 г. в 15:02, Zhenya Stanilovsky
>> >>> > >> :
>> >
>> >>
>> >>
>> >> Ivan besides documentation [1]
>> >> -s no —  no works
>> >> -- catch_system_errors =no — works properly well, tests are
>>  passed.
>> >>
>> >> boost 1.65
>> >>
>> >> [1]
>> >>
>> >>>
>> >>
>> >
>> 
>> >>>
>> https://www.boost.org/doc/libs/1_65_0/libs/test/doc/html/boost_test/utf_reference/rt_param_reference/catch_system.html
>> >>
>> >>> Hello!
>> >>>
>> >>> I didn't check tests since I don't develop AI C++, merely
>> >>> use it
>> > as
>> >>> user.
>> >>> That's where we should wait for Igor Sapego to check.
>> >>>
>> >>> Regards,
>> >>> --
>> >>> Ilya Kasnacheev
>> >>>
>> >>>
>> >>> пт, 29 мая 2020 г. в 12:20, Ivan Daschinsky <
>>  

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

Ok, I changed agents requirements to builds and add them to runAll

пн, 22 июн. 2020 г. в 22:39, Petr Ivanov :

> Cmake is installed on all agents (except 10 which is currently down and
> will be updated later).
>
>
> > On 22 Jun 2020, at 21:03, Ivan Daschinsky  wrote:
> >
> > Well, patch is merged. Thank a lot to Igor Sapego for review.
> >
> > Peter, well, cmake now can be installed on all agent.
> >
> > I think it's time to add cmake suites to runAll and exclude old suites
> from
> > it.
> >
> > Patch with removing autotools I Will submit in few days.
> >
> > пн, 22 июн. 2020 г., 20:25 Ivan Daschinsky :
> >
> >> Hi folks!
> >>
> >> Good news -- I successfully created 2 CMake suites [1] [2] and they
> works
> >> as a charm.
> >> Many thanks to Ilya Kasnacheev for giving me permissions and to Peter
> >> Ivanov for installing cmake and giving a whole agent for testing.
> >>
> >> [1] --
> >>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinuxClang_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
> >> [2] --
> >>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinux_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
> >>
> >> пн, 22 июн. 2020 г. в 12:03, Ilya Kasnacheev  >:
> >>
> >>> Hello!
> >>>
> >>> I think you should contact Peter Ivanov if you want anything to be
> >>> installed on agents.
> >>>
> >>> Regards,
> >>> --
> >>> Ilya Kasnacheev
> >>>
> >>>
> >>> пн, 22 июн. 2020 г. в 12:00, Ivan Daschinsky :
> >>>
>  Actually, I'm going to create 2 new suites based on existing ones:
>  1. Platform C++ CMake (Linux)
>  2. Platform C++ CMake (Linux Clang)
> 
>  Ilya, thank you very much. But, despite the fact, that I have
> >>> permissions,
>  it seems that it's impossible to install something (namely, CMake) on
>  agents.
>  How can I do this obviously essential task?
> 
>  пн, 22 июн. 2020 г. в 11:30, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com
>  :
> 
> > Hello!
> >
> > I have assigned roles on TC, you can now work on these builds.
> >
> > Please describe your changes on development list so that people
>  understand
> > what is going on.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > вс, 21 июн. 2020 г. в 17:35, Ivan Daschinsky :
> >
> >> Hi folks.
> >>
> >> Patch is rigorously tested and with Igor Sapego help it is possible
> >>> to
> >> build with cmake Ignite.C++  even on windows.
> >> But, it's required to make some TC suites and tune them, in order to
> > patch
> >> be merged.
> >> Unfortunately, I am not a commiter and I doesn't have rights to
> >>> create
> >> suites. Also, AFAIK, Igor currently is quite busy and doesn't have
> >>> much
> >> time to do this task by himself.
> >> So I need some help from community. Is it possible to grant me some
> > rights
> >> to TC agents?
> >>
> >> ср, 3 июн. 2020 г. в 18:03, Nikolay Izhikov :
> >>
> >>> Hello.
> >>>
> >>> I will do review of this changes.
> >>>
>  1 июня 2020 г., в 13:21, Ivan Daschinsky 
> >>> написал(а):
> 
>  Igor, could you please check my PR?
> 
>  пт, 29 мая 2020 г. в 15:28, Ivan Daschinsky <
> >>> ivanda...@gmail.com>:
> 
> > Thanks you all. Run patch (I've changed some code also) on TC
> >>> --
>  all
> >> CPP
> > suites are green (GCC, CLang, Win64)
> >
> > пт, 29 мая 2020 г. в 15:02, Zhenya Stanilovsky
> >>>  >> :
> >
> >>
> >>
> >> Ivan besides documentation [1]
> >> -s no —  no works
> >> -- catch_system_errors =no — works properly well, tests are
>  passed.
> >>
> >> boost 1.65
> >>
> >> [1]
> >>
> >>>
> >>
> >
> 
> >>>
> https://www.boost.org/doc/libs/1_65_0/libs/test/doc/html/boost_test/utf_reference/rt_param_reference/catch_system.html
> >>
> >>> Hello!
> >>>
> >>> I didn't check tests since I don't develop AI C++, merely
> >>> use it
> > as
> >>> user.
> >>> That's where we should wait for Igor Sapego to check.
> >>>
> >>> Regards,
> >>> --
> >>> Ilya Kasnacheev
> >>>
> >>>
> >>> пт, 29 мая 2020 г. в 12:20, Ivan Daschinsky <
>  ivanda...@gmail.com
> >>> :
> >>>
>  Ilya, thanks a lot! What about tests? I found one flag that
>  must
> > be
>  supplied to boost.tests.
>  This flag should fix JVM crash of C++ suites on Linux.
> 
>  Zhenya Stanilovsky and me have checked, that without this
> >>> flag
> >> tests
> >> failed
>  with SIGSEGV early (boost catch this signal from jvm, but
> >>> it is
> > ok
> >>> for

Re: [DISCUSSION] Ignite.C++ and CMake

[Petr Ivanov]

Cmake is installed on all agents (except 10 which is currently down and will be 
updated later).


> On 22 Jun 2020, at 21:03, Ivan Daschinsky  wrote:
> 
> Well, patch is merged. Thank a lot to Igor Sapego for review.
> 
> Peter, well, cmake now can be installed on all agent.
> 
> I think it's time to add cmake suites to runAll and exclude old suites from
> it.
> 
> Patch with removing autotools I Will submit in few days.
> 
> пн, 22 июн. 2020 г., 20:25 Ivan Daschinsky :
> 
>> Hi folks!
>> 
>> Good news -- I successfully created 2 CMake suites [1] [2] and they works
>> as a charm.
>> Many thanks to Ilya Kasnacheev for giving me permissions and to Peter
>> Ivanov for installing cmake and giving a whole agent for testing.
>> 
>> [1] --
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinuxClang_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
>> [2] --
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinux_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
>> 
>> пн, 22 июн. 2020 г. в 12:03, Ilya Kasnacheev :
>> 
>>> Hello!
>>> 
>>> I think you should contact Peter Ivanov if you want anything to be
>>> installed on agents.
>>> 
>>> Regards,
>>> --
>>> Ilya Kasnacheev
>>> 
>>> 
>>> пн, 22 июн. 2020 г. в 12:00, Ivan Daschinsky :
>>> 
 Actually, I'm going to create 2 new suites based on existing ones:
 1. Platform C++ CMake (Linux)
 2. Platform C++ CMake (Linux Clang)
 
 Ilya, thank you very much. But, despite the fact, that I have
>>> permissions,
 it seems that it's impossible to install something (namely, CMake) on
 agents.
 How can I do this obviously essential task?
 
 пн, 22 июн. 2020 г. в 11:30, Ilya Kasnacheev >>> :
 
> Hello!
> 
> I have assigned roles on TC, you can now work on these builds.
> 
> Please describe your changes on development list so that people
 understand
> what is going on.
> 
> Regards,
> --
> Ilya Kasnacheev
> 
> 
> вс, 21 июн. 2020 г. в 17:35, Ivan Daschinsky :
> 
>> Hi folks.
>> 
>> Patch is rigorously tested and with Igor Sapego help it is possible
>>> to
>> build with cmake Ignite.C++  even on windows.
>> But, it's required to make some TC suites and tune them, in order to
> patch
>> be merged.
>> Unfortunately, I am not a commiter and I doesn't have rights to
>>> create
>> suites. Also, AFAIK, Igor currently is quite busy and doesn't have
>>> much
>> time to do this task by himself.
>> So I need some help from community. Is it possible to grant me some
> rights
>> to TC agents?
>> 
>> ср, 3 июн. 2020 г. в 18:03, Nikolay Izhikov :
>> 
>>> Hello.
>>> 
>>> I will do review of this changes.
>>> 
 1 июня 2020 г., в 13:21, Ivan Daschinsky 
>>> написал(а):
 
 Igor, could you please check my PR?
 
 пт, 29 мая 2020 г. в 15:28, Ivan Daschinsky <
>>> ivanda...@gmail.com>:
 
> Thanks you all. Run patch (I've changed some code also) on TC
>>> --
 all
>> CPP
> suites are green (GCC, CLang, Win64)
> 
> пт, 29 мая 2020 г. в 15:02, Zhenya Stanilovsky
>>> > :
> 
>> 
>> 
>> Ivan besides documentation [1]
>> -s no —  no works
>> -- catch_system_errors =no — works properly well, tests are
 passed.
>> 
>> boost 1.65
>> 
>> [1]
>> 
>>> 
>> 
> 
 
>>> https://www.boost.org/doc/libs/1_65_0/libs/test/doc/html/boost_test/utf_reference/rt_param_reference/catch_system.html
>> 
>>> Hello!
>>> 
>>> I didn't check tests since I don't develop AI C++, merely
>>> use it
> as
>>> user.
>>> That's where we should wait for Igor Sapego to check.
>>> 
>>> Regards,
>>> --
>>> Ilya Kasnacheev
>>> 
>>> 
>>> пт, 29 мая 2020 г. в 12:20, Ivan Daschinsky <
 ivanda...@gmail.com
>>> :
>>> 
 Ilya, thanks a lot! What about tests? I found one flag that
 must
> be
 supplied to boost.tests.
 This flag should fix JVM crash of C++ suites on Linux.
 
 Zhenya Stanilovsky and me have checked, that without this
>>> flag
>> tests
>> failed
 with SIGSEGV early (boost catch this signal from jvm, but
>>> it is
> ok
>>> for
 jvm).
 Flag is -catch_system_errors=no. I added it to CTest runner.
 You
>> can
 invoke it manually and using make test ARGS="-V"
 
 
 
 пт, 29 мая 2020 г. в 11:54, Ilya Kasnacheev <
>> ilya.kasnach...@gmail.com >:
 
> Hello!
> 
> Looks good to me! But we probably also 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

Well, patch is merged. Thank a lot to Igor Sapego for review.

Peter, well, cmake now can be installed on all agent.

I think it's time to add cmake suites to runAll and exclude old suites from
it.

Patch with removing autotools I Will submit in few days.

пн, 22 июн. 2020 г., 20:25 Ivan Daschinsky :

> Hi folks!
>
> Good news -- I successfully created 2 CMake suites [1] [2] and they works
> as a charm.
> Many thanks to Ilya Kasnacheev for giving me permissions and to Peter
> Ivanov for installing cmake and giving a whole agent for testing.
>
> [1] --
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinuxClang_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
> [2] --
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinux_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
>
> пн, 22 июн. 2020 г. в 12:03, Ilya Kasnacheev :
>
>> Hello!
>>
>> I think you should contact Peter Ivanov if you want anything to be
>> installed on agents.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> пн, 22 июн. 2020 г. в 12:00, Ivan Daschinsky :
>>
>> > Actually, I'm going to create 2 new suites based on existing ones:
>> > 1. Platform C++ CMake (Linux)
>> > 2. Platform C++ CMake (Linux Clang)
>> >
>> > Ilya, thank you very much. But, despite the fact, that I have
>> permissions,
>> > it seems that it's impossible to install something (namely, CMake) on
>> > agents.
>> > How can I do this obviously essential task?
>> >
>> > пн, 22 июн. 2020 г. в 11:30, Ilya Kasnacheev > >:
>> >
>> > > Hello!
>> > >
>> > > I have assigned roles on TC, you can now work on these builds.
>> > >
>> > > Please describe your changes on development list so that people
>> > understand
>> > > what is going on.
>> > >
>> > > Regards,
>> > > --
>> > > Ilya Kasnacheev
>> > >
>> > >
>> > > вс, 21 июн. 2020 г. в 17:35, Ivan Daschinsky :
>> > >
>> > > > Hi folks.
>> > > >
>> > > > Patch is rigorously tested and with Igor Sapego help it is possible
>> to
>> > > > build with cmake Ignite.C++  even on windows.
>> > > > But, it's required to make some TC suites and tune them, in order to
>> > > patch
>> > > > be merged.
>> > > > Unfortunately, I am not a commiter and I doesn't have rights to
>> create
>> > > > suites. Also, AFAIK, Igor currently is quite busy and doesn't have
>> much
>> > > > time to do this task by himself.
>> > > > So I need some help from community. Is it possible to grant me some
>> > > rights
>> > > > to TC agents?
>> > > >
>> > > > ср, 3 июн. 2020 г. в 18:03, Nikolay Izhikov :
>> > > >
>> > > > > Hello.
>> > > > >
>> > > > > I will do review of this changes.
>> > > > >
>> > > > > > 1 июня 2020 г., в 13:21, Ivan Daschinsky 
>> > > > > написал(а):
>> > > > > >
>> > > > > > Igor, could you please check my PR?
>> > > > > >
>> > > > > > пт, 29 мая 2020 г. в 15:28, Ivan Daschinsky <
>> ivanda...@gmail.com>:
>> > > > > >
>> > > > > >> Thanks you all. Run patch (I've changed some code also) on TC
>> --
>> > all
>> > > > CPP
>> > > > > >> suites are green (GCC, CLang, Win64)
>> > > > > >>
>> > > > > >> пт, 29 мая 2020 г. в 15:02, Zhenya Stanilovsky
>> > > > > > > > > > >>> :
>> > > > > >>
>> > > > > >>>
>> > > > > >>>
>> > > > > >>> Ivan besides documentation [1]
>> > > > > >>> -s no —  no works
>> > > > > >>> -- catch_system_errors =no — works properly well, tests are
>> > passed.
>> > > > > >>>
>> > > > > >>> boost 1.65
>> > > > > >>>
>> > > > > >>> [1]
>> > > > > >>>
>> > > > >
>> > > >
>> > >
>> >
>> https://www.boost.org/doc/libs/1_65_0/libs/test/doc/html/boost_test/utf_reference/rt_param_reference/catch_system.html
>> > > > > >>>
>> > > > >  Hello!
>> > > > > 
>> > > > >  I didn't check tests since I don't develop AI C++, merely
>> use it
>> > > as
>> > > > > user.
>> > > > >  That's where we should wait for Igor Sapego to check.
>> > > > > 
>> > > > >  Regards,
>> > > > >  --
>> > > > >  Ilya Kasnacheev
>> > > > > 
>> > > > > 
>> > > > >  пт, 29 мая 2020 г. в 12:20, Ivan Daschinsky <
>> > ivanda...@gmail.com
>> > > > >:
>> > > > > 
>> > > > > > Ilya, thanks a lot! What about tests? I found one flag that
>> > must
>> > > be
>> > > > > > supplied to boost.tests.
>> > > > > > This flag should fix JVM crash of C++ suites on Linux.
>> > > > > >
>> > > > > > Zhenya Stanilovsky and me have checked, that without this
>> flag
>> > > > tests
>> > > > > >>> failed
>> > > > > > with SIGSEGV early (boost catch this signal from jvm, but
>> it is
>> > > ok
>> > > > > for
>> > > > > > jvm).
>> > > > > > Flag is -catch_system_errors=no. I added it to CTest runner.
>> > You
>> > > > can
>> > > > > > invoke it manually and using make test ARGS="-V"
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > пт, 29 мая 2020 г. в 11:54, Ilya Kasnacheev <
>> > > > > >>> ilya.kasnach...@gmail.com >:
>> > > > > >
>> > > > > >> Hello!
>> > > > > >>
>> > > > > >> 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

Hi folks!

Good news -- I successfully created 2 CMake suites [1] [2] and they works
as a charm.
Many thanks to Ilya Kasnacheev for giving me permissions and to Peter
Ivanov for installing cmake and giving a whole agent for testing.

[1] --
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinuxClang_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv
[2] --
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformCPPCMakeLinux_IgniteTests24Java8=pull%2F7854%2Fhead=buildTypeStatusDiv

пн, 22 июн. 2020 г. в 12:03, Ilya Kasnacheev :

> Hello!
>
> I think you should contact Peter Ivanov if you want anything to be
> installed on agents.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 22 июн. 2020 г. в 12:00, Ivan Daschinsky :
>
> > Actually, I'm going to create 2 new suites based on existing ones:
> > 1. Platform C++ CMake (Linux)
> > 2. Platform C++ CMake (Linux Clang)
> >
> > Ilya, thank you very much. But, despite the fact, that I have
> permissions,
> > it seems that it's impossible to install something (namely, CMake) on
> > agents.
> > How can I do this obviously essential task?
> >
> > пн, 22 июн. 2020 г. в 11:30, Ilya Kasnacheev  >:
> >
> > > Hello!
> > >
> > > I have assigned roles on TC, you can now work on these builds.
> > >
> > > Please describe your changes on development list so that people
> > understand
> > > what is going on.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > вс, 21 июн. 2020 г. в 17:35, Ivan Daschinsky :
> > >
> > > > Hi folks.
> > > >
> > > > Patch is rigorously tested and with Igor Sapego help it is possible
> to
> > > > build with cmake Ignite.C++  even on windows.
> > > > But, it's required to make some TC suites and tune them, in order to
> > > patch
> > > > be merged.
> > > > Unfortunately, I am not a commiter and I doesn't have rights to
> create
> > > > suites. Also, AFAIK, Igor currently is quite busy and doesn't have
> much
> > > > time to do this task by himself.
> > > > So I need some help from community. Is it possible to grant me some
> > > rights
> > > > to TC agents?
> > > >
> > > > ср, 3 июн. 2020 г. в 18:03, Nikolay Izhikov :
> > > >
> > > > > Hello.
> > > > >
> > > > > I will do review of this changes.
> > > > >
> > > > > > 1 июня 2020 г., в 13:21, Ivan Daschinsky 
> > > > > написал(а):
> > > > > >
> > > > > > Igor, could you please check my PR?
> > > > > >
> > > > > > пт, 29 мая 2020 г. в 15:28, Ivan Daschinsky  >:
> > > > > >
> > > > > >> Thanks you all. Run patch (I've changed some code also) on TC --
> > all
> > > > CPP
> > > > > >> suites are green (GCC, CLang, Win64)
> > > > > >>
> > > > > >> пт, 29 мая 2020 г. в 15:02, Zhenya Stanilovsky
> > > > >  > > > > >>> :
> > > > > >>
> > > > > >>>
> > > > > >>>
> > > > > >>> Ivan besides documentation [1]
> > > > > >>> -s no —  no works
> > > > > >>> -- catch_system_errors =no — works properly well, tests are
> > passed.
> > > > > >>>
> > > > > >>> boost 1.65
> > > > > >>>
> > > > > >>> [1]
> > > > > >>>
> > > > >
> > > >
> > >
> >
> https://www.boost.org/doc/libs/1_65_0/libs/test/doc/html/boost_test/utf_reference/rt_param_reference/catch_system.html
> > > > > >>>
> > > > >  Hello!
> > > > > 
> > > > >  I didn't check tests since I don't develop AI C++, merely use
> it
> > > as
> > > > > user.
> > > > >  That's where we should wait for Igor Sapego to check.
> > > > > 
> > > > >  Regards,
> > > > >  --
> > > > >  Ilya Kasnacheev
> > > > > 
> > > > > 
> > > > >  пт, 29 мая 2020 г. в 12:20, Ivan Daschinsky <
> > ivanda...@gmail.com
> > > > >:
> > > > > 
> > > > > > Ilya, thanks a lot! What about tests? I found one flag that
> > must
> > > be
> > > > > > supplied to boost.tests.
> > > > > > This flag should fix JVM crash of C++ suites on Linux.
> > > > > >
> > > > > > Zhenya Stanilovsky and me have checked, that without this
> flag
> > > > tests
> > > > > >>> failed
> > > > > > with SIGSEGV early (boost catch this signal from jvm, but it
> is
> > > ok
> > > > > for
> > > > > > jvm).
> > > > > > Flag is -catch_system_errors=no. I added it to CTest runner.
> > You
> > > > can
> > > > > > invoke it manually and using make test ARGS="-V"
> > > > > >
> > > > > >
> > > > > >
> > > > > > пт, 29 мая 2020 г. в 11:54, Ilya Kasnacheev <
> > > > > >>> ilya.kasnach...@gmail.com >:
> > > > > >
> > > > > >> Hello!
> > > > > >>
> > > > > >> Looks good to me! But we probably also ask Igor to take a
> > look.
> > > > > >>
> > > > > >> Compiled debug and release, without and with odbc, checked
> > > running
> > > > > >>> thick
> > > > > >> node and ODBC connection on Linux.
> > > > > >>
> > > > > >> Regards,
> > > > > >> --
> > > > > >> Ilya Kasnacheev
> > > > > >>
> > > > > >>
> > > > > >> чт, 28 мая 2020 г. в 17:31, Ivan Daschinsky <
> > > ivanda...@gmail.com
> > > > > >:
> > > > > >>

Re: [DISCUSSION] Ignite.C++ and CMake

[Ilya Kasnacheev]

Hello!

I think you should contact Peter Ivanov if you want anything to be
installed on agents.

Regards,
-- 
Ilya Kasnacheev


пн, 22 июн. 2020 г. в 12:00, Ivan Daschinsky :

> Actually, I'm going to create 2 new suites based on existing ones:
> 1. Platform C++ CMake (Linux)
> 2. Platform C++ CMake (Linux Clang)
>
> Ilya, thank you very much. But, despite the fact, that I have permissions,
> it seems that it's impossible to install something (namely, CMake) on
> agents.
> How can I do this obviously essential task?
>
> пн, 22 июн. 2020 г. в 11:30, Ilya Kasnacheev :
>
> > Hello!
> >
> > I have assigned roles on TC, you can now work on these builds.
> >
> > Please describe your changes on development list so that people
> understand
> > what is going on.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > вс, 21 июн. 2020 г. в 17:35, Ivan Daschinsky :
> >
> > > Hi folks.
> > >
> > > Patch is rigorously tested and with Igor Sapego help it is possible to
> > > build with cmake Ignite.C++  even on windows.
> > > But, it's required to make some TC suites and tune them, in order to
> > patch
> > > be merged.
> > > Unfortunately, I am not a commiter and I doesn't have rights to create
> > > suites. Also, AFAIK, Igor currently is quite busy and doesn't have much
> > > time to do this task by himself.
> > > So I need some help from community. Is it possible to grant me some
> > rights
> > > to TC agents?
> > >
> > > ср, 3 июн. 2020 г. в 18:03, Nikolay Izhikov :
> > >
> > > > Hello.
> > > >
> > > > I will do review of this changes.
> > > >
> > > > > 1 июня 2020 г., в 13:21, Ivan Daschinsky 
> > > > написал(а):
> > > > >
> > > > > Igor, could you please check my PR?
> > > > >
> > > > > пт, 29 мая 2020 г. в 15:28, Ivan Daschinsky :
> > > > >
> > > > >> Thanks you all. Run patch (I've changed some code also) on TC --
> all
> > > CPP
> > > > >> suites are green (GCC, CLang, Win64)
> > > > >>
> > > > >> пт, 29 мая 2020 г. в 15:02, Zhenya Stanilovsky
> > > >  > > > >>> :
> > > > >>
> > > > >>>
> > > > >>>
> > > > >>> Ivan besides documentation [1]
> > > > >>> -s no —  no works
> > > > >>> -- catch_system_errors =no — works properly well, tests are
> passed.
> > > > >>>
> > > > >>> boost 1.65
> > > > >>>
> > > > >>> [1]
> > > > >>>
> > > >
> > >
> >
> https://www.boost.org/doc/libs/1_65_0/libs/test/doc/html/boost_test/utf_reference/rt_param_reference/catch_system.html
> > > > >>>
> > > >  Hello!
> > > > 
> > > >  I didn't check tests since I don't develop AI C++, merely use it
> > as
> > > > user.
> > > >  That's where we should wait for Igor Sapego to check.
> > > > 
> > > >  Regards,
> > > >  --
> > > >  Ilya Kasnacheev
> > > > 
> > > > 
> > > >  пт, 29 мая 2020 г. в 12:20, Ivan Daschinsky <
> ivanda...@gmail.com
> > > >:
> > > > 
> > > > > Ilya, thanks a lot! What about tests? I found one flag that
> must
> > be
> > > > > supplied to boost.tests.
> > > > > This flag should fix JVM crash of C++ suites on Linux.
> > > > >
> > > > > Zhenya Stanilovsky and me have checked, that without this flag
> > > tests
> > > > >>> failed
> > > > > with SIGSEGV early (boost catch this signal from jvm, but it is
> > ok
> > > > for
> > > > > jvm).
> > > > > Flag is -catch_system_errors=no. I added it to CTest runner.
> You
> > > can
> > > > > invoke it manually and using make test ARGS="-V"
> > > > >
> > > > >
> > > > >
> > > > > пт, 29 мая 2020 г. в 11:54, Ilya Kasnacheev <
> > > > >>> ilya.kasnach...@gmail.com >:
> > > > >
> > > > >> Hello!
> > > > >>
> > > > >> Looks good to me! But we probably also ask Igor to take a
> look.
> > > > >>
> > > > >> Compiled debug and release, without and with odbc, checked
> > running
> > > > >>> thick
> > > > >> node and ODBC connection on Linux.
> > > > >>
> > > > >> Regards,
> > > > >> --
> > > > >> Ilya Kasnacheev
> > > > >>
> > > > >>
> > > > >> чт, 28 мая 2020 г. в 17:31, Ivan Daschinsky <
> > ivanda...@gmail.com
> > > > >:
> > > > >>
> > > > >>> Ok, PR is ready
> > > > >>> https://issues.apache.org/jira/browse/IGNITE-13078
> > > > >>>
> > > > >>> Build tested on Mac OS X 10.15 and Ubuntu 20.04 with CMake
> > 3.17.2
> > > > >>> and
> > > > >> 3.6.1
> > > > >>> Unfortunately, I was not able to test on Windows, but
> > principally
> > > > >>> it
> > > > >> should
> > > > >>> works, but minor issues are probable.
> > > > >>>
> > > > >>> Instruction is attached in PR.
> > > > >>> Any use reports are welcomed!
> > > > >>>
> > > > >>> вт, 26 мая 2020 г. в 18:51, Ivan Daschinsky <
> > > ivanda...@gmail.com
> > > >  :
> > > > >>>
> > > >  Stephen, looks great! I do mostly the same things in C++
> code.
> > > > >>> Thank
> > > > >> you!
> > > > 
> > > >  вт, 26 мая 2020 г. в 18:33, Stephen Darlington <
> > > >  stephen.darling...@gridgain.com >:
> > 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

Actually, I'm going to create 2 new suites based on existing ones:
1. Platform C++ CMake (Linux)
2. Platform C++ CMake (Linux Clang)

Ilya, thank you very much. But, despite the fact, that I have permissions,
it seems that it's impossible to install something (namely, CMake) on
agents.
How can I do this obviously essential task?

пн, 22 июн. 2020 г. в 11:30, Ilya Kasnacheev :

> Hello!
>
> I have assigned roles on TC, you can now work on these builds.
>
> Please describe your changes on development list so that people understand
> what is going on.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вс, 21 июн. 2020 г. в 17:35, Ivan Daschinsky :
>
> > Hi folks.
> >
> > Patch is rigorously tested and with Igor Sapego help it is possible to
> > build with cmake Ignite.C++  even on windows.
> > But, it's required to make some TC suites and tune them, in order to
> patch
> > be merged.
> > Unfortunately, I am not a commiter and I doesn't have rights to create
> > suites. Also, AFAIK, Igor currently is quite busy and doesn't have much
> > time to do this task by himself.
> > So I need some help from community. Is it possible to grant me some
> rights
> > to TC agents?
> >
> > ср, 3 июн. 2020 г. в 18:03, Nikolay Izhikov :
> >
> > > Hello.
> > >
> > > I will do review of this changes.
> > >
> > > > 1 июня 2020 г., в 13:21, Ivan Daschinsky 
> > > написал(а):
> > > >
> > > > Igor, could you please check my PR?
> > > >
> > > > пт, 29 мая 2020 г. в 15:28, Ivan Daschinsky :
> > > >
> > > >> Thanks you all. Run patch (I've changed some code also) on TC -- all
> > CPP
> > > >> suites are green (GCC, CLang, Win64)
> > > >>
> > > >> пт, 29 мая 2020 г. в 15:02, Zhenya Stanilovsky
> > >  > > >>> :
> > > >>
> > > >>>
> > > >>>
> > > >>> Ivan besides documentation [1]
> > > >>> -s no —  no works
> > > >>> -- catch_system_errors =no — works properly well, tests are passed.
> > > >>>
> > > >>> boost 1.65
> > > >>>
> > > >>> [1]
> > > >>>
> > >
> >
> https://www.boost.org/doc/libs/1_65_0/libs/test/doc/html/boost_test/utf_reference/rt_param_reference/catch_system.html
> > > >>>
> > >  Hello!
> > > 
> > >  I didn't check tests since I don't develop AI C++, merely use it
> as
> > > user.
> > >  That's where we should wait for Igor Sapego to check.
> > > 
> > >  Regards,
> > >  --
> > >  Ilya Kasnacheev
> > > 
> > > 
> > >  пт, 29 мая 2020 г. в 12:20, Ivan Daschinsky < ivanda...@gmail.com
> > >:
> > > 
> > > > Ilya, thanks a lot! What about tests? I found one flag that must
> be
> > > > supplied to boost.tests.
> > > > This flag should fix JVM crash of C++ suites on Linux.
> > > >
> > > > Zhenya Stanilovsky and me have checked, that without this flag
> > tests
> > > >>> failed
> > > > with SIGSEGV early (boost catch this signal from jvm, but it is
> ok
> > > for
> > > > jvm).
> > > > Flag is -catch_system_errors=no. I added it to CTest runner. You
> > can
> > > > invoke it manually and using make test ARGS="-V"
> > > >
> > > >
> > > >
> > > > пт, 29 мая 2020 г. в 11:54, Ilya Kasnacheev <
> > > >>> ilya.kasnach...@gmail.com >:
> > > >
> > > >> Hello!
> > > >>
> > > >> Looks good to me! But we probably also ask Igor to take a look.
> > > >>
> > > >> Compiled debug and release, without and with odbc, checked
> running
> > > >>> thick
> > > >> node and ODBC connection on Linux.
> > > >>
> > > >> Regards,
> > > >> --
> > > >> Ilya Kasnacheev
> > > >>
> > > >>
> > > >> чт, 28 мая 2020 г. в 17:31, Ivan Daschinsky <
> ivanda...@gmail.com
> > > >:
> > > >>
> > > >>> Ok, PR is ready
> > > >>> https://issues.apache.org/jira/browse/IGNITE-13078
> > > >>>
> > > >>> Build tested on Mac OS X 10.15 and Ubuntu 20.04 with CMake
> 3.17.2
> > > >>> and
> > > >> 3.6.1
> > > >>> Unfortunately, I was not able to test on Windows, but
> principally
> > > >>> it
> > > >> should
> > > >>> works, but minor issues are probable.
> > > >>>
> > > >>> Instruction is attached in PR.
> > > >>> Any use reports are welcomed!
> > > >>>
> > > >>> вт, 26 мая 2020 г. в 18:51, Ivan Daschinsky <
> > ivanda...@gmail.com
> > >  :
> > > >>>
> > >  Stephen, looks great! I do mostly the same things in C++ code.
> > > >>> Thank
> > > >> you!
> > > 
> > >  вт, 26 мая 2020 г. в 18:33, Stephen Darlington <
> > >  stephen.darling...@gridgain.com >:
> > > 
> > > > Not sure if it’ll help, but I made some changes to get it
> > > >>> working
> > > > on a
> > > > Mac with the current built system. There may be some code
> worth
> > > >> taking.
> > > >
> > > > https://github.com/apache/ignite/pull/4872 <
> > > > https://github.com/apache/ignite/pull/4872 >
> > > >
> > > > Regards,
> > > > Stephen
> > > >
> > > >> On 26 May 2020, at 16:02, Ivan 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ilya Kasnacheev]

Hello!

I have assigned roles on TC, you can now work on these builds.

Please describe your changes on development list so that people understand
what is going on.

Regards,
-- 
Ilya Kasnacheev


вс, 21 июн. 2020 г. в 17:35, Ivan Daschinsky :

> Hi folks.
>
> Patch is rigorously tested and with Igor Sapego help it is possible to
> build with cmake Ignite.C++  even on windows.
> But, it's required to make some TC suites and tune them, in order to patch
> be merged.
> Unfortunately, I am not a commiter and I doesn't have rights to create
> suites. Also, AFAIK, Igor currently is quite busy and doesn't have much
> time to do this task by himself.
> So I need some help from community. Is it possible to grant me some rights
> to TC agents?
>
> ср, 3 июн. 2020 г. в 18:03, Nikolay Izhikov :
>
> > Hello.
> >
> > I will do review of this changes.
> >
> > > 1 июня 2020 г., в 13:21, Ivan Daschinsky 
> > написал(а):
> > >
> > > Igor, could you please check my PR?
> > >
> > > пт, 29 мая 2020 г. в 15:28, Ivan Daschinsky :
> > >
> > >> Thanks you all. Run patch (I've changed some code also) on TC -- all
> CPP
> > >> suites are green (GCC, CLang, Win64)
> > >>
> > >> пт, 29 мая 2020 г. в 15:02, Zhenya Stanilovsky
> >  > >>> :
> > >>
> > >>>
> > >>>
> > >>> Ivan besides documentation [1]
> > >>> -s no —  no works
> > >>> -- catch_system_errors =no — works properly well, tests are passed.
> > >>>
> > >>> boost 1.65
> > >>>
> > >>> [1]
> > >>>
> >
> https://www.boost.org/doc/libs/1_65_0/libs/test/doc/html/boost_test/utf_reference/rt_param_reference/catch_system.html
> > >>>
> >  Hello!
> > 
> >  I didn't check tests since I don't develop AI C++, merely use it as
> > user.
> >  That's where we should wait for Igor Sapego to check.
> > 
> >  Regards,
> >  --
> >  Ilya Kasnacheev
> > 
> > 
> >  пт, 29 мая 2020 г. в 12:20, Ivan Daschinsky < ivanda...@gmail.com
> >:
> > 
> > > Ilya, thanks a lot! What about tests? I found one flag that must be
> > > supplied to boost.tests.
> > > This flag should fix JVM crash of C++ suites on Linux.
> > >
> > > Zhenya Stanilovsky and me have checked, that without this flag
> tests
> > >>> failed
> > > with SIGSEGV early (boost catch this signal from jvm, but it is ok
> > for
> > > jvm).
> > > Flag is -catch_system_errors=no. I added it to CTest runner. You
> can
> > > invoke it manually and using make test ARGS="-V"
> > >
> > >
> > >
> > > пт, 29 мая 2020 г. в 11:54, Ilya Kasnacheev <
> > >>> ilya.kasnach...@gmail.com >:
> > >
> > >> Hello!
> > >>
> > >> Looks good to me! But we probably also ask Igor to take a look.
> > >>
> > >> Compiled debug and release, without and with odbc, checked running
> > >>> thick
> > >> node and ODBC connection on Linux.
> > >>
> > >> Regards,
> > >> --
> > >> Ilya Kasnacheev
> > >>
> > >>
> > >> чт, 28 мая 2020 г. в 17:31, Ivan Daschinsky < ivanda...@gmail.com
> > >:
> > >>
> > >>> Ok, PR is ready
> > >>> https://issues.apache.org/jira/browse/IGNITE-13078
> > >>>
> > >>> Build tested on Mac OS X 10.15 and Ubuntu 20.04 with CMake 3.17.2
> > >>> and
> > >> 3.6.1
> > >>> Unfortunately, I was not able to test on Windows, but principally
> > >>> it
> > >> should
> > >>> works, but minor issues are probable.
> > >>>
> > >>> Instruction is attached in PR.
> > >>> Any use reports are welcomed!
> > >>>
> > >>> вт, 26 мая 2020 г. в 18:51, Ivan Daschinsky <
> ivanda...@gmail.com
> >  :
> > >>>
> >  Stephen, looks great! I do mostly the same things in C++ code.
> > >>> Thank
> > >> you!
> > 
> >  вт, 26 мая 2020 г. в 18:33, Stephen Darlington <
> >  stephen.darling...@gridgain.com >:
> > 
> > > Not sure if it’ll help, but I made some changes to get it
> > >>> working
> > > on a
> > > Mac with the current built system. There may be some code worth
> > >> taking.
> > >
> > > https://github.com/apache/ignite/pull/4872 <
> > > https://github.com/apache/ignite/pull/4872 >
> > >
> > > Regards,
> > > Stephen
> > >
> > >> On 26 May 2020, at 16:02, Ivan Daschinsky <
> > >>> ivanda...@gmail.com >
> > >>> wrote:
> > >>
> > >> I appreciate any help, thank you, Ilya.
> > >>
> > >> Currently I have a small PR without ticket (link in first
> > > post),but
> > >> I
> > >> decided not to file a jira issue before discussion.
> > >> Now I see, that this feature are of great interest to
> > >>> community.
> > > So
> > >> I
> > > file
> > >> a ticket, test myself on my home laptop (ubuntu 20.04)
> > >> and add detailed instructions to DEVNOTES.txt in a few days.
> > >>
> > >> I would be happy if my someone can follow the instruction and
> > 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

Hi folks.

Patch is rigorously tested and with Igor Sapego help it is possible to
build with cmake Ignite.C++  even on windows.
But, it's required to make some TC suites and tune them, in order to patch
be merged.
Unfortunately, I am not a commiter and I doesn't have rights to create
suites. Also, AFAIK, Igor currently is quite busy and doesn't have much
time to do this task by himself.
So I need some help from community. Is it possible to grant me some rights
to TC agents?

ср, 3 июн. 2020 г. в 18:03, Nikolay Izhikov :

> Hello.
>
> I will do review of this changes.
>
> > 1 июня 2020 г., в 13:21, Ivan Daschinsky 
> написал(а):
> >
> > Igor, could you please check my PR?
> >
> > пт, 29 мая 2020 г. в 15:28, Ivan Daschinsky :
> >
> >> Thanks you all. Run patch (I've changed some code also) on TC -- all CPP
> >> suites are green (GCC, CLang, Win64)
> >>
> >> пт, 29 мая 2020 г. в 15:02, Zhenya Stanilovsky
>  >>> :
> >>
> >>>
> >>>
> >>> Ivan besides documentation [1]
> >>> -s no —  no works
> >>> -- catch_system_errors =no — works properly well, tests are passed.
> >>>
> >>> boost 1.65
> >>>
> >>> [1]
> >>>
> https://www.boost.org/doc/libs/1_65_0/libs/test/doc/html/boost_test/utf_reference/rt_param_reference/catch_system.html
> >>>
>  Hello!
> 
>  I didn't check tests since I don't develop AI C++, merely use it as
> user.
>  That's where we should wait for Igor Sapego to check.
> 
>  Regards,
>  --
>  Ilya Kasnacheev
> 
> 
>  пт, 29 мая 2020 г. в 12:20, Ivan Daschinsky < ivanda...@gmail.com >:
> 
> > Ilya, thanks a lot! What about tests? I found one flag that must be
> > supplied to boost.tests.
> > This flag should fix JVM crash of C++ suites on Linux.
> >
> > Zhenya Stanilovsky and me have checked, that without this flag tests
> >>> failed
> > with SIGSEGV early (boost catch this signal from jvm, but it is ok
> for
> > jvm).
> > Flag is -catch_system_errors=no. I added it to CTest runner. You can
> > invoke it manually and using make test ARGS="-V"
> >
> >
> >
> > пт, 29 мая 2020 г. в 11:54, Ilya Kasnacheev <
> >>> ilya.kasnach...@gmail.com >:
> >
> >> Hello!
> >>
> >> Looks good to me! But we probably also ask Igor to take a look.
> >>
> >> Compiled debug and release, without and with odbc, checked running
> >>> thick
> >> node and ODBC connection on Linux.
> >>
> >> Regards,
> >> --
> >> Ilya Kasnacheev
> >>
> >>
> >> чт, 28 мая 2020 г. в 17:31, Ivan Daschinsky < ivanda...@gmail.com
> >:
> >>
> >>> Ok, PR is ready
> >>> https://issues.apache.org/jira/browse/IGNITE-13078
> >>>
> >>> Build tested on Mac OS X 10.15 and Ubuntu 20.04 with CMake 3.17.2
> >>> and
> >> 3.6.1
> >>> Unfortunately, I was not able to test on Windows, but principally
> >>> it
> >> should
> >>> works, but minor issues are probable.
> >>>
> >>> Instruction is attached in PR.
> >>> Any use reports are welcomed!
> >>>
> >>> вт, 26 мая 2020 г. в 18:51, Ivan Daschinsky < ivanda...@gmail.com
>  :
> >>>
>  Stephen, looks great! I do mostly the same things in C++ code.
> >>> Thank
> >> you!
> 
>  вт, 26 мая 2020 г. в 18:33, Stephen Darlington <
>  stephen.darling...@gridgain.com >:
> 
> > Not sure if it’ll help, but I made some changes to get it
> >>> working
> > on a
> > Mac with the current built system. There may be some code worth
> >> taking.
> >
> > https://github.com/apache/ignite/pull/4872 <
> > https://github.com/apache/ignite/pull/4872 >
> >
> > Regards,
> > Stephen
> >
> >> On 26 May 2020, at 16:02, Ivan Daschinsky <
> >>> ivanda...@gmail.com >
> >>> wrote:
> >>
> >> I appreciate any help, thank you, Ilya.
> >>
> >> Currently I have a small PR without ticket (link in first
> > post),but
> >> I
> >> decided not to file a jira issue before discussion.
> >> Now I see, that this feature are of great interest to
> >>> community.
> > So
> >> I
> > file
> >> a ticket, test myself on my home laptop (ubuntu 20.04)
> >> and add detailed instructions to DEVNOTES.txt in a few days.
> >>
> >> I would be happy if my someone can follow the instruction and
> > write
> >> possible issues.
> >>
> >> I will notify about status update in this thread in next few
> >>> days.
> >>
> >> Thank you all very much for support!
> >>
> >>
> >> вт, 26 мая 2020 г. в 17:50, Ilya Kasnacheev <
> >>> ilya.kasnach...@gmail.com
> >> :
> >>
> >>> Hello!
> >>>
> >>> I will assist with checking on Linux if you would contribute
> >>> a
> >> patch.
> >>> Please start with a ticket (or even an IEP 

Re: [DISCUSSION] Ignite.C++ and CMake

[Nikolay Izhikov]

Hello.

I will do review of this changes.

> 1 июня 2020 г., в 13:21, Ivan Daschinsky  написал(а):
> 
> Igor, could you please check my PR?
> 
> пт, 29 мая 2020 г. в 15:28, Ivan Daschinsky :
> 
>> Thanks you all. Run patch (I've changed some code also) on TC -- all CPP
>> suites are green (GCC, CLang, Win64)
>> 
>> пт, 29 мая 2020 г. в 15:02, Zhenya Stanilovsky >> :
>> 
>>> 
>>> 
>>> Ivan besides documentation [1]
>>> -s no —  no works
>>> -- catch_system_errors =no — works properly well, tests are passed.
>>> 
>>> boost 1.65
>>> 
>>> [1]
>>> https://www.boost.org/doc/libs/1_65_0/libs/test/doc/html/boost_test/utf_reference/rt_param_reference/catch_system.html
>>> 
 Hello!
 
 I didn't check tests since I don't develop AI C++, merely use it as user.
 That's where we should wait for Igor Sapego to check.
 
 Regards,
 --
 Ilya Kasnacheev
 
 
 пт, 29 мая 2020 г. в 12:20, Ivan Daschinsky < ivanda...@gmail.com >:
 
> Ilya, thanks a lot! What about tests? I found one flag that must be
> supplied to boost.tests.
> This flag should fix JVM crash of C++ suites on Linux.
> 
> Zhenya Stanilovsky and me have checked, that without this flag tests
>>> failed
> with SIGSEGV early (boost catch this signal from jvm, but it is ok for
> jvm).
> Flag is -catch_system_errors=no. I added it to CTest runner. You can
> invoke it manually and using make test ARGS="-V"
> 
> 
> 
> пт, 29 мая 2020 г. в 11:54, Ilya Kasnacheev <
>>> ilya.kasnach...@gmail.com >:
> 
>> Hello!
>> 
>> Looks good to me! But we probably also ask Igor to take a look.
>> 
>> Compiled debug and release, without and with odbc, checked running
>>> thick
>> node and ODBC connection on Linux.
>> 
>> Regards,
>> --
>> Ilya Kasnacheev
>> 
>> 
>> чт, 28 мая 2020 г. в 17:31, Ivan Daschinsky < ivanda...@gmail.com >:
>> 
>>> Ok, PR is ready
>>> https://issues.apache.org/jira/browse/IGNITE-13078
>>> 
>>> Build tested on Mac OS X 10.15 and Ubuntu 20.04 with CMake 3.17.2
>>> and
>> 3.6.1
>>> Unfortunately, I was not able to test on Windows, but principally
>>> it
>> should
>>> works, but minor issues are probable.
>>> 
>>> Instruction is attached in PR.
>>> Any use reports are welcomed!
>>> 
>>> вт, 26 мая 2020 г. в 18:51, Ivan Daschinsky < ivanda...@gmail.com
 :
>>> 
 Stephen, looks great! I do mostly the same things in C++ code.
>>> Thank
>> you!
 
 вт, 26 мая 2020 г. в 18:33, Stephen Darlington <
 stephen.darling...@gridgain.com >:
 
> Not sure if it’ll help, but I made some changes to get it
>>> working
> on a
> Mac with the current built system. There may be some code worth
>> taking.
> 
> https://github.com/apache/ignite/pull/4872 <
> https://github.com/apache/ignite/pull/4872 >
> 
> Regards,
> Stephen
> 
>> On 26 May 2020, at 16:02, Ivan Daschinsky <
>>> ivanda...@gmail.com >
>>> wrote:
>> 
>> I appreciate any help, thank you, Ilya.
>> 
>> Currently I have a small PR without ticket (link in first
> post),but
>> I
>> decided not to file a jira issue before discussion.
>> Now I see, that this feature are of great interest to
>>> community.
> So
>> I
> file
>> a ticket, test myself on my home laptop (ubuntu 20.04)
>> and add detailed instructions to DEVNOTES.txt in a few days.
>> 
>> I would be happy if my someone can follow the instruction and
> write
>> possible issues.
>> 
>> I will notify about status update in this thread in next few
>>> days.
>> 
>> Thank you all very much for support!
>> 
>> 
>> вт, 26 мая 2020 г. в 17:50, Ilya Kasnacheev <
>>> ilya.kasnach...@gmail.com
>> :
>> 
>>> Hello!
>>> 
>>> I will assist with checking on Linux if you would contribute
>>> a
>> patch.
>>> Please start with a ticket (or even an IEP maybe?)
>>> 
>>> Regards,
>>> --
>>> Ilya Kasnacheev
>>> 
>>> 
>>> вт, 26 мая 2020 г. в 16:47, Ivan Daschinsky <
>>> ivanda...@gmail.com
>> :
>>> 
 Guys, I will certainly thoroughly test my fix not only
>>> unices,
> but
>>> on
 windows too.
 And I will describe it very thoroughly.
 
 When I was C++ developer (more than 10 years ago), I have
>>> not
> any
> trouble
 at all with CMake and Visual Studio 2005.
 Everything works and works good. Moreover, you can build
>>> with
>> NMake,
 msbuild and generate solutions for development.
 
 I suppose, for CI purposes, using 

Re: Re[2]: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

Thanks you all. Run patch (I've changed some code also) on TC -- all CPP
suites are green (GCC, CLang, Win64)

пт, 29 мая 2020 г. в 15:02, Zhenya Stanilovsky :

>
>
> Ivan besides documentation [1]
> -s no —  no works
> -- catch_system_errors =no — works properly well, tests are passed.
>
> boost 1.65
>
> [1]
> https://www.boost.org/doc/libs/1_65_0/libs/test/doc/html/boost_test/utf_reference/rt_param_reference/catch_system.html
>
> >Hello!
> >
> >I didn't check tests since I don't develop AI C++, merely use it as user.
> >That's where we should wait for Igor Sapego to check.
> >
> >Regards,
> >--
> >Ilya Kasnacheev
> >
> >
> >пт, 29 мая 2020 г. в 12:20, Ivan Daschinsky < ivanda...@gmail.com >:
> >
> >> Ilya, thanks a lot! What about tests? I found one flag that must be
> >> supplied to boost.tests.
> >> This flag should fix JVM crash of C++ suites on Linux.
> >>
> >> Zhenya Stanilovsky and me have checked, that without this flag tests
> failed
> >> with SIGSEGV early (boost catch this signal from jvm, but it is ok for
> >> jvm).
> >> Flag is -catch_system_errors=no. I added it to CTest runner. You can
> >> invoke it manually and using make test ARGS="-V"
> >>
> >>
> >>
> >> пт, 29 мая 2020 г. в 11:54, Ilya Kasnacheev < ilya.kasnach...@gmail.com
> >:
> >>
> >> > Hello!
> >> >
> >> > Looks good to me! But we probably also ask Igor to take a look.
> >> >
> >> > Compiled debug and release, without and with odbc, checked running
> thick
> >> > node and ODBC connection on Linux.
> >> >
> >> > Regards,
> >> > --
> >> > Ilya Kasnacheev
> >> >
> >> >
> >> > чт, 28 мая 2020 г. в 17:31, Ivan Daschinsky < ivanda...@gmail.com >:
> >> >
> >> > > Ok, PR is ready
> >> > >  https://issues.apache.org/jira/browse/IGNITE-13078
> >> > >
> >> > > Build tested on Mac OS X 10.15 and Ubuntu 20.04 with CMake 3.17.2
> and
> >> > 3.6.1
> >> > > Unfortunately, I was not able to test on Windows, but principally it
> >> > should
> >> > > works, but minor issues are probable.
> >> > >
> >> > > Instruction is attached in PR.
> >> > > Any use reports are welcomed!
> >> > >
> >> > > вт, 26 мая 2020 г. в 18:51, Ivan Daschinsky < ivanda...@gmail.com
> >:
> >> > >
> >> > > > Stephen, looks great! I do mostly the same things in C++ code.
> Thank
> >> > you!
> >> > > >
> >> > > > вт, 26 мая 2020 г. в 18:33, Stephen Darlington <
> >> > > >  stephen.darling...@gridgain.com >:
> >> > > >
> >> > > >> Not sure if it’ll help, but I made some changes to get it working
> >> on a
> >> > > >> Mac with the current built system. There may be some code worth
> >> > taking.
> >> > > >>
> >> > > >>  https://github.com/apache/ignite/pull/4872 <
> >> > > >>  https://github.com/apache/ignite/pull/4872 >
> >> > > >>
> >> > > >> Regards,
> >> > > >> Stephen
> >> > > >>
> >> > > >> > On 26 May 2020, at 16:02, Ivan Daschinsky <
> ivanda...@gmail.com >
> >> > > wrote:
> >> > > >> >
> >> > > >> > I appreciate any help, thank you, Ilya.
> >> > > >> >
> >> > > >> > Currently I have a small PR without ticket (link in first
> >> post),but
> >> > I
> >> > > >> > decided not to file a jira issue before discussion.
> >> > > >> > Now I see, that this feature are of great interest to
> community.
> >> So
> >> > I
> >> > > >> file
> >> > > >> > a ticket, test myself on my home laptop (ubuntu 20.04)
> >> > > >> > and add detailed instructions to DEVNOTES.txt in a few days.
> >> > > >> >
> >> > > >> > I would be happy if my someone can follow the instruction and
> >> write
> >> > > >> > possible issues.
> >> > > >> >
> >> > > >> > I will notify about status update in this thread in next few
> days.
> >> > > >> >
> >> > > >> > Thank you all very much for support!
> >> > > >> >
> >> > > >> >
> >> > > >> > вт, 26 мая 2020 г. в 17:50, Ilya Kasnacheev <
> >> > >  ilya.kasnach...@gmail.com
> >> > > >> >:
> >> > > >> >
> >> > > >> >> Hello!
> >> > > >> >>
> >> > > >> >> I will assist with checking on Linux if you would contribute a
> >> > patch.
> >> > > >> >> Please start with a ticket (or even an IEP maybe?)
> >> > > >> >>
> >> > > >> >> Regards,
> >> > > >> >> --
> >> > > >> >> Ilya Kasnacheev
> >> > > >> >>
> >> > > >> >>
> >> > > >> >> вт, 26 мая 2020 г. в 16:47, Ivan Daschinsky <
> ivanda...@gmail.com
> >> >:
> >> > > >> >>
> >> > > >> >>> Guys, I will certainly thoroughly test my fix not only
> unices,
> >> but
> >> > > on
> >> > > >> >>> windows too.
> >> > > >> >>> And I will describe it very thoroughly.
> >> > > >> >>>
> >> > > >> >>> When I was C++ developer (more than 10 years ago), I have not
> >> any
> >> > > >> trouble
> >> > > >> >>> at all with CMake and Visual Studio 2005.
> >> > > >> >>> Everything works and works good. Moreover, you can build with
> >> > NMake,
> >> > > >> >>> msbuild and generate solutions for development.
> >> > > >> >>>
> >> > > >> >>> I suppose, for CI purposes, using NMake is a way better, than
> >> use
> >> > vs
> >> > > >> >>> solutions.
> >> > > >> >>>
> >> > > >> >>> вт, 26 мая 2020 г. в 16:42, Nikolay Izhikov <
> >>  nizhi...@apache.org
> 

Re[2]: [DISCUSSION] Ignite.C++ and CMake

[Zhenya Stanilovsky]

Ivan besides documentation [1]
-s no —  no works
-- catch_system_errors =no — works properly well, tests are passed.
 
boost 1.65
 
[1] 
https://www.boost.org/doc/libs/1_65_0/libs/test/doc/html/boost_test/utf_reference/rt_param_reference/catch_system.html
  
>Hello!
>
>I didn't check tests since I don't develop AI C++, merely use it as user.
>That's where we should wait for Igor Sapego to check.
>
>Regards,
>--
>Ilya Kasnacheev
>
>
>пт, 29 мая 2020 г. в 12:20, Ivan Daschinsky < ivanda...@gmail.com >:
> 
>> Ilya, thanks a lot! What about tests? I found one flag that must be
>> supplied to boost.tests.
>> This flag should fix JVM crash of C++ suites on Linux.
>>
>> Zhenya Stanilovsky and me have checked, that without this flag tests failed
>> with SIGSEGV early (boost catch this signal from jvm, but it is ok for
>> jvm).
>> Flag is -catch_system_errors=no. I added it to CTest runner. You can
>> invoke it manually and using make test ARGS="-V"
>>
>>
>>
>> пт, 29 мая 2020 г. в 11:54, Ilya Kasnacheev < ilya.kasnach...@gmail.com >:
>>
>> > Hello!
>> >
>> > Looks good to me! But we probably also ask Igor to take a look.
>> >
>> > Compiled debug and release, without and with odbc, checked running thick
>> > node and ODBC connection on Linux.
>> >
>> > Regards,
>> > --
>> > Ilya Kasnacheev
>> >
>> >
>> > чт, 28 мая 2020 г. в 17:31, Ivan Daschinsky < ivanda...@gmail.com >:
>> >
>> > > Ok, PR is ready
>> > >  https://issues.apache.org/jira/browse/IGNITE-13078
>> > >
>> > > Build tested on Mac OS X 10.15 and Ubuntu 20.04 with CMake 3.17.2 and
>> > 3.6.1
>> > > Unfortunately, I was not able to test on Windows, but principally it
>> > should
>> > > works, but minor issues are probable.
>> > >
>> > > Instruction is attached in PR.
>> > > Any use reports are welcomed!
>> > >
>> > > вт, 26 мая 2020 г. в 18:51, Ivan Daschinsky < ivanda...@gmail.com >:
>> > >
>> > > > Stephen, looks great! I do mostly the same things in C++ code. Thank
>> > you!
>> > > >
>> > > > вт, 26 мая 2020 г. в 18:33, Stephen Darlington <
>> > > >  stephen.darling...@gridgain.com >:
>> > > >
>> > > >> Not sure if it’ll help, but I made some changes to get it working
>> on a
>> > > >> Mac with the current built system. There may be some code worth
>> > taking.
>> > > >>
>> > > >>  https://github.com/apache/ignite/pull/4872 <
>> > > >>  https://github.com/apache/ignite/pull/4872 >
>> > > >>
>> > > >> Regards,
>> > > >> Stephen
>> > > >>
>> > > >> > On 26 May 2020, at 16:02, Ivan Daschinsky < ivanda...@gmail.com >
>> > > wrote:
>> > > >> >
>> > > >> > I appreciate any help, thank you, Ilya.
>> > > >> >
>> > > >> > Currently I have a small PR without ticket (link in first
>> post),but
>> > I
>> > > >> > decided not to file a jira issue before discussion.
>> > > >> > Now I see, that this feature are of great interest to community.
>> So
>> > I
>> > > >> file
>> > > >> > a ticket, test myself on my home laptop (ubuntu 20.04)
>> > > >> > and add detailed instructions to DEVNOTES.txt in a few days.
>> > > >> >
>> > > >> > I would be happy if my someone can follow the instruction and
>> write
>> > > >> > possible issues.
>> > > >> >
>> > > >> > I will notify about status update in this thread in next few days.
>> > > >> >
>> > > >> > Thank you all very much for support!
>> > > >> >
>> > > >> >
>> > > >> > вт, 26 мая 2020 г. в 17:50, Ilya Kasnacheev <
>> > >  ilya.kasnach...@gmail.com
>> > > >> >:
>> > > >> >
>> > > >> >> Hello!
>> > > >> >>
>> > > >> >> I will assist with checking on Linux if you would contribute a
>> > patch.
>> > > >> >> Please start with a ticket (or even an IEP maybe?)
>> > > >> >>
>> > > >> >> Regards,
>> > > >> >> --
>> > > >> >> Ilya Kasnacheev
>> > > >> >>
>> > > >> >>
>> > > >> >> вт, 26 мая 2020 г. в 16:47, Ivan Daschinsky < ivanda...@gmail.com
>> >:
>> > > >> >>
>> > > >> >>> Guys, I will certainly thoroughly test my fix not only unices,
>> but
>> > > on
>> > > >> >>> windows too.
>> > > >> >>> And I will describe it very thoroughly.
>> > > >> >>>
>> > > >> >>> When I was C++ developer (more than 10 years ago), I have not
>> any
>> > > >> trouble
>> > > >> >>> at all with CMake and Visual Studio 2005.
>> > > >> >>> Everything works and works good. Moreover, you can build with
>> > NMake,
>> > > >> >>> msbuild and generate solutions for development.
>> > > >> >>>
>> > > >> >>> I suppose, for CI purposes, using NMake is a way better, than
>> use
>> > vs
>> > > >> >>> solutions.
>> > > >> >>>
>> > > >> >>> вт, 26 мая 2020 г. в 16:42, Nikolay Izhikov <
>>  nizhi...@apache.org
>> > >:
>> > > >> >>>
>> > > >>  Hello, Igor.
>> > > >> 
>> > > >> > Nikolay, removing support for a certain build system is a
>> > breaking
>> > > >>  change.
>> > > >> 
>> > > >>  No, it’s not.
>> > > >>  Why do you think so?
>> > > >> 
>> > > >>  Development environment and build system is a subject to change
>> > in
>> > > >> any
>> > > >>  project.
>> > > >>  We can drop or add support of any build system any time 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ilya Kasnacheev]

Hello!

I didn't check tests since I don't develop AI C++, merely use it as user.
That's where we should wait for Igor Sapego to check.

Regards,
-- 
Ilya Kasnacheev


пт, 29 мая 2020 г. в 12:20, Ivan Daschinsky :

> Ilya, thanks a lot! What about tests? I found one flag that must be
> supplied to boost.tests.
> This flag should fix JVM crash of C++ suites on Linux.
>
> Zhenya Stanilovsky and me have checked, that without this flag tests failed
> with SIGSEGV early (boost catch this signal from jvm, but it is ok for
> jvm).
> Flag is -catch_system_errors=no. I added it to CTest runner. You can
> invoke it manually and using make test ARGS="-V"
>
>
>
> пт, 29 мая 2020 г. в 11:54, Ilya Kasnacheev :
>
> > Hello!
> >
> > Looks good to me! But we probably also ask Igor to take a look.
> >
> > Compiled debug and release, without and with odbc, checked running thick
> > node and ODBC connection on Linux.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > чт, 28 мая 2020 г. в 17:31, Ivan Daschinsky :
> >
> > > Ok, PR is ready
> > > https://issues.apache.org/jira/browse/IGNITE-13078
> > >
> > > Build tested on Mac OS X 10.15 and Ubuntu 20.04 with CMake 3.17.2 and
> > 3.6.1
> > > Unfortunately, I was not able to test on Windows, but principally it
> > should
> > > works, but minor issues are probable.
> > >
> > > Instruction is attached in PR.
> > > Any use reports are welcomed!
> > >
> > > вт, 26 мая 2020 г. в 18:51, Ivan Daschinsky :
> > >
> > > > Stephen, looks great! I do mostly the same things in C++ code. Thank
> > you!
> > > >
> > > > вт, 26 мая 2020 г. в 18:33, Stephen Darlington <
> > > > stephen.darling...@gridgain.com>:
> > > >
> > > >> Not sure if it’ll help, but I made some changes to get it working
> on a
> > > >> Mac with the current built system. There may be some code worth
> > taking.
> > > >>
> > > >> https://github.com/apache/ignite/pull/4872 <
> > > >> https://github.com/apache/ignite/pull/4872>
> > > >>
> > > >> Regards,
> > > >> Stephen
> > > >>
> > > >> > On 26 May 2020, at 16:02, Ivan Daschinsky 
> > > wrote:
> > > >> >
> > > >> > I appreciate any help, thank you, Ilya.
> > > >> >
> > > >> > Currently I have a small PR without ticket (link in first
> post),but
> > I
> > > >> > decided not to file a jira issue before discussion.
> > > >> > Now I see, that this feature are of great interest to community.
> So
> > I
> > > >> file
> > > >> > a ticket, test myself on my home laptop (ubuntu 20.04)
> > > >> > and add detailed instructions to DEVNOTES.txt in a few days.
> > > >> >
> > > >> > I would be happy if my someone can follow the instruction and
> write
> > > >> > possible issues.
> > > >> >
> > > >> > I will notify about status update in this thread in next few days.
> > > >> >
> > > >> > Thank you all very much for support!
> > > >> >
> > > >> >
> > > >> > вт, 26 мая 2020 г. в 17:50, Ilya Kasnacheev <
> > > ilya.kasnach...@gmail.com
> > > >> >:
> > > >> >
> > > >> >> Hello!
> > > >> >>
> > > >> >> I will assist with checking on Linux if you would contribute a
> > patch.
> > > >> >> Please start with a ticket (or even an IEP maybe?)
> > > >> >>
> > > >> >> Regards,
> > > >> >> --
> > > >> >> Ilya Kasnacheev
> > > >> >>
> > > >> >>
> > > >> >> вт, 26 мая 2020 г. в 16:47, Ivan Daschinsky  >:
> > > >> >>
> > > >> >>> Guys, I will certainly thoroughly test my fix not only unices,
> but
> > > on
> > > >> >>> windows too.
> > > >> >>> And I will describe it very thoroughly.
> > > >> >>>
> > > >> >>> When I was C++ developer (more than 10 years ago), I have not
> any
> > > >> trouble
> > > >> >>> at all with CMake and Visual Studio 2005.
> > > >> >>> Everything works and works good. Moreover, you can build with
> > NMake,
> > > >> >>> msbuild and generate solutions for development.
> > > >> >>>
> > > >> >>> I suppose, for CI purposes, using NMake is a way better, than
> use
> > vs
> > > >> >>> solutions.
> > > >> >>>
> > > >> >>> вт, 26 мая 2020 г. в 16:42, Nikolay Izhikov <
> nizhi...@apache.org
> > >:
> > > >> >>>
> > > >>  Hello, Igor.
> > > >> 
> > > >> > Nikolay, removing support for a certain build system is a
> > breaking
> > > >>  change.
> > > >> 
> > > >>  No, it’s not.
> > > >>  Why do you think so?
> > > >> 
> > > >>  Development environment and build system is a subject to change
> > in
> > > >> any
> > > >>  project.
> > > >>  We can drop or add support of any build system any time we
> want.
> > > >> 
> > > >> > 26 мая 2020 г., в 16:35, Ilya Kasnacheev <
> > > ilya.kasnach...@gmail.com
> > > >> >
> > > >>  написал(а):
> > > >> >
> > > >> > Hello!
> > > >> >
> > > >> > I don't see why we can't get rid of autotools in a minor
> > release,
> > > >>  provided
> > > >> > that cmake actually works. Removing native VS support may be a
> > > >> >>> different
> > > >> > thing.
> > > >> >
> > > >> > Build system and precise set of dependencies is not a part of
> > > public
> > > >> >>> API
> > > 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

Also without with flag we can observe many failures of suites on TC

https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformCLinux?branch=%3Cdefault%3E=builds#all-projects


пт, 29 мая 2020 г. в 12:20, Ivan Daschinsky :

> Ilya, thanks a lot! What about tests? I found one flag that must be
> supplied to boost.tests.
> This flag should fix JVM crash of C++ suites on Linux.
>
> Zhenya Stanilovsky and me have checked, that without this flag tests
> failed with SIGSEGV early (boost catch this signal from jvm, but it is ok
> for jvm).
> Flag is -catch_system_errors=no. I added it to CTest runner. You can
> invoke it manually and using make test ARGS="-V"
>
>
>
> пт, 29 мая 2020 г. в 11:54, Ilya Kasnacheev :
>
>> Hello!
>>
>> Looks good to me! But we probably also ask Igor to take a look.
>>
>> Compiled debug and release, without and with odbc, checked running thick
>> node and ODBC connection on Linux.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> чт, 28 мая 2020 г. в 17:31, Ivan Daschinsky :
>>
>> > Ok, PR is ready
>> > https://issues.apache.org/jira/browse/IGNITE-13078
>> >
>> > Build tested on Mac OS X 10.15 and Ubuntu 20.04 with CMake 3.17.2 and
>> 3.6.1
>> > Unfortunately, I was not able to test on Windows, but principally it
>> should
>> > works, but minor issues are probable.
>> >
>> > Instruction is attached in PR.
>> > Any use reports are welcomed!
>> >
>> > вт, 26 мая 2020 г. в 18:51, Ivan Daschinsky :
>> >
>> > > Stephen, looks great! I do mostly the same things in C++ code. Thank
>> you!
>> > >
>> > > вт, 26 мая 2020 г. в 18:33, Stephen Darlington <
>> > > stephen.darling...@gridgain.com>:
>> > >
>> > >> Not sure if it’ll help, but I made some changes to get it working on
>> a
>> > >> Mac with the current built system. There may be some code worth
>> taking.
>> > >>
>> > >> https://github.com/apache/ignite/pull/4872 <
>> > >> https://github.com/apache/ignite/pull/4872>
>> > >>
>> > >> Regards,
>> > >> Stephen
>> > >>
>> > >> > On 26 May 2020, at 16:02, Ivan Daschinsky 
>> > wrote:
>> > >> >
>> > >> > I appreciate any help, thank you, Ilya.
>> > >> >
>> > >> > Currently I have a small PR without ticket (link in first
>> post),but I
>> > >> > decided not to file a jira issue before discussion.
>> > >> > Now I see, that this feature are of great interest to community.
>> So I
>> > >> file
>> > >> > a ticket, test myself on my home laptop (ubuntu 20.04)
>> > >> > and add detailed instructions to DEVNOTES.txt in a few days.
>> > >> >
>> > >> > I would be happy if my someone can follow the instruction and write
>> > >> > possible issues.
>> > >> >
>> > >> > I will notify about status update in this thread in next few days.
>> > >> >
>> > >> > Thank you all very much for support!
>> > >> >
>> > >> >
>> > >> > вт, 26 мая 2020 г. в 17:50, Ilya Kasnacheev <
>> > ilya.kasnach...@gmail.com
>> > >> >:
>> > >> >
>> > >> >> Hello!
>> > >> >>
>> > >> >> I will assist with checking on Linux if you would contribute a
>> patch.
>> > >> >> Please start with a ticket (or even an IEP maybe?)
>> > >> >>
>> > >> >> Regards,
>> > >> >> --
>> > >> >> Ilya Kasnacheev
>> > >> >>
>> > >> >>
>> > >> >> вт, 26 мая 2020 г. в 16:47, Ivan Daschinsky > >:
>> > >> >>
>> > >> >>> Guys, I will certainly thoroughly test my fix not only unices,
>> but
>> > on
>> > >> >>> windows too.
>> > >> >>> And I will describe it very thoroughly.
>> > >> >>>
>> > >> >>> When I was C++ developer (more than 10 years ago), I have not any
>> > >> trouble
>> > >> >>> at all with CMake and Visual Studio 2005.
>> > >> >>> Everything works and works good. Moreover, you can build with
>> NMake,
>> > >> >>> msbuild and generate solutions for development.
>> > >> >>>
>> > >> >>> I suppose, for CI purposes, using NMake is a way better, than
>> use vs
>> > >> >>> solutions.
>> > >> >>>
>> > >> >>> вт, 26 мая 2020 г. в 16:42, Nikolay Izhikov > >:
>> > >> >>>
>> > >>  Hello, Igor.
>> > >> 
>> > >> > Nikolay, removing support for a certain build system is a
>> breaking
>> > >>  change.
>> > >> 
>> > >>  No, it’s not.
>> > >>  Why do you think so?
>> > >> 
>> > >>  Development environment and build system is a subject to change
>> in
>> > >> any
>> > >>  project.
>> > >>  We can drop or add support of any build system any time we want.
>> > >> 
>> > >> > 26 мая 2020 г., в 16:35, Ilya Kasnacheev <
>> > ilya.kasnach...@gmail.com
>> > >> >
>> > >>  написал(а):
>> > >> >
>> > >> > Hello!
>> > >> >
>> > >> > I don't see why we can't get rid of autotools in a minor
>> release,
>> > >>  provided
>> > >> > that cmake actually works. Removing native VS support may be a
>> > >> >>> different
>> > >> > thing.
>> > >> >
>> > >> > Build system and precise set of dependencies is not a part of
>> > public
>> > >> >>> API
>> > >>  in
>> > >> > my opinion.
>> > >> >
>> > >> > Regards,
>> > >> > --
>> > >> > Ilya Kasnacheev
>> > >> >
>> > >> 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

Ilya, thanks a lot! What about tests? I found one flag that must be
supplied to boost.tests.
This flag should fix JVM crash of C++ suites on Linux.

Zhenya Stanilovsky and me have checked, that without this flag tests failed
with SIGSEGV early (boost catch this signal from jvm, but it is ok for jvm).
Flag is -catch_system_errors=no. I added it to CTest runner. You can
invoke it manually and using make test ARGS="-V"



пт, 29 мая 2020 г. в 11:54, Ilya Kasnacheev :

> Hello!
>
> Looks good to me! But we probably also ask Igor to take a look.
>
> Compiled debug and release, without and with odbc, checked running thick
> node and ODBC connection on Linux.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 28 мая 2020 г. в 17:31, Ivan Daschinsky :
>
> > Ok, PR is ready
> > https://issues.apache.org/jira/browse/IGNITE-13078
> >
> > Build tested on Mac OS X 10.15 and Ubuntu 20.04 with CMake 3.17.2 and
> 3.6.1
> > Unfortunately, I was not able to test on Windows, but principally it
> should
> > works, but minor issues are probable.
> >
> > Instruction is attached in PR.
> > Any use reports are welcomed!
> >
> > вт, 26 мая 2020 г. в 18:51, Ivan Daschinsky :
> >
> > > Stephen, looks great! I do mostly the same things in C++ code. Thank
> you!
> > >
> > > вт, 26 мая 2020 г. в 18:33, Stephen Darlington <
> > > stephen.darling...@gridgain.com>:
> > >
> > >> Not sure if it’ll help, but I made some changes to get it working on a
> > >> Mac with the current built system. There may be some code worth
> taking.
> > >>
> > >> https://github.com/apache/ignite/pull/4872 <
> > >> https://github.com/apache/ignite/pull/4872>
> > >>
> > >> Regards,
> > >> Stephen
> > >>
> > >> > On 26 May 2020, at 16:02, Ivan Daschinsky 
> > wrote:
> > >> >
> > >> > I appreciate any help, thank you, Ilya.
> > >> >
> > >> > Currently I have a small PR without ticket (link in first post),but
> I
> > >> > decided not to file a jira issue before discussion.
> > >> > Now I see, that this feature are of great interest to community. So
> I
> > >> file
> > >> > a ticket, test myself on my home laptop (ubuntu 20.04)
> > >> > and add detailed instructions to DEVNOTES.txt in a few days.
> > >> >
> > >> > I would be happy if my someone can follow the instruction and write
> > >> > possible issues.
> > >> >
> > >> > I will notify about status update in this thread in next few days.
> > >> >
> > >> > Thank you all very much for support!
> > >> >
> > >> >
> > >> > вт, 26 мая 2020 г. в 17:50, Ilya Kasnacheev <
> > ilya.kasnach...@gmail.com
> > >> >:
> > >> >
> > >> >> Hello!
> > >> >>
> > >> >> I will assist with checking on Linux if you would contribute a
> patch.
> > >> >> Please start with a ticket (or even an IEP maybe?)
> > >> >>
> > >> >> Regards,
> > >> >> --
> > >> >> Ilya Kasnacheev
> > >> >>
> > >> >>
> > >> >> вт, 26 мая 2020 г. в 16:47, Ivan Daschinsky :
> > >> >>
> > >> >>> Guys, I will certainly thoroughly test my fix not only unices, but
> > on
> > >> >>> windows too.
> > >> >>> And I will describe it very thoroughly.
> > >> >>>
> > >> >>> When I was C++ developer (more than 10 years ago), I have not any
> > >> trouble
> > >> >>> at all with CMake and Visual Studio 2005.
> > >> >>> Everything works and works good. Moreover, you can build with
> NMake,
> > >> >>> msbuild and generate solutions for development.
> > >> >>>
> > >> >>> I suppose, for CI purposes, using NMake is a way better, than use
> vs
> > >> >>> solutions.
> > >> >>>
> > >> >>> вт, 26 мая 2020 г. в 16:42, Nikolay Izhikov  >:
> > >> >>>
> > >>  Hello, Igor.
> > >> 
> > >> > Nikolay, removing support for a certain build system is a
> breaking
> > >>  change.
> > >> 
> > >>  No, it’s not.
> > >>  Why do you think so?
> > >> 
> > >>  Development environment and build system is a subject to change
> in
> > >> any
> > >>  project.
> > >>  We can drop or add support of any build system any time we want.
> > >> 
> > >> > 26 мая 2020 г., в 16:35, Ilya Kasnacheev <
> > ilya.kasnach...@gmail.com
> > >> >
> > >>  написал(а):
> > >> >
> > >> > Hello!
> > >> >
> > >> > I don't see why we can't get rid of autotools in a minor
> release,
> > >>  provided
> > >> > that cmake actually works. Removing native VS support may be a
> > >> >>> different
> > >> > thing.
> > >> >
> > >> > Build system and precise set of dependencies is not a part of
> > public
> > >> >>> API
> > >>  in
> > >> > my opinion.
> > >> >
> > >> > Regards,
> > >> > --
> > >> > Ilya Kasnacheev
> > >> >
> > >> >
> > >> > вт, 26 мая 2020 г. в 16:02, Igor Sapego :
> > >> >
> > >> >> 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
> > >> >>
> > >> >>
> > >> 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ilya Kasnacheev]

Hello!

Looks good to me! But we probably also ask Igor to take a look.

Compiled debug and release, without and with odbc, checked running thick
node and ODBC connection on Linux.

Regards,
-- 
Ilya Kasnacheev


чт, 28 мая 2020 г. в 17:31, Ivan Daschinsky :

> Ok, PR is ready
> https://issues.apache.org/jira/browse/IGNITE-13078
>
> Build tested on Mac OS X 10.15 and Ubuntu 20.04 with CMake 3.17.2 and 3.6.1
> Unfortunately, I was not able to test on Windows, but principally it should
> works, but minor issues are probable.
>
> Instruction is attached in PR.
> Any use reports are welcomed!
>
> вт, 26 мая 2020 г. в 18:51, Ivan Daschinsky :
>
> > Stephen, looks great! I do mostly the same things in C++ code. Thank you!
> >
> > вт, 26 мая 2020 г. в 18:33, Stephen Darlington <
> > stephen.darling...@gridgain.com>:
> >
> >> Not sure if it’ll help, but I made some changes to get it working on a
> >> Mac with the current built system. There may be some code worth taking.
> >>
> >> https://github.com/apache/ignite/pull/4872 <
> >> https://github.com/apache/ignite/pull/4872>
> >>
> >> Regards,
> >> Stephen
> >>
> >> > On 26 May 2020, at 16:02, Ivan Daschinsky 
> wrote:
> >> >
> >> > I appreciate any help, thank you, Ilya.
> >> >
> >> > Currently I have a small PR without ticket (link in first post),but I
> >> > decided not to file a jira issue before discussion.
> >> > Now I see, that this feature are of great interest to community. So I
> >> file
> >> > a ticket, test myself on my home laptop (ubuntu 20.04)
> >> > and add detailed instructions to DEVNOTES.txt in a few days.
> >> >
> >> > I would be happy if my someone can follow the instruction and write
> >> > possible issues.
> >> >
> >> > I will notify about status update in this thread in next few days.
> >> >
> >> > Thank you all very much for support!
> >> >
> >> >
> >> > вт, 26 мая 2020 г. в 17:50, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com
> >> >:
> >> >
> >> >> Hello!
> >> >>
> >> >> I will assist with checking on Linux if you would contribute a patch.
> >> >> Please start with a ticket (or even an IEP maybe?)
> >> >>
> >> >> Regards,
> >> >> --
> >> >> Ilya Kasnacheev
> >> >>
> >> >>
> >> >> вт, 26 мая 2020 г. в 16:47, Ivan Daschinsky :
> >> >>
> >> >>> Guys, I will certainly thoroughly test my fix not only unices, but
> on
> >> >>> windows too.
> >> >>> And I will describe it very thoroughly.
> >> >>>
> >> >>> When I was C++ developer (more than 10 years ago), I have not any
> >> trouble
> >> >>> at all with CMake and Visual Studio 2005.
> >> >>> Everything works and works good. Moreover, you can build with NMake,
> >> >>> msbuild and generate solutions for development.
> >> >>>
> >> >>> I suppose, for CI purposes, using NMake is a way better, than use vs
> >> >>> solutions.
> >> >>>
> >> >>> вт, 26 мая 2020 г. в 16:42, Nikolay Izhikov :
> >> >>>
> >>  Hello, Igor.
> >> 
> >> > Nikolay, removing support for a certain build system is a breaking
> >>  change.
> >> 
> >>  No, it’s not.
> >>  Why do you think so?
> >> 
> >>  Development environment and build system is a subject to change in
> >> any
> >>  project.
> >>  We can drop or add support of any build system any time we want.
> >> 
> >> > 26 мая 2020 г., в 16:35, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com
> >> >
> >>  написал(а):
> >> >
> >> > Hello!
> >> >
> >> > I don't see why we can't get rid of autotools in a minor release,
> >>  provided
> >> > that cmake actually works. Removing native VS support may be a
> >> >>> different
> >> > thing.
> >> >
> >> > Build system and precise set of dependencies is not a part of
> public
> >> >>> API
> >>  in
> >> > my opinion.
> >> >
> >> > Regards,
> >> > --
> >> > Ilya Kasnacheev
> >> >
> >> >
> >> > вт, 26 мая 2020 г. в 16:02, Igor Sapego :
> >> >
> >> >> 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
> >>   wrote:
> >> 
> >> >
> >> > Ivan huge +1 with your proposal.
> >> > I had some problems with odbc tests building too, looks like
> >> >> cmake
> >> >> will
> >> > make it more easy.
> >> 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

Ok, PR is ready
https://issues.apache.org/jira/browse/IGNITE-13078

Build tested on Mac OS X 10.15 and Ubuntu 20.04 with CMake 3.17.2 and 3.6.1
Unfortunately, I was not able to test on Windows, but principally it should
works, but minor issues are probable.

Instruction is attached in PR.
Any use reports are welcomed!

вт, 26 мая 2020 г. в 18:51, Ivan Daschinsky :

> Stephen, looks great! I do mostly the same things in C++ code. Thank you!
>
> вт, 26 мая 2020 г. в 18:33, Stephen Darlington <
> stephen.darling...@gridgain.com>:
>
>> Not sure if it’ll help, but I made some changes to get it working on a
>> Mac with the current built system. There may be some code worth taking.
>>
>> https://github.com/apache/ignite/pull/4872 <
>> https://github.com/apache/ignite/pull/4872>
>>
>> Regards,
>> Stephen
>>
>> > On 26 May 2020, at 16:02, Ivan Daschinsky  wrote:
>> >
>> > I appreciate any help, thank you, Ilya.
>> >
>> > Currently I have a small PR without ticket (link in first post),but I
>> > decided not to file a jira issue before discussion.
>> > Now I see, that this feature are of great interest to community. So I
>> file
>> > a ticket, test myself on my home laptop (ubuntu 20.04)
>> > and add detailed instructions to DEVNOTES.txt in a few days.
>> >
>> > I would be happy if my someone can follow the instruction and write
>> > possible issues.
>> >
>> > I will notify about status update in this thread in next few days.
>> >
>> > Thank you all very much for support!
>> >
>> >
>> > вт, 26 мая 2020 г. в 17:50, Ilya Kasnacheev > >:
>> >
>> >> Hello!
>> >>
>> >> I will assist with checking on Linux if you would contribute a patch.
>> >> Please start with a ticket (or even an IEP maybe?)
>> >>
>> >> Regards,
>> >> --
>> >> Ilya Kasnacheev
>> >>
>> >>
>> >> вт, 26 мая 2020 г. в 16:47, Ivan Daschinsky :
>> >>
>> >>> Guys, I will certainly thoroughly test my fix not only unices, but on
>> >>> windows too.
>> >>> And I will describe it very thoroughly.
>> >>>
>> >>> When I was C++ developer (more than 10 years ago), I have not any
>> trouble
>> >>> at all with CMake and Visual Studio 2005.
>> >>> Everything works and works good. Moreover, you can build with NMake,
>> >>> msbuild and generate solutions for development.
>> >>>
>> >>> I suppose, for CI purposes, using NMake is a way better, than use vs
>> >>> solutions.
>> >>>
>> >>> вт, 26 мая 2020 г. в 16:42, Nikolay Izhikov :
>> >>>
>>  Hello, Igor.
>> 
>> > Nikolay, removing support for a certain build system is a breaking
>>  change.
>> 
>>  No, it’s not.
>>  Why do you think so?
>> 
>>  Development environment and build system is a subject to change in
>> any
>>  project.
>>  We can drop or add support of any build system any time we want.
>> 
>> > 26 мая 2020 г., в 16:35, Ilya Kasnacheev > >
>>  написал(а):
>> >
>> > Hello!
>> >
>> > I don't see why we can't get rid of autotools in a minor release,
>>  provided
>> > that cmake actually works. Removing native VS support may be a
>> >>> different
>> > thing.
>> >
>> > Build system and precise set of dependencies is not a part of public
>> >>> API
>>  in
>> > my opinion.
>> >
>> > Regards,
>> > --
>> > Ilya Kasnacheev
>> >
>> >
>> > вт, 26 мая 2020 г. в 16:02, Igor Sapego :
>> >
>> >> 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 > >:
>> >>>
>>  +1
>> 
>>  On Tue, May 26, 2020 at 12:02 PM Zhenya Stanilovsky
>>   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 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

Stephen, looks great! I do mostly the same things in C++ code. Thank you!

вт, 26 мая 2020 г. в 18:33, Stephen Darlington <
stephen.darling...@gridgain.com>:

> Not sure if it’ll help, but I made some changes to get it working on a Mac
> with the current built system. There may be some code worth taking.
>
> https://github.com/apache/ignite/pull/4872 <
> https://github.com/apache/ignite/pull/4872>
>
> Regards,
> Stephen
>
> > On 26 May 2020, at 16:02, Ivan Daschinsky  wrote:
> >
> > I appreciate any help, thank you, Ilya.
> >
> > Currently I have a small PR without ticket (link in first post),but I
> > decided not to file a jira issue before discussion.
> > Now I see, that this feature are of great interest to community. So I
> file
> > a ticket, test myself on my home laptop (ubuntu 20.04)
> > and add detailed instructions to DEVNOTES.txt in a few days.
> >
> > I would be happy if my someone can follow the instruction and write
> > possible issues.
> >
> > I will notify about status update in this thread in next few days.
> >
> > Thank you all very much for support!
> >
> >
> > вт, 26 мая 2020 г. в 17:50, Ilya Kasnacheev :
> >
> >> Hello!
> >>
> >> I will assist with checking on Linux if you would contribute a patch.
> >> Please start with a ticket (or even an IEP maybe?)
> >>
> >> Regards,
> >> --
> >> Ilya Kasnacheev
> >>
> >>
> >> вт, 26 мая 2020 г. в 16:47, Ivan Daschinsky :
> >>
> >>> Guys, I will certainly thoroughly test my fix not only unices, but on
> >>> windows too.
> >>> And I will describe it very thoroughly.
> >>>
> >>> When I was C++ developer (more than 10 years ago), I have not any
> trouble
> >>> at all with CMake and Visual Studio 2005.
> >>> Everything works and works good. Moreover, you can build with NMake,
> >>> msbuild and generate solutions for development.
> >>>
> >>> I suppose, for CI purposes, using NMake is a way better, than use vs
> >>> solutions.
> >>>
> >>> вт, 26 мая 2020 г. в 16:42, Nikolay Izhikov :
> >>>
>  Hello, Igor.
> 
> > Nikolay, removing support for a certain build system is a breaking
>  change.
> 
>  No, it’s not.
>  Why do you think so?
> 
>  Development environment and build system is a subject to change in any
>  project.
>  We can drop or add support of any build system any time we want.
> 
> > 26 мая 2020 г., в 16:35, Ilya Kasnacheev 
>  написал(а):
> >
> > Hello!
> >
> > I don't see why we can't get rid of autotools in a minor release,
>  provided
> > that cmake actually works. Removing native VS support may be a
> >>> different
> > thing.
> >
> > Build system and precise set of dependencies is not a part of public
> >>> API
>  in
> > my opinion.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > вт, 26 мая 2020 г. в 16:02, Igor Sapego :
> >
> >> 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 :
> >>>
>  +1
> 
>  On Tue, May 26, 2020 at 12:02 PM Zhenya Stanilovsky
>   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 

Re: [DISCUSSION] Ignite.C++ and CMake

[Stephen Darlington]

Not sure if it’ll help, but I made some changes to get it working on a Mac with 
the current built system. There may be some code worth taking.

https://github.com/apache/ignite/pull/4872 


Regards,
Stephen

> On 26 May 2020, at 16:02, Ivan Daschinsky  wrote:
> 
> I appreciate any help, thank you, Ilya.
> 
> Currently I have a small PR without ticket (link in first post),but I
> decided not to file a jira issue before discussion.
> Now I see, that this feature are of great interest to community. So I file
> a ticket, test myself on my home laptop (ubuntu 20.04)
> and add detailed instructions to DEVNOTES.txt in a few days.
> 
> I would be happy if my someone can follow the instruction and write
> possible issues.
> 
> I will notify about status update in this thread in next few days.
> 
> Thank you all very much for support!
> 
> 
> вт, 26 мая 2020 г. в 17:50, Ilya Kasnacheev :
> 
>> Hello!
>> 
>> I will assist with checking on Linux if you would contribute a patch.
>> Please start with a ticket (or even an IEP maybe?)
>> 
>> Regards,
>> --
>> Ilya Kasnacheev
>> 
>> 
>> вт, 26 мая 2020 г. в 16:47, Ivan Daschinsky :
>> 
>>> Guys, I will certainly thoroughly test my fix not only unices, but on
>>> windows too.
>>> And I will describe it very thoroughly.
>>> 
>>> When I was C++ developer (more than 10 years ago), I have not any trouble
>>> at all with CMake and Visual Studio 2005.
>>> Everything works and works good. Moreover, you can build with NMake,
>>> msbuild and generate solutions for development.
>>> 
>>> I suppose, for CI purposes, using NMake is a way better, than use vs
>>> solutions.
>>> 
>>> вт, 26 мая 2020 г. в 16:42, Nikolay Izhikov :
>>> 
 Hello, Igor.
 
> Nikolay, removing support for a certain build system is a breaking
 change.
 
 No, it’s not.
 Why do you think so?
 
 Development environment and build system is a subject to change in any
 project.
 We can drop or add support of any build system any time we want.
 
> 26 мая 2020 г., в 16:35, Ilya Kasnacheev 
 написал(а):
> 
> Hello!
> 
> I don't see why we can't get rid of autotools in a minor release,
 provided
> that cmake actually works. Removing native VS support may be a
>>> different
> thing.
> 
> Build system and precise set of dependencies is not a part of public
>>> API
 in
> my opinion.
> 
> Regards,
> --
> Ilya Kasnacheev
> 
> 
> вт, 26 мая 2020 г. в 16:02, Igor Sapego :
> 
>> 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 :
>>> 
 +1
 
 On Tue, May 26, 2020 at 12:02 PM Zhenya Stanilovsky
  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

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

I appreciate any help, thank you, Ilya.

Currently I have a small PR without ticket (link in first post),but I
decided not to file a jira issue before discussion.
Now I see, that this feature are of great interest to community. So I file
a ticket, test myself on my home laptop (ubuntu 20.04)
 and add detailed instructions to DEVNOTES.txt in a few days.

I would be happy if my someone can follow the instruction and write
possible issues.

I will notify about status update in this thread in next few days.

Thank you all very much for support!


вт, 26 мая 2020 г. в 17:50, Ilya Kasnacheev :

> Hello!
>
> I will assist with checking on Linux if you would contribute a patch.
> Please start with a ticket (or even an IEP maybe?)
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 26 мая 2020 г. в 16:47, Ivan Daschinsky :
>
> > Guys, I will certainly thoroughly test my fix not only unices, but on
> > windows too.
> > And I will describe it very thoroughly.
> >
> > When I was C++ developer (more than 10 years ago), I have not any trouble
> > at all with CMake and Visual Studio 2005.
> > Everything works and works good. Moreover, you can build with NMake,
> > msbuild and generate solutions for development.
> >
> > I suppose, for CI purposes, using NMake is a way better, than use vs
> > solutions.
> >
> > вт, 26 мая 2020 г. в 16:42, Nikolay Izhikov :
> >
> > > Hello, Igor.
> > >
> > > > Nikolay, removing support for a certain build system is a breaking
> > > change.
> > >
> > > No, it’s not.
> > > Why do you think so?
> > >
> > > Development environment and build system is a subject to change in any
> > > project.
> > > We can drop or add support of any build system any time we want.
> > >
> > > > 26 мая 2020 г., в 16:35, Ilya Kasnacheev 
> > > написал(а):
> > > >
> > > > Hello!
> > > >
> > > > I don't see why we can't get rid of autotools in a minor release,
> > > provided
> > > > that cmake actually works. Removing native VS support may be a
> > different
> > > > thing.
> > > >
> > > > Build system and precise set of dependencies is not a part of public
> > API
> > > in
> > > > my opinion.
> > > >
> > > > Regards,
> > > > --
> > > > Ilya Kasnacheev
> > > >
> > > >
> > > > вт, 26 мая 2020 г. в 16:02, Igor Sapego :
> > > >
> > > >> 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 :
> > > >>>
> > >  +1
> > > 
> > >  On Tue, May 26, 2020 at 12:02 PM Zhenya Stanilovsky
> > >   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, 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ilya Kasnacheev]

Hello!

I will assist with checking on Linux if you would contribute a patch.
Please start with a ticket (or even an IEP maybe?)

Regards,
-- 
Ilya Kasnacheev


вт, 26 мая 2020 г. в 16:47, Ivan Daschinsky :

> Guys, I will certainly thoroughly test my fix not only unices, but on
> windows too.
> And I will describe it very thoroughly.
>
> When I was C++ developer (more than 10 years ago), I have not any trouble
> at all with CMake and Visual Studio 2005.
> Everything works and works good. Moreover, you can build with NMake,
> msbuild and generate solutions for development.
>
> I suppose, for CI purposes, using NMake is a way better, than use vs
> solutions.
>
> вт, 26 мая 2020 г. в 16:42, Nikolay Izhikov :
>
> > Hello, Igor.
> >
> > > Nikolay, removing support for a certain build system is a breaking
> > change.
> >
> > No, it’s not.
> > Why do you think so?
> >
> > Development environment and build system is a subject to change in any
> > project.
> > We can drop or add support of any build system any time we want.
> >
> > > 26 мая 2020 г., в 16:35, Ilya Kasnacheev 
> > написал(а):
> > >
> > > Hello!
> > >
> > > I don't see why we can't get rid of autotools in a minor release,
> > provided
> > > that cmake actually works. Removing native VS support may be a
> different
> > > thing.
> > >
> > > Build system and precise set of dependencies is not a part of public
> API
> > in
> > > my opinion.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > вт, 26 мая 2020 г. в 16:02, Igor Sapego :
> > >
> > >> 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 :
> > >>>
> >  +1
> > 
> >  On Tue, May 26, 2020 at 12:02 PM Zhenya Stanilovsky
> >   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
>

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

Guys, I will certainly thoroughly test my fix not only unices, but on
windows too.
And I will describe it very thoroughly.

When I was C++ developer (more than 10 years ago), I have not any trouble
at all with CMake and Visual Studio 2005.
Everything works and works good. Moreover, you can build with NMake,
msbuild and generate solutions for development.

I suppose, for CI purposes, using NMake is a way better, than use vs
solutions.

вт, 26 мая 2020 г. в 16:42, Nikolay Izhikov :

> Hello, Igor.
>
> > Nikolay, removing support for a certain build system is a breaking
> change.
>
> No, it’s not.
> Why do you think so?
>
> Development environment and build system is a subject to change in any
> project.
> We can drop or add support of any build system any time we want.
>
> > 26 мая 2020 г., в 16:35, Ilya Kasnacheev 
> написал(а):
> >
> > Hello!
> >
> > I don't see why we can't get rid of autotools in a minor release,
> provided
> > that cmake actually works. Removing native VS support may be a different
> > thing.
> >
> > Build system and precise set of dependencies is not a part of public API
> in
> > my opinion.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > вт, 26 мая 2020 г. в 16:02, Igor Sapego :
> >
> >> 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 :
> >>>
>  +1
> 
>  On Tue, May 26, 2020 at 12:02 PM Zhenya Stanilovsky
>   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

Re: [DISCUSSION] Ignite.C++ and CMake

[Nikolay Izhikov]

Hello, Igor.

> Nikolay, removing support for a certain build system is a breaking change.

No, it’s not.
Why do you think so?

Development environment and build system is a subject to change in any project.
We can drop or add support of any build system any time we want.

> 26 мая 2020 г., в 16:35, Ilya Kasnacheev  
> написал(а):
> 
> Hello!
> 
> I don't see why we can't get rid of autotools in a minor release, provided
> that cmake actually works. Removing native VS support may be a different
> thing.
> 
> Build system and precise set of dependencies is not a part of public API in
> my opinion.
> 
> Regards,
> -- 
> Ilya Kasnacheev
> 
> 
> вт, 26 мая 2020 г. в 16:02, Igor Sapego :
> 
>> 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 :
>>> 
 +1
 
 On Tue, May 26, 2020 at 12:02 PM Zhenya Stanilovsky
  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
>>> 
>> 

Re: [DISCUSSION] Ignite.C++ and CMake

[Ilya Kasnacheev]

Hello!

I don't see why we can't get rid of autotools in a minor release, provided
that cmake actually works. Removing native VS support may be a different
thing.

Build system and precise set of dependencies is not a part of public API in
my opinion.

Regards,
-- 
Ilya Kasnacheev


вт, 26 мая 2020 г. в 16:02, Igor Sapego :

> 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 :
> >
> > > +1
> > >
> > > On Tue, May 26, 2020 at 12:02 PM Zhenya Stanilovsky
> > >  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
> >
>

Re: [DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinsky]

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 :

> 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 
> 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 :
> > >>
> > >>> +1
> > >>>
> > >>> On Tue, May 26, 2020 at 12:02 PM Zhenya Stanilovsky
> > >>>  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

Re: [DISCUSSION] Ignite.C++ and CMake

[Igor Sapego]

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 
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 :
> >>
> >>> +1
> >>>
> >>> On Tue, May 26, 2020 at 12:02 PM Zhenya Stanilovsky
> >>>  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
> >>
>

Re: [DISCUSSION] Ignite.C++ and CMake

[Nikolay Izhikov]

Hello, Igor.

I’m ++1 for this change.

How build system relates to major version of product?
I think we can change the way we build modules any time we want.


> 26 мая 2020 г., в 16:02, Igor Sapego  написал(а):
> 
> 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 
> 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 :
>> 
>>> +1
>>> 
>>> On Tue, May 26, 2020 at 12:02 PM Zhenya Stanilovsky
>>>  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
>> 

Re: [DISCUSSION] Ignite.C++ and CMake

[Igor Sapego]

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 
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 :
>
> > +1
> >
> > On Tue, May 26, 2020 at 12:02 PM Zhenya Stanilovsky
> >  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
>

Re: [DISCUSSION] Ignite.C++ and CMake

[Alexey Kukushkin]

+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 :

> +1
>
> On Tue, May 26, 2020 at 12:02 PM Zhenya Stanilovsky
>  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

Re: [DISCUSSION] Ignite.C++ and CMake

[Pavel Tupitsyn]

+1

On Tue, May 26, 2020 at 12:02 PM Zhenya Stanilovsky
 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
> >
> >
> >
>
>
>
>

Re: [DISCUSSION] Ignite.C++ and CMake

[Zhenya Stanilovsky]

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
>
>
>  
 
 
 
 

[DISCUSSION] Ignite.C++ and CMake

[Ivan Daschinskiy]

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