Rivoreo Source Code Repositories
src.rivoreo.one / compiler-explorer / 37076ebcd91c8f2f20f1223cbfe6ac4e48db7ec6
commit37076ebcd91c8f2f20f1223cbfe6ac4e48db7ec6[log] [download]
authorGabriel Devillers <gdevillers@kalray.eu>Thu Aug 04 14:13:05 2016 +0200
committerGabriel Devillers <gdevillers@kalray.eu>Fri Aug 05 11:51:49 2016 +0200
tree5a48ec45a92cc122be77eb379e1d313322cec827
parent1dfd40961f43141901f933ee601d9c4bc978bfa4 [diff]
Hide close cross in slots if need be.

Better cross  (unicode as icon).
CSS settings are better applied.
3 files changed
tree: 5a48ec45a92cc122be77eb379e1d313322cec827
  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.