User Tools

Site Tools


en:games:building_lilium_voyager

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
en:games:building_lilium_voyager [2020-06-01-11-41] – [Linux] 7saturnen:games:building_lilium_voyager [2022-12-04-18-07] 7saturn
Line 8: Line 8:
  
 If you want to compile the 32 bit version on an amd64 platform, you might also need to do these steps: If you want to compile the 32 bit version on an amd64 platform, you might also need to do these steps:
-  - ''sudo dpkg --add-architecture i386'': Activate i386 packages as well,+  - ''sudo dpkg <nowiki>--</nowiki>add-architecture i386'': Activate i386 packages as well,
   - ''sudo apt-get install libc6-dev-i386 libsdl2-dev:i386'': Install the SDL and libc6 for i386.   - ''sudo apt-get install libc6-dev-i386 libsdl2-dev:i386'': Install the SDL and libc6 for i386.
  
Line 28: Line 28:
 ''make ARCH=x86''. ''make ARCH=x86''.
  
-So what ''make'' actually does on an amd64 system is the same as ''make ARCH=x86_64''. +So what ''make'' actually does on an amd64 system is the same as ''make ARCH=x86_64''Similarly, on an ARM system the //make// command does the same as ''make ARCH=arm''.
 ===== Cross compile for Windows via Linux ===== ===== Cross compile for Windows via Linux =====
 For cross-compiling from Linux to Windows the MingW environment is necessary. Use something like ''sudo apt-get install mingw-w64'' for x64 or ''sudo apt-get install mingw'' for x86 Linux (here: for Debian & derived distributions...) to install it. Then run the compilation process like this: For cross-compiling from Linux to Windows the MingW environment is necessary. Use something like ''sudo apt-get install mingw-w64'' for x64 or ''sudo apt-get install mingw'' for x86 Linux (here: for Debian & derived distributions...) to install it. Then run the compilation process like this:
Line 53: Line 52:
  
   * Remove the build directory if you previously built ioq3 using make, because it defaults to 10.7 compatibility.   * Remove the build directory if you previously built ioq3 using make, because it defaults to 10.7 compatibility.
-* Run ''./make-macosx-ub.sh''+  * Run ''./make-macosx-ub.sh''
  
 If you're running Mac OS 10.7 or newer you can build a x86 / x86_64 universal binary that is compatible with 10.7 or later. (Not particularly useful since all Mac OS 10.7 and later are x86_64.) If you're running Mac OS 10.7 or newer you can build a x86 / x86_64 universal binary that is compatible with 10.7 or later. (Not particularly useful since all Mac OS 10.7 and later are x86_64.)
Line 135: Line 134:
   * ''make ARCH=x86'' (32 bit) or   * ''make ARCH=x86'' (32 bit) or
   * ''make ARCH=x86_64'' (64 bit).   * ''make ARCH=x86_64'' (64 bit).
 +
 +You can also compile for Linux, when adding ''PLATFORM=Linux''.
  
 After the build completes the output files will be in the ''build'' folder. The path would be ''C:\Cygwin\home\<nowiki><username></nowiki>\lilium-voyager\build\release-mingw32-arch'' for the default Cygwin install. After the build completes the output files will be in the ''build'' folder. The path would be ''C:\Cygwin\home\<nowiki><username></nowiki>\lilium-voyager\build\release-mingw32-arch'' for the default Cygwin install.
  
-[[Star Trek Voyager Eliteforce#Building Lilium Voyager|Back to Star Trek - Voyager Elite Force]] [[games database|Back to the games database]]+===== Pre-Compiled Binaries ===== 
 +As many users would find it requiring too much effort compiling Lilium Voyager themselves, pre-compiled binaries can be found [[https://www.mobile-infanterie.de/lilium-voyager/|here]]. These are builds based directly upon the Github repository, compiled by 7Saturn. 
 + 
 +[ [[star_trek_-_voyager_elite_force#Building Lilium Voyager|Back to Star Trek - Voyager Elite Force]] [ [[..:games_database|Back to the games database]] ]
en/games/building_lilium_voyager.txt · Last modified: 2023-12-22-23-07 by 7saturn

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki