ee4a6b1149 warnings: catalog what we emit today, error on anything new
No warning is fixed here. Every one we currently emit is harvested and
switched off one by one, and /WX goes on top, so both toolchains build
quiet and any *new* warning fails the build instead of scrolling past.

cmake/Warnings.cmake carries two independent lists, one per compiler,
one line per warning with its occurrence count. Deleting a single line
is the unit of work from here on: drop the line, fix the fallout in
both compilers, commit. The build stays honest in the meantime.

Picking a level had to come first. CMake stopped injecting /W3 of its
own accord (policy CMP0092), which had quietly left MSVC on the /W1
default and hid nearly everything; at /W4 it reports 89361 warnings
across 31 codes. clang-cl is pinned to /W3 -- clang's own -Wall, and
already broader than MSVC /W4 -- for 55 more. The two lists are not
comparable by length.

Counts cover all four applications, since the #ifdef forest means each
one compiles different code. The file is included after the ext/
subdirectories so that add_compile_options' directory scope leaves
vendored code on its default flags; ext/ still warns, deliberately,
and /WX does not reach it.

The existing /wd4838 moves here with the rest.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 15:56:01 -03:00
2025-01-05 07:57:57 -03:00
2025-01-02 08:02:52 -03:00
2023-01-10 13:50:05 +01:00

JA2 v1.13




JA2 v1.13



Preamble

Jagged Alliance 2 v1.13 is a modification for the Jagged Alliance 2 game.

Original development was done through SVN, this however ended abruptly in 2022, to keep the development going the step to Github has been made.

Feel free to participate in the development!

For more information you can visit the following locations:

In case of any issues, look at Reports or Participation

Downloads

Note

All-in-one releases come for different languages and include JA2 v1.13, the Map Editor and JA2 Unfinished Business.

Visit the releases page to download the latest all-in-one.

Installation

  1. Install the original Jagged Alliance 2

  2. Download the latest all-in-one release and copy its content to JA2 game directory. Overwrite when asked.

  3. Modify ini settings if you like.

  4. Play the game.

    Some additional information on can be found in folder "docs" inside download.

    If you face issues with higher resolutions, alt+tab not working, blackscreen, etc.,
    run the "cnc-ddraw-config.exe" in game-folder and adjust settings to your liking.
    (those issues can occur due to the combination of old game and modern OS/hardware, cnc-ddraw helps to avoid those)

Visual Studio setup

  1. Run Visual Studio 2019 or newer.
  2. Clone and open the location with the source code using one of these two options:
    • Click Clone a repository
      • Enter git@github.com:1dot13/source.git or https://github.com/1dot13/source.git in the Repository location field, select the path you want to clone the repository to and click Clone.
      • Double-click on Folder View in the Solution Explorer
    • Click Open a local folder
      • Use this option if you already cloned the repository yourself.
  3. Visual Studio will automatically detect the CMake configuration files and will run the CMake generation. There will bet a CMake error in the logs saying No existing preset was found, copied a preset template to [some_path]. This is normal and only happens once.
  4. Click on the dropdown that says x64-Debug and select Manage configurations.... This should trigger Visual Studio to load the CMakeUserPresets.json file it just copied. Now you can close the window for managing the configurations.
  5. The x64-Debug option should have been replaced by 1dot13 Debug. Click it and select Manage configurations... again. Here is where you configure the language for the built executables as well as which ones to build, Most important, here is where you set CMAKE_RUNTIME_OUTPUT_DIRECTORY to the path to your JA2 1.13 installation. This will be used for debugging. Note that the path needs to have a working 1.13 installation, and that includes the 1.13 game data.
  6. You can use Build -> Build All to build the executables you selected in the configuration.

Reports

For more information and reports, visit Bug reports at Bear's Pit Forum or join the Bear's Pit Discord

Participation

Feel free to participate on GitHub. If you want to know how, or simply wanna share your thoughts on a topic join the Bear's Pit Discord

S
Description
No description provided
Readme
1.7 GiB
Languages
Python 78.8%
C++ 18.2%
C 1.9%
Lua 0.6%
GAP 0.3%