On Feb 23, 2009, at 10:06, Jacob Floyd wrote:
I added a 'JDK' dict variable to setup.py that contains the root of
the jdk
installation for each platform. I then replaced all hard coded
occurrences
of that directory in the INCLUDES and LFLAGS dicts.
If a JCC_JDK env variable is set it sup
>
> I added a 'JDK' dict variable to setup.py that contains the root of the jdk
> installation for each platform. I then replaced all hard coded occurrences
> of that directory in the INCLUDES and LFLAGS dicts.
> If a JCC_JDK env variable is set it supercedes the value in setup.py for
> your platfo
On Sun, 22 Feb 2009, Andi Vajda wrote:
Thank you for the patch.
This is the second time in a week that someone suggest the same thing: a
variable to specify the JDK root (JAVA_HOME or somesuch).
I'll take the ideas from both patches and incorporate that into JCC's
setup.py.
I added a 'JDK'
> Getting annoyed with having to modify setup.py myself and needing a
> way to build JCC that didn't involve editing the file, I added a long
> time ago the possibility to set all these flags via environment
> variables (as you noticed). I then do the right thing, once, in the
> Makefile driving my
On Fri, 20 Feb 2009, Jacob Floyd wrote:
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
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
