[Greg McKaskle]

A LV diagram is always compiled to some lower level form before execution, and over the years several approaches have been added for reaching targets.

LV desktop and LV RT products compile the diagram directly to machine code for the CPU and OS ABI in use. The code is capable of calling binary library code and this is used for vision, memory management, etc.

LV embedded, also called LV PDA is the product that instead compiles the diagram and generates C source code which can be sent through the embedded C compiler of the HW platform being targeted. The runtime libs are provided as C code.

There are a few products developed for LEGO which compile the diagram and produce a VM bytecode which is then interpreted by the virtual machine running on the brick.

The most recent release of LV desktop and RT (LV 2010), compiles the diagram into LLVM bytecode and the LLVM backend tools are used to produce a more optimized machine code for the target processor.

As stated, at this time, the appropriate way to target the VEX HW would be to use the embedded version. Personally, I don't think it will produce a very satisfying result.

Greg McKaskle