Mercurial > octave-nkf
view etc/README.MinGW @ 20569:b70cc4bd8109
begin removal of global error_state variable
* gripes.h, gripes.cc (gripe_library_execution_error): Delete.
* error.cc (warning_state): Delete unused variable.
(reset_error_handler): Don't set warning_state or error_state.
(debug_or_throw_exception): New static function.
(verror): Don't check error_state.
(vmessage): Call debug_or_throw_exception instead of setting
error_state.
(error_1, error_2): Combine into single function, error_1 that prints
error message and ultimately calls debug_or_throw_exception.
(verror, verror_with_cfn, verror_with_id_cfn): Call error_1. Don't
check or set warning_state.
(error): Don't check error_state.
(Flasterror, Flasterr): Adapt to not using error_state.
(interpreter_try): Don't unwind_protect error_state.
* NEWS: Update.
* doc/interpreter/external.txi: Explain octave_execution_exception
instead of error_state for matrix addition example.
* jit-typeinfo.cc (octave_jit_gripe_nan_to_logical_conversion,
octave_jit_ginvalid_index, octave_jit_gindex_range,
octave_jit_paren_scalar, octave_jit_paren_scalar_subsasgn):
Don't catch octave_execution_exception.
* cellfun.cc (Fcellfun): Use exceptions instead of error_state.
* ls-mat-ascii.cc (save_mat_ascii_data): Likewise.
* mex.cc (mexCallMATLAB, mexEvalString): Likewise.
* variables.cc (safe_symbol_lookup): Likewise.
* svd.cc (Fsvd): Eliminate use of error_state.
* __magick_read__.cc (read_file, write_file): Likewise.
* variables.cc (generate_struct_completions): Eliminate use of
obsolete warning_state variable.
* ov-builtin.cc (octave_builtin::do_multi_index_op): Don't catch
octave_execution_exception and call gripe_library_execution_error.
* ov-class.cc (octave_class::reconstruct_exemplar): Eliminate use of
error_state. Catch possible octave_execution_exception in
do_multi_index_op.
* ov-mex-fcn.cc (octave_mex_function::do_multi_index_op): Eliminate
use of error_state. Catch possible octave_execution_exception in
call_mex.
* ov-fcn-handle.cc (octave_fcn_binder::maybe_binder): Eliminate use of
error_state.
* ov-oncleanup.cc (octave_oncleanup::~octave_oncleanup): Eliminate use
of error_state. Propagate possible octave_execution_exception from
do_multi_index_op.
* ov.cc (octave_value::assign, do_binary_op, do_unary_op,
octave_value::do_non_const_unary_op): Don't catch
octave_execution_exception here.
* oct-parse.in.yy (octave_base_parser::finish_colon_expression,
octave_base_parser::finish_array_list): Eliminate use of warning_state
and error_state.
(Feval, Fevalin): Use exceptions instead of error_state.
* pt-eval.cc, pt-eval.h (tree_evaluator::unwind_protect_exception):
New static variable.
* (tree_evaluator::visit_statement): Don't catch
octave_execution_exception here.
(tree_evaluator::visit_try_catch_command,
tree_evaluator::do_unwind_protect_cleanup): Eliminate use of error_state.
(tree_evaluator::visit_unwind_protect_command): Use
unwind_protect_exception to track whether an exception has occurred in
the try block.
| author | John W. Eaton <jwe@octave.org> |
|---|---|
| date | Thu, 01 Oct 2015 16:18:19 -0400 |
| parents | 446c46af4b42 |
| children |
line wrap: on
line source
1. General Users ================ A MInGW bundle is available from sourceforge. http://octave.sourceforge.net/index.html 2. Developers ============= The process for building Octave from source is as follows. * Install development tools and compiler * Install or compile dependencies of Octave * Download Octave source * Configure and compile source We strongly encourage experienced users to build Octave from the testing and development snapshots to try the latest features of Octave. A good tutorial on building Octave for version 3.2 is available from http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/admin/Windows/mingw32/HOWTO.txt Additional information beyond the tutorial is summarized below. 2.1 Development tools and compiler ---------------------- Msys + MinGW development Tools The Msys + MinGW development Tools are required to build Octave from source. The latest version of the Msys system is 1.0.16. For MinGW, search and use the most recent version available. Note: The Howto.txt file describing the development tools is rather old. The latest GCC (GNU Complier Collection) for MinGW is gcc-4.5.0. Earlier versions are not recommended for building Octave 3.4.xx. The latest Msys, MinGW, and GCC tools can be downloaded from http://sourceforge.net/projects/mingw/files/ (Compiling for 64-bit binaries requires mingw-64 toolkits. This has not been tested.) 2.2 Dependencies ---------------------- External program dependencies * gnuplot (you can build this with the shell script mentioned in Howto.txt) * MikTeX * ghostscript * pstoedit (required for printing using FLTK (OpenGL) graphics) * fig2dev (Optional; better quality for FLTK printing in some file formats) * sed * less The tools below are required for building the development sources from the Mercurial archive, but not for simply building Octave from a snapshot tar.gz file. * Mercurial * git * automake * autoconf Library dependencies Please read Howto.txt carefully on how to build them. The Howto.txt is old so some revisions will be required when using GCC-4.5.0 2.3 Download Octave source ---------------------- The source for testing snapshots can be downloaded from the official Octave web site. http://www.octave.org/download.html The very latest development code is also available via anonymous access to a read-only Mercurial archive. The method of download is described on the web site. You will also need to install gnulib as another dependency. Please visit http://www.gnu.org/software/gnulib/ and download sources using git. 2.4 Configure and compile source ---------------------- Building from source can be carried out using the script described in Howto.txt. When using GCC-4.5.0, remove flags for shared libstdc++ because a shared build is already the default. When running './configure', you must add '--enable-float-truncate' option. Please see the following thread for more information: http://thread.gmane.org/gmane.comp.gnu.octave.bugs/12361/focus=12404 To build development sources from the Mercurial repository you must run bootstrap before running configure and make. This requires that automake and autoconf tools be installed. Tatsuro MATSUOKA tmacchant@yahoo.co.jp Benjamin Lindner bjmldn@gmail.com Last updated: Sat Jan 22 17:29:12 PST 2011