[
https://issues.apache.org/jira/browse/IGNITE-10940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17086542#comment-17086542
]
Ilya Kasnacheev commented on IGNITE-10940:
------------------------------------------
[~nizhikov]
I think there's VS solution there.
On Linux, just hit ./configure and then make. If it built without errors, it's
fine. <-- this is for builds of this feature branch
To run,
LD_LIBRARY_PATH=/path/to/Downloads/jdk-12.0.1/lib/server:$LD_LIBRARY_PATH
ignite/ignite
Not sure about tests, I never run them, but since I have changed no C++ code it
should be OK.
> 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)
