Locally maintained version of the FieldSystem VEX parser as separate project
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
Harro Verkouter 2a5b361e8f gcc complains about (intended) implicit fall-through il y a 1 an
src Create shared lib, cranked up compiler warnings il y a 2 ans
CMakeLists.txt gcc complains about (intended) implicit fall-through il y a 1 an
README.md Still not ok il y a 1 an

README.md

Stand-alone version of the official VEX parser.

Uses cmake to figure out your system and create makefiles. Needs bison, flex and a C compiler.

In the following, assume ${MYVEX} expands to the directory where this file (README.md) is located. Thus ${MYVEX}/README.md == the file you’re now reading.

Create a directory where you will build for the desired system + installation location:

$> mkdir /path/to/build
$> cd /path/to/build

Now ask cmake to set up, passing in options a la cmake ("-DXXX=YYYY”):

$> cmake -DCMAKE_INSTALL_PREFIX=/myvex/install/dir ${MYVEX}

If your system is all ok, you can now do:

$> make

to build the system, or, when feeling bold:

$> make install

to build+install in one go.

make install will install the following files:

    ${CMAKE_INSTALL_PREFIX}/lib/libvex.a
    ${CMAKE_INSTALL_PREFIX}/include/vex.h
           ...                     /vex++.h (for C++ code)
           ...                     /vex_parser.h