BuildingOnWindows.wiki
changeset 1958 6c8b92bd9511
parent 1957 166ed9944600
child 1959 74dd219b6f7a
equal deleted inserted replaced
1957:166ed9944600 1958:6c8b92bd9511
    47    * Type and execute (The initial clone of the repository will take a while): `hg clone https://hg.hedgewars.org/hedgewars/ trunk`
    47    * Type and execute (The initial clone of the repository will take a while): `hg clone https://hg.hedgewars.org/hedgewars/ trunk`
    48  # Run Vckpg in the command line to build the necessary libraries (this will also take a while, especially for Qt). The command is:
    48  # Run Vckpg in the command line to build the necessary libraries (this will also take a while, especially for Qt). The command is:
    49   * For 32-bit builds: `./vcpkg.exe install sdl2 sdl2-image sdl2-ttf sdl2-mixer sdl2-mixer[libvorbis] physfs openssl qt5-base qt5-tools ffmpeg`
    49   * For 32-bit builds: `./vcpkg.exe install sdl2 sdl2-image sdl2-ttf sdl2-mixer sdl2-mixer[libvorbis] physfs openssl qt5-base qt5-tools ffmpeg`
    50   * For 64-bit builds: `./vcpkg.exe install sdl2:x64-windows sdl2-image:x64-windows sdl2-ttf:x64-windows sdl2-mixer:x64-windows sdl2-mixer[libvorbis]:x64-windows physfs:x64-windows openssl:x64-windows qt5-base:x64-windows qt5-tool:x64-windows ffmpeg:x64-windows`
    50   * For 64-bit builds: `./vcpkg.exe install sdl2:x64-windows sdl2-image:x64-windows sdl2-ttf:x64-windows sdl2-mixer:x64-windows sdl2-mixer[libvorbis]:x64-windows physfs:x64-windows openssl:x64-windows qt5-base:x64-windows qt5-tool:x64-windows ffmpeg:x64-windows`
    51  # Build Hedgewars
    51  # Build Hedgewars
    52   * Run the Developer Command Prompt for VS 2019 (or other installed version) from the Start menu (if you want Hedgewars to install to the default location in *C:/Program Files (x86)*, run it as administrator).
    52   * Run the Developer Command Prompt for VS 2019 (or other installed version) from the Start menu (if you want Hedgewars to install to the default location in `C:\Program Files (x86)`, run it as administrator).
    53   * For 64-bit builds, in the dev command prompt run the following command (not necessary for 32-bit builds): `VC\Auxiliary\Build\vcvarsall.bat amd64`
    53   * For 64-bit builds, in the dev command prompt run the following command (not necessary for 32-bit builds): `VC\Auxiliary\Build\vcvarsall.bat amd64`
    54   * Navigate to `<hedgewars_root>/tools` where `<hedgewars_root>` is the directory where you cloned the repository source to.
    54   * Navigate to `<hedgewars_root>\tools` where `<hedgewars_root>` is the directory where you cloned the repository source to.
    55   * Run `build_vcpkg.bat` script
    55   * Run `build_vcpkg.bat` script
    56  # After building, you can run Hedgewars from the installed location (default is `C:/Program Files (x86)/hedgewars/hedgewars.exe`)
    56  # After building, you can run Hedgewars from the installed location (default is `C:\Program Files (x86)\hedgewars\hedgewars.exe`)
    57 
    57 
    58 == Caveats ==
    58 == Caveats ==
    59  # The linker from 64-bit FPC included in the Lazarus IDE might occasionally fail, producing `hwengine.exe` filled with zeroes. If this happens, just delete it and re-run `tools/build_vcpkg.bat` again (or run `nmake hedgewars` in the root directory to only rebuild the engine)
    59  # The linker from 64-bit FPC included in the Lazarus IDE might occasionally fail, producing `hwengine.exe` filled with zeroes. If this happens, just delete it and re-run `tools\build_vcpkg.bat` again (or run `nmake hedgewars` in the root directory to only rebuild the engine)