[
https://issues.apache.org/jira/browse/IGNITE-10940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17115997#comment-17115997
]
Ilya Kasnacheev commented on IGNITE-10940:
------------------------------------------
I don't see why you are supposed to build release bundles of Apache Ignite on
anything other than Linux. Do you do that often? I think we can make this step
skippable if it becomes a problem [~alex_pl]
It is not customary for projects containing autotools to expose them end-user.
I can't name one C or C++ project which ships no `configure' in their release
bundles. The remaining dependencies is another question. [~ivandasch]
I am offended by your "it's too hard for us developers, but users can do it
easily" attitude. You can always discuss this on developers list, but other
than that, I think this feature stays put.
> 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)
