Bearbin's Automated Builds

[bearbin]

Minor change to the URL: now http://builds.cuberite.org

The old one still works though.

[bearbin]

armhf (raspi) builds are down for now, our power went down today and the pi didn't want to come back up again.

[xoft]

It seems my win builders got kicked off the network for some reason, I restarted the connections, too.

I'm wondering if QtBiomeVisualiser could be built as well. Is there any demand for it? I could set up the windows builds, but I have no idea about Linux builds.

[bearbin]

Yep. I'd be perfectly happy to set up a build.

Only thing is, I'd really like it to be split into a seperate GitHub project if we were to do that, so only changes to it will trigger a rebuild.

[xoft]

It shares code with MCS, so it can't be split that easily.

[bearbin]

Can it not just include MCServer as a submodule?

[xoft]

How about, instead, building it together with MCS, so that each time you build, you get the MCS executable and the QTBV executable. Much easier.

[bearbin]

It doesn't really achieve what I wanted. What we have ATM is fine I guess.

[Seadragon91]

Why are there no more any raspberry pi builds?
I found a way to cross compile a raspberry pi build on my linux laptop. I didn't fixed the problem with tolua, but I found a nice workaround to use the tolua from the compiled mc server for my linux laptop.

Should I create a tutorial for that until the cross compile problem has been fixed?

[xoft]

If you can write a tutorial for that, that'd be cool, even if bearbin doesn't use it for the build server. I would use it myself, and there are probably others