widelands-dev team mailing list archive

[Hans Joachim Desserud <launchpad@xxxxxxxxxxxx>]

The proposal to merge lp:~widelands-dev/widelands/travis-osx into lp:widelands has been updated.

Description changed to:

Ready for feedback, probably not ready for merge.

As mentioned I came across the travis documentation for running on osx [1][2][3] on travis.

So far, I've set added two simple build to run a debug and release build on osx [4]. This is mostly working, except for the regression test suite [5], which is where I need some help.

I stronly suspect it needs an equivalent of xvfb which we use to present the graphic on Linux, though I don't know what that would be in the osx world. It could be xvfb installed through brew or it could be something completely different. Would appreciate input here. :) If it turns out to be really tricky, we could keep the regression tests for linux only and figure out how to deal with them later. Presumably, verifying that things are buildable would be better than no checks at all.

The second thing is compilers, where I don't know what the situation is like in osx-land. We have a wide array of compilers tested for linux where we ensure that WL is buildable by both latest and newest and oldest supported versions of GCC and Clang. For osx, I've gone the default compiler. It seemed like brew could install alternative ones, but I don't know how many would be needed/useful. (Also want to avoid too many builds in total). I added one debug and release build initially, which seemed like a good place to start.

Somewhat related, when starting out, I tried to follow the osx-section fot he build page[6]. This turned out to be outdated and after "converting" things to brew as I went along, I finally discovered the separate osx build page [7]. I am not sure why this is completely separate from the rest of the build instructions, nor why there are two set of instructions. 
Since the former seems rather outdated, I wonder if the best would be to
move the standalone page in as part of the overall build page and keep it up to date there.

This is bound to have conflicts with the other travis MP I have going. I knew that from the get-go, but they do different things, so I didn't want to mix them too much. I can sort out the conflicts when one of them is landed. :) I suspect the other one might be first.

Just a quick headsup: I might not be able to respond to comments here the next couple of days.


[1] https://docs.travis-ci.com/user/osx-ci-environment/
[2] https://docs.travis-ci.com/user/multi-os/
[3] And yes, I know it's called macOS these days :p
[4] https://travis-ci.org/widelands/widelands/builds/254399849
[5] https://travis-ci.org/widelands/widelands/jobs/254399850
[6] https://wl.widelands.org/wiki/BuildingWidelands/#building-under-mac-os-x
[7] https://wl.widelands.org/wiki/BuildingWidelandsMac/

-- Original description
Strictly WIP at the moment, but I believe I need a merge proposal for bunnybot to pick it up and run the builds? (Also is there a way to re-trigger builds manually? Might come in handy for this)

For more details, see:
https://code.launchpad.net/~widelands-dev/widelands/travis-osx/+merge/327490
-- 
Your team Widelands Developers is requested to review the proposed merge of lp:~widelands-dev/widelands/travis-osx into lp:widelands.