I am not sure I agree with setting this at build time: a jvm could be
installed afterwards and/or updated independently of sage
S.
* Michael Orlitzky
<mich...@orlitzky.com> [2019-11-04 08:49:18]:
On 11/3/19 4:55 PM, VulK wrote:
On the same note: the current implementation of `is_jvm_available` is not
really robust and I should open a ticket about this; any suggestion for a
better implementation?
S.
const false
Does it do anything except jmol? The right way to do it would be to add
--with-jvm=/path/to/jvm or something like that to the ./configure
script. The is_jvm_available() implementation would then be hard-coded
at build time, and not enabled automagically. But that's a lot of work a
a feature that no one's going to use after jmol is replaced.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/e01aeb45-7170-ef2e-9f0b-77f5c8301a5b%40orlitzky.com.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/20191105101851.GA15686%40strabo.