|
From: | Mike Miller |
Subject: | [Octave-bug-tracker] [bug #47480] [octave forge] (io) relies on deprecated octave_config_info |
Date: | Sun, 6 Jan 2019 17:14:37 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 |
Follow-up Comment #7, bug #47480 (project octave): Philip - it would be helpful if you could explain the logic that you need in the io package and what Octave could provide. I don't really understand the differences with all of the possibilities of Java and LibreOffice 32/64 bit support on Windows that you are selecting. Can you explain why the value of computer("arch") or uname().machine is not sufficient? That should help eliminate the need for "ENABLE_64". You should be able to eliminate all uses of octave_config_info("build_features").JAVA and have_feature("JAVA") immediately, I can provide a patch if you want. I guess you expect that jar files will be dropped into the Octave library directory on Windows? Or is that an old assumption that can be dropped? _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?47480> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |