| Git Clone URL: | https://aur.archlinux.org/openmw-git.git (read-only, click to copy) |
|---|---|
| Package Base: | openmw-git |
| Description: | An open-source engine reimplementation for the role-playing game Morrowind. |
| Upstream URL: | http://www.openmw.org |
| Licenses: | custom, MIT, GPL-3.0-or-later |
| Conflicts: | openmw |
| Provides: | openmw |
| Submitter: | None |
| Maintainer: | bwrsandman (Lone_Wolf) |
| Last Packager: | Lone_Wolf |
| Votes: | 30 |
| Popularity: | 0.000139 |
| First Submitted: | 2011-01-05 16:17 (UTC) |
| Last Updated: | 2024-06-25 12:42 (UTC) |
sdl3 3.2.2 and sdl2-compat 2.30.52 entered extra repo a few hours ago and should have many fixes .
Try updating first , if that doesn't solve the issue check https://gitlab.archlinux.org/archlinux/packaging/packages/sdl2-compat/-/issues/1 and consider reporting the issue to sdl upstream.
Hi,
there appears to have been a severe breaking change due to a recent SDL update in Arch linux. Still not quite sure what's going on, but I think it may be due to changing to extra/sdl-compat in the last few days. Logs have this:
[11:39:05.405 I] Unhandled SDL event of type 0x202
[11:39:05.405 I] Unhandled SDL event of type 0x217
[11:39:05.405 I] Unhandled SDL event of type 0x20e
[11:39:05.405 I] Unhandled SDL event of type 0x20c
[11:39:05.405 I] Unhandled SDL event of type 0x205
[11:39:05.405 I] Unhandled SDL event of type 0x206
[11:39:05.405 I] Unhandled SDL event of type 0x207
[11:39:05.405 I] Unhandled SDL event of type 0x215
[11:39:05.405 I] Unhandled SDL event of type 0x204
I think this is really an sdl2-compat bug, but I don't think it's a good idea to try replacing it on my system, so not sure if I can really test whether replacing with the sdl package is a solid fix or not.
collada-dom 2.5.0-5 has been patched to build with boost 1.85+ , you no longer need boost183/boost183-libs .
Download latest PKGBUILD for collada-dom, remove boost183* and build collada-dom.
I am having issues in compiling openmv-vr-git and it seems the same issue as been reported in this package, related to changes after boost 1.83. How do I change from boost to boost183 for compilation? I've tried installed boost183 and boost183-libs but they conflict with installed boost and boost-libs and I see a lot of sensitive .so files in boost, so my system could become unbootable if I revert to an earlier version of these files, no?
boost183-libs is setup to coexist with boost-libs and openmw has no problem with having both present and will use boost-libs .
However boost183 and boost DO conflict.
boost183 is only needed during building collada-dom and should be removed after that build has finished .
Building in a clean chroot will do this for you automatically,
In case your chosen build method doesn't remove built deps then you need to do that yourself .
TL;DR: remove boost183
If that doesn't help, post full build output somewhere public so others can look at it.
I believe users whom are no longer able to use OpenMW-git after boost 186 must install the boost183-libs package provided by Lone_Wolf here: https://aur.archlinux.org/packages/boost183-libs
Would it be possible to update the mainstream openmw-git package to use boost183-libs instead of boost-libs to avoid build failures? Thanks!
@Lone_Wolf
That's it. Thank you!
Yes, with Update recasnagivation to c393777d26d2ff6519ac23612abf8af42678c9dd from dec 2023 openmw switched to that version .
Using anything older can cause problems .
No, it doesn't work in a fresh folder...
I have recastnavigation-openmw 1.5.1 and no "RecastNavigationConfig.cmake" file... Must i upgrade to recastnavigation-openmw 1.6.0 ? Is it the cause of the pb?
This message only appears for me if recastnavigation-openmw isn't present .
Try building in a new fresh folder.
Pinned Comments
Lone_Wolf commented on 2022-06-17 10:07 (UTC)
openmw-git has been found to require a sizable amount of temporary space during building.
The available amount depends on system specifics so is different for all systems. In case build fails with "no space left on device" you may be bitten by this.
See https://bbs.archlinux.org/viewtopic.php?id=277304 for details and possible solutions.
bwrsandman commented on 2016-09-24 14:59 (UTC) (edited on 2018-11-22 17:28 (UTC) by bwrsandman)
Please refrain from flagging the git version as out date when a new release comes out. The git aur packages update their version on install time based on the tags of the git repo.
Keep in mind that this is a VCS package and it is meant to be in line with the latest master which might not always work. It is not meant to follow the release pattern in any particularly smart way and assumes that upstream maintains their tags consistently.
For the newest release, the correct page is https://www.archlinux.org/packages/?q=openmw