Andi Vajda commented on PYLUCENE-40:

Note, that, as the code is currently, if you *only* set JCC_JDK and not 
JCC_INCLUDES, etc..., then it will use the values derived from the found 

If you want to set your own JCC_JDK, you must also set the other JCC_ env vars 
that depend on it, or else you'll be building with the wrong version header 
files and libraries. See line 176 in setup.py where these are set (and later 
where they're used).

> Document use of JCC_JDK
> -----------------------
>                 Key: PYLUCENE-40
>                 URL: https://issues.apache.org/jira/browse/PYLUCENE-40
>             Project: PyLucene
>          Issue Type: Improvement
>            Reporter: Ryan J Ollos
>            Priority: Minor
>         Attachments: jcc_build_output.txt
> I found two issues when trying to [help someone on Stack 
> Overflow|https://stackoverflow.com/questions/48711714/] build the library. 
> First, the [documentation on PyPI|https://pypi.python.org/pypi/JCC/] states:
> {quote}JCC’s setup.py file needs to be edited before building JCC to specify 
> the location of the Java Runtime Environment’s header files and libraries.
> {quote}
> However, it appears you have a better mechanism of setting {{JCC_JRE}}, but 
> it's not documented.
> Second, when setting {{JCC_JRE}} is appears to work correctly and use the 
> path to the specified {{JCC_JRE}} in the compilation, but the first line of 
> output might indicate that a different JRE is being used:
> {code:java}
> $JCC_JDK=/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home 
> python setup.py install
> found JAVAHOME = 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_141.jdk/Contents/Home
> found JAVAFRAMEWORKS = /System/Library/Frameworks/JavaVM.framework
> ...
> {code}
> So maybe the found {{JAVAHOME}} should not be printed if {{JCC_JRE}} is set, 
> so it appears that {{JCC_JRE}} is successfully overriding the {{JAVAHOME}}. 
> I'll attach the full output from building on my platform.

This message was sent by Atlassian JIRA

Reply via email to