The build button should be clickable, and refer to a log to indicate what went wrong exactly.

[GijsTimmers]

When you click the button, you should be referred to log.txt, which contains:

• The build target: uname -a
• The build log

Future: set up a build farm with a couple of VirtualBox appliances. Make the farm compile for each target, return binaries and the build logs, and upload them to github in a clean fashion. For example:

[gijs@ubuntu test]$ tree
.
├── lin
│   ├── build
│   │   ├── arch
│   │   │   ├── x86
│   │   │   │   └── jsh-1.2.0
│   │   │   └── x86_64
│   │   │       └── jsh-1.2.0
│   │   ├── debian
│   │   │   ├── x86
│   │   │   │   └── jsh-1.2.0
│   │   │   └── x86_64
│   │   │       └── jsh-1.2.0
│   │   ├── fedora
│   │   │   ├── x86
│   │   │   │   └── jsh-1.2.0
│   │   │   └── x86_64
│   │   │       └── jsh-1.2.0
│   │   ├── redhat
│   │   │   ├── x86
│   │   │   │   └── jsh-1.2.0
│   │   │   └── x86_64
│   │   │       └── jsh-1.2.0
│   │   └── ubuntu
│   │       ├── x86
│   │       │   └── jsh-1.2.0
│   │       └── x86_64
│   │           └── jsh-1.2.0
│   └── source
│       └── jsh-1.2.0.tar.gz
└── mac
    ├── build
    │   └── jsh-1.2.0.tar.gz
    └── source
        └── jsh-1.2.0.tar.gz

21 directories, 13 files

Or: use the OpenSuse Build Service

[jovanbulck]

Don't try to reinvent the wheel here :p

https://travis-ci.org/jovanbulck/jo-shell

In future we'll add other supported compilers such as clang to the .travis.yml file. Eventual dependencies etc could also explicitly be added, it seems. I'll have to look more into it, but its really awesome :-)