[
https://issues.apache.org/jira/browse/IGNITE-10940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088122#comment-17088122
]
Ilya Kasnacheev commented on IGNITE-10940:
------------------------------------------
It is an improvement to release procedures. I think that improving release
procedures is a thing to do in patch releases, since major releases have too
much stuff anyway and people have zero interest in improving release procedures
when there is no release.
This is why I suggest we put IGNITE-10940 and IGNITE-12765 inti 2.8.1 or maybe
2.8.2
> Supply pre-built ./configure with Apache Ignite releases
> --------------------------------------------------------
>
> Key: IGNITE-10940
> URL: https://issues.apache.org/jira/browse/IGNITE-10940
> Project: Ignite
> Issue Type: Improvement
> Components: build
> Reporter: Ilya Kasnacheev
> Assignee: Ilya Kasnacheev
> Priority: Major
> Labels: c++
> Fix For: 2.8.1
>
>
> Right now we have the following build steps for C++ in docs:
> {code}
> cd modules/platforms/cpp
> libtoolize && aclocal && autoheader && automake --add-missing && autoreconf
> ./configure
> make
> sudo make install
> {code}
> However, it is customary for C++ projects to ship release tarballs with first
> step already done. ./configure should be pre-built and libtoolize, etc, are
> already ran since you should not force user to install them, and the process
> of their application is deterministic.
> I suggest we add libtoolize && etc step to release builds so that user's
> first step will be ./configure.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
