forked from apache/ignite
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.txt
85 lines (68 loc) · 3.34 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
Apache Ignite C++
==================================
Apache Ignite C++ provides data grid functionality.
Using Apache Ignite C++ APIs you can perform concurrent operations on
the data stored in cache.
Apache Ignite C++ can access cluster and share data with .Net and
Java applications using binary object format.
Support for the following will be added in next releases:
* ACID transactions management.
* Distributed locks.
* Asynchronous operations.
* Cache SQL continuous queries.
* Event listening.
* Compute grid functionality.
Full source code is provided. Users should build the library for intended platform.
For build instructions please refer to DEVNOTES.txt.
For details on ODBC driver installation and usage please refer to
$IGNITE_HOME/platforms/cpp/odbc/README.txt.
Linux info
==============
Files list:
* ignite - executable to start standalone Ignite C++ node.
* libignite.so - Ignite C++ API library.
* libignite-odbc.so - Ignite ODBC driver.
* libignite-thin-client.so - Ignite C++ thin client library.
Development:
* IGNITE_HOME environment variable must be set to Ignite installation directory.
* Once both libraries are built and installed, required headers are placed in the
"/usr/local/include/ignite" directory.
* Apache Ignite C++ depends on jni.h file located inside ${JAVA_HOME}/include directory.
Add this directory to headers search path: "-I${JAVA_HOME}/include".
* Library is placed in the "/usr/local/lib" directory. Link it to your project: "-lignite".
* Ignite depends on "libjvm.so" library shipped with Java. Typically this library is
located inside $JAVA_HOME/jre/lib/amd64/server directory. Ensure that LD_LIBRARY_PATH
environment variable points to this directory.
* To start Apache Ignite as a standalone node use "ignite" binary.
Windows info
===============
Files list:
* ignite.exe - executable to start standalone Ignite C++ node.
* ignite.core.dll - Ignite C++ API library.
* ignite.odbc.dll - Ignite ODBC driver.
* ignite.thin-client.dll - Ignite thin C++ client.
Development:
* IGNITE_HOME environment variable must be set to Ignite installation directory.
* Update Include Directories in Project Properties with paths to:
* $(IGNITE_HOME)\platforms\cpp\common\include
* $(IGNITE_HOME)\platforms\cpp\common\os\win\include
* $(IGNITE_HOME)\platforms\cpp\jni\include
* $(IGNITE_HOME)\platforms\cpp\jni\os\win\include
* $(IGNITE_HOME)\platforms\cpp\binary\include
* $(IGNITE_HOME)\platforms\cpp\core\include to use thick client
* $(IGNITE_HOME)\platforms\cpp\thin-client\include to use thin client
* $(JAVA_HOME)\include
* $(JAVA_HOME)\include\win32
* Update Library Directories with path to the built binaries
* Update Linker\Input\Additional Dependencies in Project Properties with path to
* ignite.common.lib
* ignite.binary.lib
* ignite.jni.lib to use thick client
* ignite.core.lib to use thick client
* ignite.network.lib to use thin client
* ignite.thin-client.lib to use thin client
* Make sure that your application is aware about ignite.jni.dll and ignite.core.dll or
ignite.thin-client.dll libraries. The easiest way to achieve this is to either make
sure these files are in %PATH%, or to put them into the output directory of your
project with help of PostBuild events.
* To start Apache Ignite as a standalone node or Windows service use ignite.exe