Eve is a set of tools to help us think. Currently, these tools include: a temporal query language, a compiler, and a database.
Before you can install Eve you'll need need LuaJIT, gcc, make, and python. Currently, building from source is only supported on Linux and OSX. On Windows, we've managed to compile Eve in cygwin, but have not gotten it to run yet. Contributions are welcome on this front.
First install gcc, make, and python using your operating system's standard channels. Chances are you already have these. Install luajit by downloading LuaJIT-2.1.0-beta2 and then in the LuaJIT directory:
make
make install
By default, LuaJIT is not added to your path, so you'll need to do that as well:
ln -sf luajit-2.1.0-beta2 /usr/local/bin/luajit
Next you'll need to download the Eve source, either by cloning our repository
git clone https://github.com/witheve/Eve.git
or downloading the source directly.
To build Eve, execute make in the eve/build directory.
Eve is also on Docker Hub. You can get our container with the following command:
docker pull witheve/eve
Windows Users - Docker for Windows requires Microsoft Hyper-V, which requires Windows 10. For users of earlier Windows versions, binaries are forthcoming.
To run Eve, execute the following command in the eve/build directory:
./eve
This command launches a server at http://localhost:8080. You can configure the port with the --port flag e.g. ./eve --port 1234. You can point your browser that location to access the Eve editor.
If you want to compile an existing program, use the -e flag and provide a path to a *.eve file e.g. ./eve -e ../examples/tic-tac-toe.eve. As you make changes in the editor, they will be reflected back into this file.
To run the Docker container, execute:
docker run -p [port]:8080 witheve/eve [eve_file]
Here, [port] is an available port on your local machine. It can be 8080 or any other port you would like. Then direct your browser to http://localhost:[port] to access the editor.
Note: The working directory of the container is eve/build. To run a program in the eve/examples directory, you need to provide a relative path e.g. ../examples/tic-tac-toe.eve. To pass Eve files on your local machine into the container, you'll need to mount a docker volume.
You can learn about Eve with the following resources:
Please let us know what kind of documents would be the most helpful as you begin your journey with Eve. We want our documentation to be a highlight of the Eve experience, so any suggestions are greatly appreciated.
The Eve community is small but constantly growing, and everyone is welcome!
- Join our mailing list and get involved with the latest discussions on Eve.
- Impact the future of Eve by getting involved with our Request for Comments process.
- Read our development diary.
- Follow us on twitter.
The best way to contribute right now is to write Eve code and report your experiences. Let us know what kind of programs you’re trying to write, what barriers your are facing in writing code (both mental and technological), and any errors you encounter along the way. Also, let us know what you love! What features are your favorite?
Another way to really help us is to host your *.eve files on Github, so we can get Eve recognized as an official language in the eyes of Github. Be sure to also send us a link to your repo!
Please file any issues in this repository. Before you file an issue, please take a look to see if the issue already exists. When you file an issue, please include:
- The steps needed to reproduce the bug
- Your operating system and browser.
- If applicable, the .*eve file that causes the bug.
Eve is licensed under the Apache 2.0 license, see LICENSE for details.
Eve is currently at a very early, "pre-alpha" stage of development. This means the language, tools, and docs are largely incomplete, but undergoing rapid and continuous development. If you encounter errors while using Eve, don't worry: it's likely our fault. Please bring the problem to our attention by filing an issue.
As always, with pre-release software, don’t use this for anything important. We are continuously pushing to this codebase, so you can expect very rapid changes. At this time, we’re not prepared make the commitment that our changes will not break your code, but we’ll do our best to update you on the biggest changes.