You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Bastien Durel (Jira)" <ji...@apache.org> on 2020/05/07 10:44:00 UTC
[jira] [Created] (IGNITE-12988) c++ thin client installer misses
some headers
Bastien Durel created IGNITE-12988:
--------------------------------------
Summary: c++ thin client installer misses some headers
Key: IGNITE-12988
URL: https://issues.apache.org/jira/browse/IGNITE-12988
Project: Ignite
Issue Type: Bug
Components: build, examples, thin client
Affects Versions: 2.8
Reporter: Bastien Durel
Hello,
After building and installing (with make install) the c++ module for ignite, some header files are missing, so the most simple example cannot compile :
{code:java}
make: Entering directory '/home/bastien/project/webix/cpp'
g++ -I/usr/local/include -c -o data.o data.cpp
In file included from /usr/local/include/ignite/impl/binary/binary_writer_impl.h:32,
from /usr/local/include/ignite/binary/binary_raw_writer.h:30,
from /usr/local/include/ignite/impl/thin/writable.h:21,
from /usr/local/include/ignite/thin/cache/cache_client.h:28,
from /usr/local/include/ignite/thin/ignite_client.h:31,
from data.cpp:3:
/usr/local/include/ignite/impl/binary/binary_utils.h:30:10: fatal error: ignite/binary/binary_enum_entry.h: No such file or directory
30 | #include <ignite/binary/binary_enum_entry.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make: *** [<builtin>: data.o] Error 1
{code}
To make the first thin client example compile, I had to manually copy `binary_enum_entry.h` and `binary_enum.h` to /usr/local/include/ignite/binary/
Using the deb file from [http://apache.org/dist/ignite/deb/] leads to the same results.
While trying to compile a non-thin client, I ran into a similar issue with <ignite/jni/utils.h> which is not installed, but I did not push this way.
By the way, the examples on [https://apacheignite-cpp.readme.io/docs/thin-client] reffers to a non-existant include file : <ignite/thin/cache/ignite_client.h>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)