[
https://issues.apache.org/jira/browse/IGNITE-10940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev reassigned IGNITE-10940:
----------------------------------------
Fix Version/s: 2.8.1
Assignee: Ilya Kasnacheev
Let's fix it! [~nizhikov] can you please review?
https://ci.ignite.apache.org/buildConfiguration/Releases_NightlyRelease_ApacheIgniteNightlyReleaseAssembleBinaries/5233102?buildTab=artifacts
- you can download a binary release here, where in platforms/cpp ./configure
works out of box and make just builds it.
[~isapego] please review my changes
https://github.com/apache/ignite/compare/ignite-10940
> 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)
