| commit | 3e405c0a9fb704ba4bf734cf06334a645d456aa5 | [log] [download] |
|---|---|---|
| author | Matt Godbolt <mgodbolt@drw.com> | Fri Dec 09 06:16:06 2016 -0600 |
| committer | Matt Godbolt <mgodbolt@drw.com> | Fri Dec 09 06:16:06 2016 -0600 |
| tree | 1bca05524c87f06b4cd9053dee7f6731032f3575 | |
| parent | 7a173dcf4fc3305a8c7b599b0550a577a2c0e802 [diff] |
Actually run npm tests as part of 'make test'
- .bowerrc
- .gdb_history
- .gitignore
- .idea/
- .jshintrc
- .travis.yml
- LICENSE
- Makefile
- README.md
- app.build.js
- app.js
- bower.json
- c-preload/
- d/
- etc/
- examples/
- lib/
- package.json
- static-old/
- static/
- test/
Compiler Explorer
Compiler Explorer is an interactive compiler. The left-hand pane shows editable C/C++/Rust/Go/D code. The right, the assembly output of having compiled the code with a given compiler and settings. Multiple compilers are supported, and the UI layout is configurable (the Golden Layout library is used for this).
Try out one of the demo sites: C++, Rust, D or Go.
Developing
Compiler Explorer is written in node.js.
Assuming you have npm and node installed, simply running make ought to get you up and running with an Explorer running on port 10240 on your local machine: http://localhost:10240/
The Makefile will automatically install all the third party libraries needed to run; using npm to install server-side components and bower to install all the client-facing libraries.
If you want to point it at your own GCC or similar binaries, either edit the etc/config/gcc-explorer.defaults.properties or else make a new one with the name gcc-explorer.local.properties. *.local.properties files have the highest priority when loading properties.
The config system leaves a lot to be desired, I'm working on porting CCS to javascript and then something more rational can be used.
Feel free to raise an issue on github or email me directly for more help.
Credits
Compiler Explorer is maintained by Matt Godbolt. Multiple compiler and difference view was implemented by Gabriel Devillers.