Xash3D FWGS is a fork of Xash3D Engine by Unkle Mike.
Xash3D FWGS is a fork of Xash3D Engine by Unkle Mike with extended features and crossplatform.
```
Xash3D is a game engine, aimed to provide compatibility with Half-Life Engine,
@ -8,17 +9,21 @@ as well as to give game developers well known workflow and extend it.
@@ -8,17 +9,21 @@ as well as to give game developers well known workflow and extend it.
Read more about Xash3D on ModDB: https://www.moddb.com/engines/xash3d-engine
@ -29,11 +34,40 @@ Read more about Xash3D on ModDB: https://www.moddb.com/engines/xash3d-engine
@@ -29,11 +34,40 @@ Read more about Xash3D on ModDB: https://www.moddb.com/engines/xash3d-engine
## Build instructions
We are using Waf build system. If you have some Waf-related questions, I recommend you to read https://waf.io/book/
1) Clone this repository: `git clone --recursive https://github.com/FWGS/xash3d-fwgs`
2) Examine which build options are available: `waf --help`
3) Configure build: `waf configure`
If you're stuck somewhere and you need a clear example, open `.travis.yml`.
### Prerequisites
#### Windows(Visual Studio)
* Install Visual Studio.
* Install latest [Python](https://python.org) *OR* run `cinst python.install` if you have Chocolatey.
* Install latest [Git](https://git-scm.com/download/win) *OR* run `cinst git.install` if you have Chocolatey.
* Download [SDL2](https://libsdl.org/download-2.0.php) development package for Visual Studio.
* Clone this repository: `git clone --recursive https://github.com/FWGS/xash3d-fwgs`.
* Make sure you have at least 12GB of free space to store all build-time dependencies: ~10GB for Visual Studio, 300 MB for Git, 100 MB for Python and other.
#### Linux
NOTE: Make sure you're OK with targetting 32-bit.
Even if Xash3D FWGS does support targetting 64-bit, anything can happen, not to mention that you can't load games without recompiling them from source code!
* *Gentoo*: TODO
* *Debian*: TODO
* *ArchLinux*: TODO
### Building
#### Windows(Visual Studio)
0) Open command line
1) Navigate to `xash3d-fwgs` directory.
2) Carefully examine which build options are available: `waf --help`