Package Details: openjk-git 3303.2764ebc-1

Git Clone URL: https://aur.archlinux.org/openjk-git.git (read-only)
Package Base: openjk-git
Description: Open Source Jedi Knight II + III Engine
Upstream URL: https://github.com/JACoders/OpenJK
Licenses: GPL
Conflicts: openjk
Provides: openjk
Submitter: ImNtReal
Maintainer: ImNtReal
Last Packager: ImNtReal
Votes: 17
Popularity: 0.007623
First Submitted: 2013-05-13 15:11
Last Updated: 2016-06-22 20:04

Latest Comments

ProfessorKaos64 commented on 2016-11-10 19:19

There isn't a need to have a separate openjk package, since this builds both. I do this for a build on SteamOS. A provides "openjk" and "openjk" woudld suffice.

ProfessorKaos64 commented on 2016-11-10 13:12

Yep, visit here to always test with clean chroots:

https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot

Khor commented on 2016-06-20 10:22

Hello mate, Thanks for the work on posting this to the AUR.

But you need to add 'git' to the dependencies of this packages. You really need git to get this done

hyness commented on 2016-05-28 15:22

I created a new package, based on this one, for Jedi Outcast...

https://aur.archlinux.org/packages/openjo-git

xDShot commented on 2016-03-17 04:49

It fails on build now. Any workarounds?:

In file included from /home/xdshot/aur/openjk-git/src/openjk/code/ui/../server/exe_headers.h:27:0,
from /home/xdshot/aur/openjk-git/src/openjk/code/ui/ui_main.cpp:35:
/home/xdshot/aur/openjk-git/src/openjk/code/ui/../server/../qcommon/q_shared.h: In function 'int Q_isnan(float)':
/home/xdshot/aur/openjk-git/src/openjk/code/ui/../server/../qcommon/q_shared.h:783:17: error: 'isnan' was not declared in this scope
return isnan (f);
^
/home/xdshot/aur/openjk-git/src/openjk/code/ui/../server/../qcommon/q_shared.h:783:17: note: suggested alternative:
In file included from /usr/include/c++/5.3.0/random:38:0,
from /usr/include/c++/5.3.0/bits/stl_algo.h:66,
from /usr/include/c++/5.3.0/algorithm:62,
from /home/xdshot/aur/openjk-git/src/openjk/code/ui/ui_main.cpp:32:
/usr/include/c++/5.3.0/cmath:641:5: note: 'std::isnan'
isnan(_Tp __x)
^
code/CMakeFiles/openjk_sp.x86_64.dir/build.make:1742: recipe for target 'code/CMakeFiles/openjk_sp.x86_64.dir/ui/ui_main.cpp.o' failed
make[2]: *** [code/CMakeFiles/openjk_sp.x86_64.dir/ui/ui_main.cpp.o] Error 1
CMakeFiles/Makefile2:145: recipe for target 'code/CMakeFiles/openjk_sp.x86_64.dir/all' failed
make[1]: *** [code/CMakeFiles/openjk_sp.x86_64.dir/all] Error 2
Makefile:149: recipe for target 'all' failed
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...

hyness commented on 2015-11-14 03:19

Typo in symlink to sp and ded binaries...

ln -s "/opt/${pkgname}JediAcademy/openjk_sp.${_jkarch}" "${pkgdir}/usr/bin/openjk_sp"
ln -s "/opt/${pkgname}JediAcademy/openjkded.${_jkarch}" "${pkgdir}/usr/bin/openjkded"

should be

ln -s "/opt/${pkgname}/JediAcademy/openjk_sp.${_jkarch}" "${pkgdir}/usr/bin/openjk_sp"
ln -s "/opt/${pkgname}/JediAcademy/openjkded.${_jkarch}" "${pkgdir}/usr/bin/openjkded"

mwohah commented on 2015-07-30 17:41

Thanks for the update. One thing I noticed is that OpenJK supports placing your base assets inside the /opt/openjk-git/JediAcademy/base folder to have a system wide installation (IIRC you can also place them in your home folder). However, when using the desktop file, OpenJK will not detect them because it looks inside the working directory. I can solve this by adding the following line to the openjkmp.desktop file:

Path=/opt/openjk-git/JediAcademy/

This may however be a bit controversial, perhaps it would be interesting to use a path from /usr/local/share or just print a message regarding where you have to install your base files?

ImNtReal commented on 2015-07-27 16:55

@mwhoha, the reason is that no one has brought that up, and I haven't tried building in 64-bit since it was originally broken. I'll switch it to 64-bit.

mwohah commented on 2015-07-27 15:53

Is there a specific reason it pulls 32-bit multilib libraries on 64-bit? OpenJK has natively supported 64-bit Linux for quite some time now. Each time I install, I just remove all the lib32- prefices, as well as the -m32 and void pointer size parameters for CMake. It seems to run rather well here on native 64-bit.

TimorLee commented on 2014-06-29 10:49

Hey, just a heads up, you should make sure that gcc-multilib is installed, it won't compile if you only have gcc on a 64-Bit environment!

All comments