lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1025348 - in /websites/staging/lucene/trunk/content: ./ pylucene/jcc/install.html
Date Tue, 13 Feb 2018 20:03:59 GMT
Author: buildbot
Date: Tue Feb 13 20:03:59 2018
New Revision: 1025348

Log:
Staging update by buildbot for lucene

Modified:
    websites/staging/lucene/trunk/content/   (props changed)
    websites/staging/lucene/trunk/content/pylucene/jcc/install.html

Propchange: websites/staging/lucene/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 13 20:03:59 2018
@@ -1 +1 @@
-1823661
+1824170

Modified: websites/staging/lucene/trunk/content/pylucene/jcc/install.html
==============================================================================
--- websites/staging/lucene/trunk/content/pylucene/jcc/install.html (original)
+++ websites/staging/lucene/trunk/content/pylucene/jcc/install.html Tue Feb 13 20:03:59 2018
@@ -161,19 +161,29 @@ APIs to do its work. It is built and ins
 via <i>distutils</i>
 or <a href="http://pypi.python.org/pypi/setuptools">setuptools</a>.</p>
 <ul>
-<li>Edit <i>setup.py</i> and review that values in
-the <i>INCLUDES</i>, <i>CFLAGS</i>,
-<i>DEBUG_CFLAGS</i>, <i>LFLAGS</i>
-and <i>JAVAC</i> are correct for your system. These values
-are also going to be compiled into JCC's <i>config.py</i>
-file and are going to be used by JCC when
-invoking <i>distutils</i> or <i>setuptools</i> to
-compile extensions it is generating code for.</li>
-<li>At the command line, enter:
+<li>
+<p>On Mac OS X and Windows, <i>setup.py</i> will attempt to find a JDK
on your
+system and report what it found by showing the values for <i>JAVAHOME</i> and
+<i>JAVAFRAMEWORKS</i> it was able to derive. If the JDK installation that was
+found is not the one you wish to use or if you are not on Mac OS X or Windows,
+you can either edit <i>setup.py</i> and review that the values in the
+<i>INCLUDES</i>, <i>CFLAGS</i>, <i>DEBUG_CFLAGS</i>,
<i>LFLAGS</i>,
+<i>JAVAC</i>, and <i>JAVADOC</i> dicts are correct for your system
or set
+<b>all</b> of the following environment variables, <i>JCC_JDK</i>,
+<i>JCC_INCLUDES</i>, <i>JCC_CFLAGS</i>, <i>JCC_DEBUG_CFLAGS</i>,
+<i>JCC_LFLAGS</i>, <i>JCC_JAVAC</i> and <i>JCC_JAVADOC</i>,
using os.pathsep
+as value separator to override them.
+The values hereby configured are going to be compiled into JCC's
+<i>config.py</i> file and are going to be used by JCC when invoking
+<i>setuptools</i> to compile the extensions it is going to generate code for.</p>
+</li>
+<li>
+<p>At the command line, enter:
 <code>
 $ python setup.py build<br/>
 $ sudo python setup.py install<br/>
-</code></li>
+</code></p>
+</li>
 </ul>
 <h2 id="requirements">Requirements<a class="headerlink" href="#requirements" title="Permanent
link">&para;</a></h2>
 <p>JCC requires a Java Development Kit to be present. It uses the Java
@@ -190,14 +200,13 @@ extension is going to be imported into a
 <p>Shared mode depends on <i>setuptools</i>' capability of
 building plain shared libraries (as opposed to shared libraries for
 Python extensions).</p>
-<p>Currently, shared mode is supported with <i>setuptools
-0.6c7</i> and above out of the box on macOS and Windows. On
-Linux, a patch to <i>setuptools</i> needs to be applied
-first. This patch is included in the JCC source distribution in
-the <i>jcc/patches</i> directory, <i>patch.43</i>. This
-patch was submitted to the <i>setuptools</i> project
-via <a href="http://bugs.python.org/setuptools/issue43">issue
-43</a>.</p>
+<p>Currently, shared mode is supported with <i>setuptools 0.6c7</i> and
above out
+of the box on MacOSX and Windows. On Linux, a patch to <i>setuptools</i> needs
+to be applied first. This patch is included in the JCC source distribution in
+the <i>jcc2/patches</i> directory, <i>patch.43</i>. This patch was
submitted
+to the <i>setuptools</i> project via <a
+href="http://bugs.python.org/setuptools/issue43">issue 43</a>.
+<i>setup.py</i> will attempt to apply the patch for you via monkeypatching.</p>
 <p>The <i>shared mode disabled</i> error reported during the
 build of JCC's on Linux contains the exact instructions on how to
 patch the <i>setuptools</i> installation
@@ -222,7 +231,7 @@ the <i>NO_SHARED</i> environment variabl
 <p>Is JCC built with shared mode support or not ?</p>
 <ul>
 <li>
-<p>By default, on macOS, Linux or Windows, this is the case when using a
+<p>By default, on MacOSX, Linux or Windows, this is the case when using a
   modern version of <i>setuptools</i></p>
 </li>
 <li>
@@ -239,13 +248,13 @@ the <i>NO_SHARED</i> environment variabl
     the <i>--shared</i> command line argument.</p>
 </li>
 </ul>
-<h2 id="notes-for-mac-macos">Notes for Mac macOS<a class="headerlink" href="#notes-for-mac-macos"
title="Permanent link">&para;</a></h2>
-<p>On macOS, Java is installed by Apple's setup as a framework. The
+<h2 id="notes-for-macosx">Notes for MacOSX<a class="headerlink" href="#notes-for-macosx"
title="Permanent link">&para;</a></h2>
+<p>On MacOSX, Java is installed by Apple's setup as a framework. The
 values in <i>setup.py</i> for <i>INCLUDES</i>
 and <i>LFLAGS</i> for <i>darwin</i> should be correct
 and ready to use.</p>
 <p>However, if you intend to use the 'system' Python from a Java VM
-  on macOS -- Python embedded in Java --
+  on MacOSX -- Python embedded in Java --
   you will need to add the flags <i>"-framework", "Python"</i>
   to the <i>LFLAGS</i> value.</p>
 <h2 id="notes-for-linux">Notes for Linux<a class="headerlink" href="#notes-for-linux"
title="Permanent link">&para;</a></h2>



Mime
View raw message