Rivoreo Source Code Repositories
src.rivoreo.one / compiler-explorer / 2e057e59d7810ec7769a89b218b00752a9a040fd
commit2e057e59d7810ec7769a89b218b00752a9a040fd[log] [download]
authorGabriel Devillers <gdevillers@kalray.eu>Fri Jul 29 11:39:05 2016 +0200
committerGabriel Devillers <gdevillers@kalray.eu>Fri Aug 05 11:51:49 2016 +0200
tree6d323109e6b8fe634bd0d5723bc140c9389ef9ba
parent90894e8abc2fdf457170828d3c57e38223bd7ce9 [diff]
Fix: autospawn 1 compiler slot on startup.

Another way of implementing it would have been to check if at least on slot
exist in a $.onDocumentReady close, in static/gcc.js.
But there already was code to spawn slots from previous session in
static/compiler.js so I chose this place.
2 files changed
tree: 6d323109e6b8fe634bd0d5723bc140c9389ef9ba
  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.