|
From: | Philip Nienhuis |
Subject: | [Octave-bug-tracker] [bug #47480] [octave forge] (io) relies on deprecated octave_config_info |
Date: | Mon, 7 Jan 2019 05:58:20 -0500 (EST) |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48 |
Follow-up Comment #9, bug #47480 (project octave): I had a brief look in __init_io__.m and yes it's a tad more complicated than I initially remembered. It's slowly coming back :-) The following calls to __octave_config_info__ exist in __init__io.m : * ('build_features').JAVA - needed to know if Java support was built into Octave * libdir - where are libraries situated. Not so much for MingW but also for some Linux distros; maybe sometime in the future for Octave as well if ever some spreadsheet I/O would move to core * ENABLE_64 - ( IIRC) needed to avoid 64-bit Octave find & try to invoke 32-bit LO as that might crash Octave. The other way round was more robust IIRC. I once had 32-bit and 64-bit Octave and 32-bit and 64-bit LO or OOo installations on the same box (admittedly a weird but not impossible scenario), IIRC on Linux and Windows. Later this week I'll come back to it, I really have to do Real work now. _______________________________________________________ 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] |