view .hgignore @ 19897:09ed6f7538dd

avoid needing to include hdf5 in public header files (bug #44370, #43180) * oct-hdf5-id.cc, oct-hdf5-id.h: New files. * libinterp/corefcn/module.mk: Update. * libgui/src/module.mk (src_libgui_src_la_CPPFLAGS): Remove $(HDF5_CPPFLAGS) from the list. * load-save.h (enum load_save_format_type): Always include LS_HDF5 in the list of values. * ls-hdf5.cc (read_hdf5_data, save_hdf5_data): Call check_hdf5_id_type. * oct-hdf5.h: Also #define HDF5_SAVE_TYPE. * ov.h, ov-base.h: Include oct-hdf5-id.h instead of oct-hdf5.h. Always declare load_hdf5 and save_hdf5 functions. * ov-base-int.cc, ov-base-int.h, ov-base.cc, ov-bool-mat.cc, ov-bool-mat.h, ov-bool-sparse.cc, ov-bool-sparse.h, ov-bool.cc, ov-bool.h, ov-cell.cc, ov-cell.h, ov-class.cc, ov-class.h, ov-complex.cc, ov-complex.h, ov-cx-mat.cc, ov-cx-mat.h, ov-cx-sparse.cc, ov-cx-sparse.h, ov-fcn-handle.cc, ov-fcn-handle.h, ov-fcn-inline.cc, ov-fcn-inline.h, ov-float.cc, ov-float.h, ov-flt-complex.cc, ov-flt-complex.h, ov-flt-cx-mat.cc, ov-flt-cx-mat.h, ov-flt-re-mat.cc, ov-flt-re-mat.h, ov-int16.cc, ov-int32.cc, ov-int64.cc, ov-int8.cc, ov-lazy-idx.h, ov-oncleanup.cc, ov-oncleanup.h, ov-range.cc ov-range.h, ov-re-mat.cc, ov-re-mat.h, ov-re-sparse.cc, ov-re-sparse.h, ov-scalar.cc, ov-scalar.h, ov-str-mat.cc, ov-str-mat.h, ov-struct.cc, ov-struct.h, ov-uint16.cc, ov-uint32.cc, ov-uint64.cc, ov-uint8.cc: Move #ifdef HAVE_HDF5 inside load_hdf5 and save_hdf5 functions. Always declare and define load_hdf5 and save_hdf5 functions.
author John W. Eaton <jwe@octave.org> and Mike Miller <mtmiller@ieee.org>
date Thu, 26 Feb 2015 10:49:20 -0500
parents dc76e3909d36
children c16c446204e5
line wrap: on
line source

syntax: regexp
# The recurrent (^|/) idiom in the regexps below should be understood
# to mean "at any directory" while the ^ idiom means "from the
# project's top-level directory".

# gnulib makes these silly backup files
.~$

# This directory gets created by gnulib during the build. 
# It contains no Octave files.
^libgnu/*

# This directory mostly contains cruft during build time, but it does
# contain some Octave code, so we gotta be a bit more careful about
# what we ignore here
^m4/(?!ax_).+\.m4$

# Emacs tools create these
(^|/)TAGS$
(^|/)semantic.cache$

(/|^)Makefile\.in$
^INSTALL$

^aclocal\.m4$
^build-.*($|/)
^configure$
^autom4te\.cache($|/)
^config\.in\.h$

# e.g. doc/faq/OctaveFAQ.info
#      doc/interpreter/octave.info-4
^doc/.*\.info(-\d)?$

^doc/\w*/stamp-vti$
^doc/\w*/version\.texi$
^doc/interpreter/images\.mk$

# e.g. liboctave/operators/smx-op-inc.mk
^liboctave/operators/\w+-op-\w+\.mk$

^libinterp/dldfcn/module\.mk$