meson_options.txt

# Meson options for binary_c 

option('accurate', type : 'boolean', value: false, description: 'Accurate mathematics mode: compiler options are chosen to keep calculations as accurate as possible.')
option('generic', type : 'boolean', value: false, description: 'Turns off CPU-specific optimization so that the executable can be used on different platforms. Useful for condor/slurm clusters.')
option('valgrind', type: 'boolean', value: false, description: 'Turns off CPU-specific instruction sets that are not compatible with Valgrind.')
option('libname', type : 'string', value: 'binary_c', description: 'The binary_c shared-library name, usually "binary_c" to give a file libbinary_c.so (on Linux).')
option('usepch', type : 'boolean', value: true, description: 'Use pre-compiled headers. Binary_c usually precompiled headers which are used for many object-file builds to considerably speed up compilation. You may wish to disable this if it causes you, or your compiler, problems.' )
option('clean_data_objects', type : 'boolean', value : false, description: 'If true, data objects - which are pre-compiled object files that persist between builds, are purged before the build.')
option('data_object_builder', type : 'string', value : 'binary_c', description: 'Sets whether binary_c or meson builds data objects. It is usually faster to let meson do it, because on each new rebuild these are not rebuilt, saving time. However, on MacOSX this does not work, so you must use binary_c. Usually binary_c is faster because ninja will distribute the build across multiple CPUs, so we default to this.')
option('allow_libs', type : 'boolean', value : false, description: 'When using the generic option, external libraries are usually disabled (so you can copy the executable elsewhere). Turning allow_libs on allows on to have a generic build, i.e. independent of architecture details, but with external libraries (e.g. libbacktrace) used.')