| 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, GPL3, MIT |
| Conflicts: | openmw |
| Provides: | openmw |
| Submitter: | None |
| Maintainer: | bwrsandman (Lone_Wolf) |
| Last Packager: | bwrsandman |
| Votes: | 30 |
| Popularity: | 0.022144 |
| First Submitted: | 2011-01-05 16:17 (UTC) |
| Last Updated: | 2024-03-25 21:25 (UTC) |
Since https://gitlab.com/OpenMW/openmw/-/commit/18ef32ca82bd9c3cfcdc9f420131e4697ee054c9 openmw trunk requires bullet built with double precision.
Atm my bullet-multithreaded package is the only one that provides that. I have uploaded a copy of my personal openmw trunk package to https://aur.archlinux.org/packages/openmw-mt-git .
bwrsandman, please check openmw-mt-git and adjust your pkgbuild . Once that has been done I'll submit a deletion request for openmw-mt-git .
Recently openmw master gained support for async physiscs, see https://forum.openmw.org/viewtopic.php?f=8&t=7148 for some background info.
To use this you need bullet with multihreaded support. Repo package doesn't provide that.
Use my new aur package https://aur.archlinux.org/pkgbase/bullet-multithreaded/ and rebuild openmw-git against it.
I've sent you my PKGBUILD through email.
@Lone_Wolf I am still maintaining the package. If you have improvements to the PKGBUILD that I should be integrating, let me know.
In general this is a very simple package to maintain and requires little logic since most of the packaging logic is done by cmake. The biggest issue I have is that the devs have stopped branching off of release tags since 0.43 which makes it impossible to deduce the correct version automatically.
bwrsandman, are you still maintaining / using this ?
I have been using my own PKGBUILD for master a few months now and do play openmw using it.
Fails to build after recent boost update.
Errors like Boost_INCLUDE_DIR used as include directory in directory /tmp/yaourt-tmp-****/aur-openmw-git/src/openmw repeated several dozen times, apparently for every file in the build, and then
-- Configuring incomplete, errors occurred!
I tried adding -DBoost_NO_BOOST_CMAKE=ON to the build instructions, this works for some other projects but not openmw.
OK, I just rebuilt after hardcoding #branch=openmw-45 (which is what I really wanted, I didn't want the master branch) and the package built as openmw-git-0.43.0.1680.g03437b712-1-x86_64.pkg.tar.xz. However the 03437b712... commit is indeed the one at the top of the openmw-45 branch as of right now, so I am satisfied with your explanation.
TLDR: The package still rebuilds latest master as it is intended to, which is much more up to date than release 0.44. Error is due to the fact that the 0.44 tag was never merged into master and the standard way of determining versions is broken for this version only.
@Rulatir if you're looking for the 0.44 release please refer to the community version [1]
This package (openmw-git) does not guarentee to be inline with the latest release (last updated on June 20th).
It does, however guarantee to be inline with the latest master of the git repo, which as of writing this is the case (4098a7be1dac0f674171864e78ee1ab10a8d24ce Wed Nov 21 20:24:11 2018 +0100).
The reason why building it gives a misleading version number is the command in pkgver(): git describe --always
The way git describe works is by looking for the latest tag on the branch (master), taking that and giving the number of commits since that tag and a shortref.
The reason why this release is showing up as 0.43 right now is that the folks at openmw never merged the 0.44 tag into master.
Now, I could go against the AUR packaging standards[2] and hard code 0.44 in pkgver(), but I think we can agree that this would cause more issues down the line such as when 0.45 is released. Not to mention this sort of package update forces a half hour to multi hour rebuild for all users using aur helpers.
VCS packages, unfortunately, are not an exact science and they require upstream to do things consistently.
[1] https://www.archlinux.org/packages/community/x86_64/openmw/
[2] https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver()_function
@bwrsandman The cold fact is that there is a release 0.44, but this package builds version 0.43 as of today. Automatic selection of the newest release seems to fail in this case, and manual intervention by maintainer is needed after all. I am therefore flagging the package as outdated.
https://gitlab.com/OpenMW/openmw/issues/4692
Until this bug is resolved, OpenMW will need to require OpenSceneGraph 3.4.1
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