Rivoreo Source Code Repositories
src.rivoreo.one / compiler-explorer / 32e742ee512be8bbed24d5490a63201252be5539
commit32e742ee512be8bbed24d5490a63201252be5539[log] [download]
authorMatt Godbolt <matt@godbolt.org>Sat Aug 06 15:20:03 2016 -0500
committerMatt Godbolt <matt@godbolt.org>Sat Aug 06 15:20:03 2016 -0500
tree7024de930558ad897f0378bf740513bf2df21b74
parent51ae5486d44f7d8d17062787bd57080870557f2b [diff]
More tidyups; added some TODOs
2 files changed
tree: 7024de930558ad897f0378bf740513bf2df21b74
  1. .gdb_history
  2. .gitignore
  3. .idea/
  4. .jshintrc
  5. .travis.yml
  6. LICENSE
  7. Makefile
  8. Notes.md
  9. README.md
  10. app.js
  11. c-preload/
  12. d/
  13. etc/
  14. examples/
  15. gdb.txt
  16. launch_c++_port_10241.sh
  17. launch_port_10241.sh
  18. lib/
  19. package.json
  20. static/
  21. test/
README.md

Build Status Codewake

GCC Explorer

GCC Explorer is an interactive compiler. The left-hand pane shows editable C/C++ code. The right, the assembly output of having compiled the code with a given compiler and settings.

Try out the demo site!

Developing

GCC Explorer is written in node.

Assuming you have npm and node installed, simply running make ought to get you up and running with a GCC explorer running on port 10240 on your local machine: http://localhost:10240

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.YOURHOSTNAME.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.