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

["Aleksey Plekhanov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-10940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114690#comment-17114690 ] 

Aleksey Plekhanov commented on IGNITE-10940:
--------------------------------------------

[~ilyak], the patch adds external dependencies to some libraries which are not preinstalled on some systems (at least MacOS and Windows). It makes release process platform dependent. Before the patch to build Ignite all you needed is maven, which downloads all other dependencies, but now you need to download and install libtool, which is not related at all to java development. For a small part of C++ users we broke the build for another, much larger part of users. Moreover, there are no notes about it on DEVNOTES. Java contributors will try to build the project by {{mvn initialize -Prelease}} command and build will fail. I think such a feature should be at least optional, and perhaps disabled by default with a description in  DEVNOTES about how to enable it. 

Another question, why such a change not discussed on dev-list? 

> 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)