Package Details: vcmi 1.6.7-4

Git Clone URL: https://aur.archlinux.org/vcmi.git (read-only, click to copy)
Package Base: vcmi
Description: Open-source engine for Heroes of Might and Magic III
Upstream URL: https://github.com/vcmi/vcmi
Keywords: homm homm3 vcmi
Licenses: CC-BY-SA-4.0, GPL-2.0-or-later
Submitter: Raziel23
Maintainer: Gigas002
Last Packager: Gigas002
Votes: 50
Popularity: 0.058509
First Submitted: 2013-03-12 14:11 (UTC)
Last Updated: 2025-03-10 11:00 (UTC)

Pinned Comments

Gigas002 commented on 2024-05-29 15:08 (UTC)

PKGBUILD tweaks

If you want to build with clang, add this part to cmake flags:

    -DCMAKE_CXX_COMPILER='clang++' \
    -DCMAKE_C_COMPILER='clang' \

If you want to use bundled fuzzylite:

    -DFORCE_BUNDLED_FL=ON \

If you want to use innoextract (system-wide installation won't work since vcmi has a temporary? fork of innoextract for now):

    -DENABLE_INNOEXTRACT=ON \

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

Raziel23 commented on 2014-08-24 14:22 (UTC)

[Update without bump the pkgver]. Set MAKEFLAGS="-j1" in the PKGBUILD in order to avoid running out of memory during compilation, because some people have problems with exceeding their memory during compilation with more than one job. Better safe than sorry. This change doesn't affect the package (only compilation) so I didn't bump the pkgver to avoid recompilation for other people.

Raziel23 commented on 2014-08-24 13:51 (UTC)

@bladedglove: Good catch. Thank you for the tip. With my 2 cores (2 threads) memory usage doesn't exceed my 8 GB. I think that instead of changing /etc/makepkg.conf I will set the variable MAKEFLAGS="-j1" in the PKGBUILD to avoid such situations. The compilation time will take longer (for me with -j1 it takes about 40 minutes), but at least more people will be able build the vcmi successfully.

bladedglove commented on 2014-08-24 08:15 (UTC)

To avoid running out of memory and freezing your system on multicore computers, set a lower value for MAKEFLAGS="-jX" in /etc/makepkg.conf before running makepkg -s. Compiling with "-j4" (forcing the compiler to use all 4 cores of my i5 CPU) resulted in running out of memory (8GB) and failing at 56%, but the "-j1" value forced the compiler to use only 1 core and the top memory usage was at around ~3-4GB. Of course, using a huge swap partition/file is also a solution, but that's another story.

Raziel23 commented on 2014-08-02 12:56 (UTC)

@KlavKalashj: I've experienced freezing the system during compilation vcmi version 0.95. Even with the frozen system I was able successfully compile vcmi 0.95. For me with vcmi version 0.96 and with vcmi-git this issue not exist. I can only speak for myself, because the problem doesn't exist for me. I presume that this issue may that exist during compilation registerTypes. This part of compilation takes most memory and time compilation. I'm not vcmi developer, I'm only the package maintainer and I don't know how solve this problem. You can write about this issue in the vcmi forum. Here it is the related topic about this problem: http://forum.vcmi.eu/viewtopic.php?p=11612

KlavKalashj commented on 2014-07-27 14:42 (UTC)

@Raziel23: I am also experiencing freezes when compiling, and I also have 8gb ram. Are you saying that your compilation is finishing even though your computer is frozen? Also, I get this with both this package and vcmi-git.

Raziel23 commented on 2014-07-02 07:44 (UTC)

[Bump to version 0.96-1]. New upstream release. The changelog is as follows: http://forum.vcmi.eu/viewtopic.php?p=12595#12595 I have added libxkbcommon-x11 dependency in order to run properly the vcmilauncher. Starting from version 0.96 vcmi supports XDG filesystem specifications. This transition mean that all user data has been moved according to specs: - Game data (H3 files and mods) and saves: from ~/.vcmi to ~/.local/share/vcmi - Temporary files, including logs: from ~/.vcmi to ~/.cache/vcmi - Config files: from ~/.vcmi/config to ~/.config/vcmi This transition affect users who have already installed previous version of vcmi than 0.96. New users who have not previously installed vcmi are not affected by this transition because those directories will be created automatically during data preparation by vcmibuilder script. Users who have already installed previous version of vcmi have to: - move game data to ~/.local/share/vcmi with command: mkdir ~/.local/share/vcmi && mv ~/.vcmi/{Data,Games,Maps,Mp3,Mods,Saves} ~/.local/share/vcmi/ - move temporary files to ~/.cache/vcmi with command: mkdir ~/.cache/vcmi && mv ~/.vcmi/{*log.txt,downloads} ~/.cache/vcmi/ - remove remaining config files because they are not compatible in vcmi version 0.96 with command: rm -rf ~/.vcmi Here is the appropriate announcement about this: http://forum.vcmi.eu/viewtopic.php?p=11696#11696

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »