You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Peter Bourgon 6b97e767b5 Fix example Go code 8 years ago
.idea Add IDEA files. 8 years ago
c-preload First steps towards new config for amazon 8 years ago
d Copyright update, formatting changes 8 years ago
etc More go fiddlings 8 years ago
examples Fix example Go code 8 years ago
lib Fix Intel syntax 8 years ago
static Go example 8 years ago
test Copyright update, formatting changes 8 years ago
.gitignore Remove accidentally-added npm-updated file 11 years ago
.jshintrc Add IDEA files. 8 years ago
LICENSE Copyright update, formatting changes 8 years ago
Makefile Fix up makefile for 14.04 8 years ago
Notes.md Add IDEA files. 8 years ago
README.md Add IDEA files. 8 years ago
app.js Retry connection to proxies 8 years ago
package.json First attempt at proxying remote compilers 8 years ago

README.md

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. Most of the heavy lifting is actually done on the client, which is arguably a bad decision.

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.