[
https://issues.apache.org/jira/browse/IGNITE-10940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16743085#comment-16743085
]
Igor Sapego commented on IGNITE-10940:
--------------------------------------
[~ilyak],
I totally support this initiative.
[~vveider],
It will not work on our Windows agents, if that's was what you were asking, so
this step only should be performed on Unix-like agents.
If you mean generated ./configure script - than no, it is platform-independent.
Actually, its purpose is to create Makefile for any platform.
> 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
> Priority: Major
> Labels: c++
>
> 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)
