Mailing-List: contact pylucene-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: pylucene-dev@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of techgurufloyd@gmail.com
 designates 209.85.198.229 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=Dti1YifleNyKSdg4CNjRajqUZqwrbf6xgoP7uSCt8GZj1JJNYs535BJ2tXsJkb2Tuv
         HalvCKcj9sxqaVG8BU+wuwswpBdNi2z6JzHCPvA1VfVUEO41U8Y4KYnCn9bopvaOZdlx
         7TLczrKUJDvKYTn2ThbXJdbPY7vWpI2APUNrw=
MIME-Version: 1.0
Date: Fri, 20 Feb 2009 18:05:23 -0700
Message-ID: <4afbebfe0902201705o5b1e68e8r669e10c491f0f008@mail.gmail.com>
Subject: JCC Install
From: Jacob Floyd <techgurufloyd@gmail.com>
To: pylucene-dev@lucene.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Here I am again.
After talking with some of the gentoo devs, they suggested I modify
the setup.py to include gentoo specifics and send it upstream. As it
is, they don't like to have to specify all the lflags, and in fact it
becomes troublesome, because we'd then have to duplicate what you're
doing (sniffing for x86/x86_x86_64...) within the ebuild. Instead, it
would be nicer to have something like a JCC_JAVA_DIR, that specifies
where the java install is, and then use that within Includes and
lflags. In my case I would then set not the JCC_LFLAGS variable but
the JCC_JAVA_DIR, and the setup.py would automatically give me either
i386/i686/x86_64.

I don't know if you prefer a copy or a patch, and I don't know if I
can attach things going to the list, so here's the setup.py and the
diff (available for the next 30 days):
setup.py http://dpaste.com/123231/
setup.py.diff http://dpaste.com/123234/
Note that I moved some of the variables up or down, to keep it simple
for users to change just what they need.

What do you think?

Thanks,
Jacob