Igniters!
Currently we have CMake build system, that works on Windows, Linux and
MacOs flawlessly
1. CMake is supported natively in VS 2019
2. CMake can generate VS projects for about 20 years flawlessly.
3. Sometimes even maintainers forget to add test sources to VS projects [1]
4. Currently on
completely support !
>Igniters!
>
>Currently we have CMake build system, that works on Windows, Linux and
>MacOs flawlessly
>
>1. CMake is supported natively in VS 2019
>2. CMake can generate VS projects for about 20 years flawlessly.
>3. Sometimes even maintainers forget to add test sources to
-1
This may become an obstacle for some of the users and I'm not sure how it
improves anything.
> 3. Sometimes even maintainers forget to add test sources to VS projects
[1]
We can add an automatic check for this (in form of a test).
On Wed, Sep 15, 2021 at 10:28 AM Zhenya Stanilovsky
wrote:
>
+1
> 15 сент. 2021 г., в 11:57, Pavel Tupitsyn написал(а):
>
> -1
>
> This may become an obstacle for some of the users and I'm not sure how it
> improves anything.
>
>> 3. Sometimes even maintainers forget to add test sources to VS projects
> [1]
> We can add an automatic check for this (in f
+1 for removing VS project
2021-09-15 12:01 GMT+03:00, Nikolay Izhikov :
> +1
>
>> 15 сент. 2021 г., в 11:57, Pavel Tupitsyn
>> написал(а):
>>
>> -1
>>
>> This may become an obstacle for some of the users and I'm not sure how it
>> improves anything.
>>
>>> 3. Sometimes even maintainers forget to
+1
Let's keep the project clean and on the verge of preferable tech stack.
> On 15 Sep 2021, at 12:02, Ivan Pavlukhin wrote:
>
> +1 for removing VS project
>
> 2021-09-15 12:01 GMT+03:00, Nikolay Izhikov :
>> +1
>>
>>> 15 сент. 2021 г., в 11:57, Pavel Tupitsyn
>>> написал(а):
>>>
>>> -1
>>
>> This may become an obstacle for some of the users and I'm not sure how
it improves anything.
Please specify more correctly. What is an obstacle? Current VS projects
(odbc) cannot be build on VC 2015+
without modification. CMake is an industry standard now.
>> I'm not sure how it improves anythin
+1
Checked sha512 and sign of archives, built from sources, started a cluster
with a few nodes.
вт, 14 сент. 2021 г. в 21:23, Pavel Tupitsyn :
> Ilya,
>
> > I'm still confused by this publish/ directory. Why are we shipping
> > something which is not for publishing in our binary package? I've al
>> Please specify more correctly.
Sorry, typo, more concretely.
ср, 15 сент. 2021 г. в 12:22, Ivan Daschinsky :
> >> This may become an obstacle for some of the users and I'm not sure how
> it improves anything.
> Please specify more correctly. What is an obstacle? Current VS projects
> (odbc) ca
> It makes development much more easier.
How?
> I can hardly imagine how it can be done
1. Get all files in the directory
2. Filter by TestSuite suffix
3. Check if all of them are present in VS files
Am I missing something? We have checks like this for Ignite.NET [1]
[1]
https://github.com/apac
> How?
Currently user must add sources in 2 different places. One of this places
is not specified and not intended to be edit outside VC.
CMake can generate VS projects easily and without any problem. I've done
this even in 2008 when I was C++/Qt developer.
>> 1. Get all files in the directory
>>
>> Currently user
Sorry typo, I meant developer.
ср, 15 сент. 2021 г. в 12:35, Ivan Daschinsky :
> > How?
> Currently user must add sources in 2 different places. One of this places
> is not specified and not intended to be edit outside VC.
> CMake can generate VS projects easily and without any
Ivan,
Ok, I've got your point.
What's your assessment on the following:
1. What percentage of our users rely on existing VS projects?
2. How much time (in minutes) does it take to switch from using existing VS
projects to CMake-generated ones?
On Wed, Sep 15, 2021 at 12:37 PM Ivan Daschinsky
>> 1. What percentage of our users rely on existing VS projects?
It is impossible to answer, but I suppose not so much. And, again, these
projects needs some tweaks in order to work properly in VS 2015+
Moreover, you cannot use VS as is, you should tweak them or download
dependencies in specific lo
Ivan, thanks for the answers! I retract my "-1". No objections.
On Wed, Sep 15, 2021 at 12:58 PM Ivan Daschinsky
wrote:
> >> 1. What percentage of our users rely on existing VS projects?
> It is impossible to answer, but I suppose not so much. And, again, these
> projects needs some tweaks in or
+1 (binding)
> 15 сент. 2021 г., в 12:24, Alex Plehanov написал(а):
>
> +1
>
> Checked sha512 and sign of archives, built from sources, started a cluster
> with a few nodes.
>
> вт, 14 сент. 2021 г. в 21:23, Pavel Tupitsyn :
>
>> Ilya,
>>
>>> I'm still confused by this publish/ directory. Wh
A new feedback has been added, go to bugyard.io to see all the details...
https://bugyard.io
A new feedback has been added
"this procedure is not working, also the following item is not completed 3.c
" by ibrahim.altun
View feedback
https://app.bugyard.io/web/app/rycqZJDyY/f/6141f7cb8d3cd7
Hi, Petr!
I closed the ticket, Anton Vinogradov (thanks!) helped me and created the
suite fast. It successfully ran.
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_IndexQuery?mode=branches
On Tue, Sep 14, 2021 at 6:13 PM Maksim Timonin
wrote:
> Hi, Petr!
>
> Thanks for the
Actually, Index Query API suite is not part of RunAll.
Let's fix this.
On Wed, Sep 15, 2021 at 5:12 PM Maksim Timonin
wrote:
> Hi, Petr!
>
> I closed the ticket, Anton Vinogradov (thanks!) helped me and created the
> suite fast. It successfully ran.
>
>
> https://ci.ignite.apache.org/buildConfi
It has not to be before merge. After merge we will add it to RunAll.
On Wed, Sep 15, 2021 at 5:25 PM Andrey Mashenkov
wrote:
> Actually, Index Query API suite is not part of RunAll.
> Let's fix this.
>
> On Wed, Sep 15, 2021 at 5:12 PM Maksim Timonin
> wrote:
>
> > Hi, Petr!
> >
> > I closed t
+0.5 From me
1.ubuntu 20.04 gcc9.3.0 oracle jdk 1.8.0_281 cmake 3.16
a. build from source -- passed
b. run examples -- passed
2. windows 10 x86_64 visual studio 2017 cmake 3.21
a. build from source using cmake --passed
b. build odbc driver using cmake -- passed
c. run examples -- passed
Installin
Ok, found issue -- need to install VC++ 2010 redistributable package.
Currently, it is not available on windows 10.
I suppose, that this is a blocker.
ср, 15 сент. 2021 г. в 20:07, Ivan Daschinsky :
> +0.5 From me
> 1.ubuntu 20.04 gcc9.3.0 oracle jdk 1.8.0_281 cmake 3.16
> a. build from source --
>> Currently, it is not available on windows 10.
I mean that it is impossible to download this redist package from official
site, it was removed.
It is weird to make user search this on suspicious sites over the internet.
The main issue that we still build C++ packages on TC using Visual
Studion 2
Ivan,
Can you please clarify in detail what exactly should be fixed? I'm not
familiar with running something from Ignite under the Windows
environment. It's weird if something is not available on the official
site, however available on mirrors. It's not good but not a crime but
doesn't sound like
>> Can you please clarify in detail what exactly should be fixed?
Sure. The ODBC driver is a native shared library, it depends on C++
runtime.
We ship one builded using Visual C++ 2010, so runtime libraries should be
installed first.
These runtime libraries are usually shipped in so called redistri
So +1 for me, checked all C++ and ODBC drivers on ubuntu 20.04 and windows
10 x86_64
чт, 16 сент. 2021 г. в 09:35, Ivan Daschinsky :
> >> Can you please clarify in detail what exactly should be fixed?
> Sure. The ODBC driver is a native shared library, it depends on C++
> runtime.
> We ship one b
Hello, Igniters!
Release pyignite-0.5.2-rc0 has been accepted
The votes received:
3 "+1" binding votes
3 "+1" votes
There is neither "+0" nor "-1"
Here the votes received:
- +1 Pavel Tupitsyn (binding)
- +1 Nickolay Izhikov (binding)
- +1 Maxim Muzafarov (binding)
- +1 Ilya Shishkov
- +1 Aleksa
27 matches
Mail list logo
