|
From: | Mike Miller |
Subject: | [Octave-bug-tracker] [bug #54260] mkoctfile doesn't export some Octave features that packages need at build time |
Date: | Fri, 6 Jul 2018 15:04:21 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0 |
Follow-up Comment #4, bug #54260 (project octave): I don't think Octave needs to provide a .m4 file as a service to other packages. I think it's fine if we say that packages that use HDF5 to interface with Octave just need to detect it on their own. Both PCRE and HDF5 have pkg-config files these days, there is no need for Octave to provide autoconf logic for those libraries. I'm fine with changing the communications package to find HDF5 on its own, and PCRE should be easy as well for the strings package. Let's just add the bare minimum that we need to mkoctfile to make it equivalent to what people actually use from octave-config. That does include the various "DIR" variables like LOCALFCNFILEDIR and LOCALOCTFILEDIR. VERSION and CANONICAL_HOST_TYPE would also be nice to add. OCTINCLUDEDIR is already available with mkoctfile, so gsl can start using that today. And something to easily indicate whether octave_idx_type is a 32 or 64 bit integer. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?54260> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |