OpenMW 0.32.0

[Ace (SWE)]

Interesting, does it only happen on the 64-bit build?

Oh wait, I see the problem...

It seems that my RC build script failed to update the build branch properly, so the 64-bit build ended up being built from some old revision. I cleaned the branch and am currently rebuilding the 64-bit RC with the correct commit, should be done in a bit.

New build is uploaded, can be found on the same link. Or here, if you can't be bothered to go back a page

[raevol]

@psi29a, are the PPAs building correctly?

[psi29a]

The dailies are failing due to patches (for fonts of all reasons) aren't applying cleanly.

Known issue, just takes time to fix.

[maqifrnswa]

@psi29a, are the PPAs building correctly?

should be fixed now but will need to be rebuilt

[raevol]

Sounds good. Thanks!

[sandstranger]

4

[psi29a]

@Sandstranger: Can you go into detail about this java code, what it is used for and how to build it?

I assume that this is the Android framework for getting OpenMW running?

I'm not sure we can just 'merge' this into OpenMW itself.

@Zini and @Scrawl: What do you think? Can you have look here:
https://github.com/sandstranger/eclipse-project
and see if this is something we want to either: merge into OpenMW repo, just host in OpenMW org as an apart repo or not leave this be?

I suspect that this would better hosted in a new git repo, under OpenMW. You can go into your repo settings on github and click on "Transfer ownership" to OpenMW. What then happens is that, if we agree, it now becomes the 'property' of OpenMW group. We would make you the core contributor of this. This means that others can fork it and contribute back and you (and other OpenMW devs) can handle merge requests.

[Zini]

Agreed. A separate repository under the OpenMW organisation seems to be the way to go. I don't see any benefit in merging this repository into our main repository.

[sandstranger]

4

[Zini]

I don't see anything on my end. Anyway, that wasn't correct anyway. You should transfer it to the OpenMW organisation.