Connorcreeper wrote:Would it be possible to maybe get a video demonstrating how to do it ??
no
Jk Idk Acronym
Connorcreeper wrote:Would it be possible to maybe get a video demonstrating how to do it ??
hernextmeal wrote:So I got curious and decided to try compiling it on Windows. Turns out that it needs a few more libraries and tools than what the instructions tell you to install. I'm not finished and it's late but for sure libtool, autoconf, automake, and gmp are needed.
Also don't bother with tortoisegit, if you're already using the command line you might as well just use command line git.
When I sort it out I'll make a shell script people can just copy and paste into msys that will download and compile everything. That should be more fool resistant than the current build instructions.
pacman -S git curl zip make gcc mingw-w64-x86_64-{toolchain,make,gcc,SDL2,libjpeg-turbo,libpng,libogg,gmp} autoconf libtool automake gmp-devel unzip p7zip
git clone https://gitlab.com/xonotic/xonotic.git xonotic
pushd xonotic
./all update -l best
git clone https://gitlab.com/MirceaKitsune/voretournament-mod.git data_voretournament
./all compile
pushd data_voretournament
sh build.sh
popd
./all run -customgamedirname2 data_voretournament
explorer "$(cygpath -w "$(pwd)")"
pushd data
curl $URL #where $URL is the URL you wish to download.
popd
hernextmeal wrote:When I sort it out I'll make a shell script people can just copy and paste into msys that will download and compile everything. That should be more fool resistant than the current build instructions.
GramzonTheDragon wrote:Where did you get the music for the older vore tournament? I'm specially interested in that interesting track that's played on soylent space (or however you spell it...).
MirceaKitsune wrote:Thank you for that script, it looks very complete and useful! The Windows users I collaborated with to test my build.sh script didn't require those extra dependencies, so I am a bit curious as to why you need them. Also I wonder if that pacman command can be thought to check whether the packages already exist, and not reinstall everything unnecessarily whenever "pacman -S" is ran... if so I could make it part of my build.sh perhaps. And is "./all compile" really working on Windows... because one of the admins said there's currently a problem with running it through MSYS2..
pacman --needed -S $dependencies
shadyguy wrote:Followed hernextmeal's instructions and ran into a slight hiccup at the end which, it seems, was a result of the Darkplaces engine being incorrectly compiled. Fixed it by downloading the Darkplaces engine manually through a link on the gitlab page *available in Mircea's sig* and placing the unextracted contents in the "darkplaces" folder in the xonotic directory. Thought it worth mentioning, if any other Windows users are having problems. Running Windows 7 x64 myself.
shadyguy wrote:Followed hernextmeal's instructions and ran into a slight hiccup at the end which, it seems, was a result of the Darkplaces engine being incorrectly compiled. Fixed it by downloading the Darkplaces engine manually through a link on the gitlab page *available in Mircea's sig* and placing the unextracted contents in the "darkplaces" folder in the xonotic directory. Thought it worth mentioning, if any other Windows users are having problems. Running Windows 7 x64 myself.
MirceaKitsune wrote:If Darkplaces compiled without errors, there should be no problem. Just remember that darkplaces.exe needs to be renamed into xonotic.exe, while you also need to copy the necessary dll files next to it (from xonotic/misc/buildfiles/win64).
hernextmeal wrote:shadyguy wrote:Followed hernextmeal's instructions and ran into a slight hiccup at the end which, it seems, was a result of the Darkplaces engine being incorrectly compiled. Fixed it by downloading the Darkplaces engine manually through a link on the gitlab page *available in Mircea's sig* and placing the unextracted contents in the "darkplaces" folder in the xonotic directory. Thought it worth mentioning, if any other Windows users are having problems. Running Windows 7 x64 myself.
What specifically was the error? Downloading a precompiled binary is a nice workaround but ideally compiling should just work (and knowing what errors people are getting would help with that.) I have a bunch of dev tools on my PC so maybe there's still missing deps that a fresh Windows+MSYS2 wouldn't have.
MirceaKitsune wrote:shadyguy wrote:Followed hernextmeal's instructions and ran into a slight hiccup at the end which, it seems, was a result of the Darkplaces engine being incorrectly compiled. Fixed it by downloading the Darkplaces engine manually through a link on the gitlab page *available in Mircea's sig* and placing the unextracted contents in the "darkplaces" folder in the xonotic directory. Thought it worth mentioning, if any other Windows users are having problems. Running Windows 7 x64 myself.
If Darkplaces compiled without errors, there should be no problem. Just remember that darkplaces.exe needs to be renamed into xonotic.exe, while you also need to copy the necessary dll files next to it (from xonotic/misc/buildfiles/win64).
shadyguy wrote:"Client darkplaces/darkplaces not found, aborting" was the error. I fixed it by downloading the precompiled binary, like you said, but a quick search revealed that someone else fixed it by it downloading the "development packages for SDL". Perhaps that's what you're looking for? http://forums.xonotic.org/showthread.php?tid=365
./all compile 2>&1 > compile.log
MirceaKitsune wrote:Any reason for this? Renaming wasn't necessary for me to get the game to run, and doing so causes me to get the same error I had originally--"Client darkplaces/darkplaces not found, aborting".
shadyguy wrote:Any reason for this? Renaming wasn't necessary for me to get the game to run, and doing so causes me to get the same error I had originally--"Client darkplaces/darkplaces not found, aborting".
Connorcreeper wrote:is there a way to make a shortcut and make it much easier ??
MirceaKitsune wrote:Connorcreeper wrote:is there a way to make a shortcut and make it much easier ??
Sure: Create a shortcut to xonotic.exe, then go into its Properties and in the Target field modify the command to be "path_to_xonotic\xonotic.exe -customgamedirname2 data_voretournament".