Package Details: openmw-git 0.48.0.r5496.g8471cfb576-1

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.000019
First Submitted: 2011-01-05 16:17 (UTC)
Last Updated: 2024-06-25 12:42 (UTC)

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

Latest Comments

1 2 3 4 5 6 .. 15 Next › Last »

Lone_Wolf commented on 2025-05-02 17:13 (UTC)

Archlinux default is gcc . Anyone who set clang as default compiler on archlinux should know how they achieved it and be able to reverse it.

Incase you're on some other distro that sets clang as default compiler, you'll need to ask on their support channels how to build with gcc.

Assuming you're on archlinux and don't know how to revert to defaults : setup clean chroot building. see https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

Another option is not to build from source but use a nightly binary provided by upstream, see https://redfortune.de/openmw/nightly/?C=M;O=D

Spiolito commented on 2025-05-01 21:48 (UTC)

I was unable to install via yay as per chapien's comment as clang is used. I wasn't able to set the compiler to gcc/g++ in makepkg.conf or environment variable, though. It always seems to be ignored. Any pointers?

chapien commented on 2025-03-11 13:56 (UTC)

Currently, fails to build if clang is set as the system compiler. Changing compiler to GCC/G++ fixes this. I'm a little rusty with PKGBUILD, so I can't recall if this can be fixed via the PKGBUILD. If it can, great. If it can't, and you're having errors building, check to see if your system compiler is on clang or G++, and adjust accordingly. Issue: https://gitlab.com/OpenMW/openmw/-/merge_requests/4549

Lone_Wolf commented on 2025-02-02 23:08 (UTC) (edited on 2025-02-02 23:08 (UTC) by Lone_Wolf)

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.

S3ctor commented on 2025-02-02 21:38 (UTC) (edited on 2025-02-04 13:07 (UTC) by S3ctor)

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.

EDIT:

Sorry for the false alarm, sdl2-compat 2.30.52 did indeed solve the issue.

Lone_Wolf commented on 2024-12-12 08:34 (UTC)

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.

Patola commented on 2024-12-12 04:31 (UTC)

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?

Lone_Wolf commented on 2024-11-16 09:36 (UTC) (edited on 2024-11-16 09:37 (UTC) by Lone_Wolf)

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.

S3ctor commented on 2024-11-16 08:14 (UTC)

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!

Le_Limule commented on 2024-08-20 16:38 (UTC)

@Lone_Wolf

That's it. Thank you!

1 2 3 4 5 6 .. 15 Next › Last »