Rivoreo Source Code Repositories
src.rivoreo.one / compiler-explorer / 712d255d2042e9c8ad41643badb51af9ad43498f
commit712d255d2042e9c8ad41643badb51af9ad43498f[log] [download]
authorMatt Godbolt <matt@godbolt.org>Wed Sep 21 21:31:42 2016 -0500
committerMatt Godbolt <matt@godbolt.org>Wed Sep 21 21:31:42 2016 -0500
tree267600b3a2038ba5f2a1ca19f405bc49e7a130ec
parent7c35539aa55e20b248ab33d0914be79996edebbd [diff]
Latest GoldenLayout with numerous bug fixes
1 file changed
tree: 267600b3a2038ba5f2a1ca19f405bc49e7a130ec
  1. .bowerrc
  2. .gdb_history
  3. .gitignore
  4. .idea/
  5. .jshintrc
  6. .travis.yml
  7. LICENSE
  8. Makefile
  9. Notes.md
  10. README.md
  11. app.build.js
  12. app.js
  13. bower.json
  14. c-preload/
  15. d/
  16. etc/
  17. examples/
  18. gdb.txt
  19. launch_c++_port_10241.sh
  20. launch_port_10241.sh
  21. lib/
  22. package.json
  23. static-old/
  24. static/
  25. 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.