[jira] [Created] (IGNITE-10940) Supply pre-built ./configure with Apache Ignite releases

["Ilya Kasnacheev (JIRA)" <ji...@apache.org>]

Ilya Kasnacheev created IGNITE-10940:
----------------------------------------

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


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
(v7.6.3#76005)