Hi Erik,
On Fri, 30 Jul 2021, Erik Groeneveld - Seecr wrote:
Hi Andy,
Thanks for your answer. I can now formulate my question.
We use at least 3 extensions generated by JCC and we use shared mode.
Thus, you need shared mode.
My actual question is.
Why does JCC generate extensions that
Hi Andy,
Thanks for your answer. I can now formulate my question.
We use at least 3 extensions generated by JCC and we use shared mode.
My actual question is.
Why does JCC generate extensions that use the shared library
“libjcc3.so, while all that is needed is also in jcc/_
jcc3.cpython-37m-x86
> On Jul 29, 2021, at 14:51, Erik Groeneveld - Seecr wrote:
>
> L.S.,
>
> We make Debian packages for JCC and PyLucene.
>
> When building debug extensions for JCC and Lucene, we run into the problem
> that JCC links the generated extension against libjcc3.so.
That is the case if you use 'sh
L.S.,
We make Debian packages for JCC and PyLucene.
When building debug extensions for JCC and Lucene, we run into the problem
that JCC links the generated extension against libjcc3.so.
However, libjcc3.so defines Python objects and because the Python object
header defines additional fields in D
