muParser - a fast math parser library
Author: Ingo Berg
Description: a fast and portable math parser library written in C++
Keywords: math parser, parser, expression evaluator, C++, Mathematical, Expression

class documentation | math parser download
Start page About the parser News Projects using this lib Licence Features Features Overview Built in functions Built in binary operators Build instructions Building on Win32 Building on BSD/Linux Misc build instructions Including the files Where to ask for help Math parser interface Parser (de)initialization Evaluating an expression Setting the expression Defining identifier charsets Defining parser variables Explicit variable definition Implicit variable definition Defining constants Defining functions Defining operators Unary operators Binary operators Querying variables Querying constants Value recognition callbacks Removing variables/constants Error handling Example code Current version Release notes Benchmarks | # Build instructions ## Building on win32 muParser supports various win32 command-line compilers: Mingw Borland C++ Watcom Microsoft CL and provides also project files for MSVC6 IDE and the Borland C++ Builder. In order to compile muParser from makefiles, open an MSDOS prompt and then move to the muParser/build directory and type: mingw32-make -fmakefile.gcc for mingw nmake -fmakefile.vc for msvc make -fmakefile.bcc for borland wmake -fmakefile.wat for watcom All makefiles support the following options:
      # Set to 1 to build debug version [0,1]
      #   0 - Release
      #   1 - Debug
      DEBUG = 0

      # Set to 1 to build shared (DLL) version [0,1]
      #   0 - Static
      #   1 - DLL
      SHARED = 0

      # Set to 1 to compile samples [0,1]
      SAMPLES = 1
The muParser library is created in the 'lib' folder and the sample binaries are created in samples\example1 or samples\example3.
| samples\example1 can be compiled *only* when building muParser as a STATIC library (SHARED=0). samples\example3 can be compiled *only* when building muParser as a SHARED library (SHARED=1).
## Building on BSD/Linux muParser can be installed just extracting the sources somewhere and then, from a terminal, typing:
     cd [path to muParser]
     ./configure [--enable-shared=yes/no] [--enable-samples=yes/no]
                 [--enable-debug=yes/no]
     make
     [sudo*] make install
* = this command must be executed with root permissions and thus you have to use 'sudo' or just 'su' to gain root access. Note that installation is not strictly required. The "make" step will create the muParser library in 'lib' and the sample binary in samples/example1. The samples/example2 and samples/example3 are win32-specific and thus won't be built. ## Other miscellaneous info Unix-specific If you don't like to have your muParser folder filled by temporary files created by GCC, then you can do the following:
      mkdir mybuild && cd mybuild && ../configure && make
to put all object files in the "mybuild" directory. If you want to use muParser library in your programs, you can use the pkg-config program (this works only if muParser was installed with 'make install' !). The commands: pkg-config muparser --cflags pkg-config muparser --libs will return all useful info you need to build your programs against muParser ! ## Including the source code directly Sometimes including the library sources directly into an application is the easiest possibility to avoid linker conflicts originating from different versions of the runtime libraries used by the parser and your project. In order to use the parser simply include the following files into your project: muParser.cpp muParserBase.cpp muParserBytecode.cpp muParserCallback.cpp muParserError.cpp muParserTokenReader.cpp And make sure the following files can be found in your projects include path: muParser.h muParserBase.h muParserBytecode.h muParserCallback.h muParserDef.h muParserError.h muParserFixes.h muParserStack.h muParserToken.h muParserTokenReader.h The parser class and all related classes reside in the namespace `mu` (MathUtils). So make sure to either add a using
    using namespace mu;
to your files or reference all classes with their complete name. ## Where to ask for help If you find problems with either compilation, installation or usage of muParser, then you can ask in the muParser forum at: https://sourceforge.net/forum/forum.php?forum_id=462843 For more info about muParser, visit: http://sourceforge.net/projects/muparser/ http://muparser.sourceforge.net
© 2005-2006 Ingo Berg | ^ TOP