2 _____ __ _____________ _______ ______ ___________
3 / \| | \____ \__ \\_ __ \/ ___// __ \_ __ \
4 | Y Y \ | / |_> > __ \| | \/\___ \\ ___/| | \/
5 |__|_| /____/| __(____ /__| /____ >\___ >__|
7 Copyright (C) 2004 - 2020 Ingo Berg
9 =======================================================================
10 https://muparser.beltoforion.de
11 =======================================================================
16 muParser can be installed just extracting the sources somewhere
17 and then, from a terminal, typing:
20 cmake . [-DENABLE_SAMPLES=ON/OFF] [-DENABLE_OPENMP=OFF/ON]
21 [-DBUILD_SHARED_LIBS=ON/OFF]
28 * = this command must be executed with root permissions and thus
29 you have to use 'sudo' or just 'su' to gain root access.
30 Note that installation and ldconfig are not strictly required unless
31 you built in shared mode.
33 The "make" step will create the muParser library in 'lib' and the
34 sample binary in samples/example1.
35 The samples/example2 is win32-specific and thus won't be built.
39 Other miscellaneous info Unix-specific
40 ======================================
42 If you don't like to have your muParser folder filled by temporary
43 files created by GCC, then you can do the following:
45 mkdir mybuild && cd mybuild && cmake .. && make
47 to put all object files in the "mybuild" directory.
49 If you want to use muParser library in your programs, you can use
50 the pkg-config program (this works only if muParser was installed
51 with 'make install' !). The commands:
53 pkg-config muparser --cflags
54 pkg-config muparser --libs
56 will return all useful info you need to build your programs against
61 3. Where to ask for help
62 ========================
64 Please report any bugs or issues at the muparser project page at GitHub:
66 https://github.com/beltoforion/muparser/issues