[
https://issues.apache.org/jira/browse/IGNITE-10940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114752#comment-17114752
]
Ivan Daschinskiy commented on IGNITE-10940:
-------------------------------------------
Absolutelly agree with [~alex_pl]
First of all in order to build Ignite.C++ one should install libboost-dev,
libssl-dev, g++, build-essentials, optionally unixodbc-dev. And (I hardly
believe that C++ developer doesn't have them installed already) just add to
this list autotools and libtool is not a big problem.
I suppose, that the right direction is migrating to cmake and C++ 11. But this
patch just adds problems, but not solve the root cause -- Ignite C++ should be
modernized.
> 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, platforms
> Reporter: Ilya Kasnacheev
> Assignee: Ilya Kasnacheev
> Priority: Major
> Labels: c++
> Fix For: 2.9
>
>
> 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)
