2024-06-26 05:33:41 +00:00
2023-12-30 15:00:39 +02:00
2023-09-30 16:12:29 +03:00
2023-09-30 16:12:29 +03:00
2023-12-26 17:25:07 +02:00
2023-11-26 08:21:13 +02:00
2023-09-30 16:12:29 +03:00
2023-12-09 12:21:18 +02:00
2022-07-25 11:44:19 +03:00
2023-12-26 15:13:54 +02:00
2023-09-30 16:27:39 +03:00
2023-09-30 16:12:29 +03:00
2023-12-30 11:23:55 +02:00
2023-10-15 16:00:47 +03:00
2023-10-15 16:00:47 +03:00
2023-12-30 11:23:55 +02:00
2023-10-15 16:00:47 +03:00
2023-12-02 12:28:35 +02:00
2023-12-30 10:34:25 +02:00
2023-12-30 10:34:25 +02:00
2023-11-26 08:21:13 +02:00
2023-11-26 12:41:16 +02:00
2023-11-26 12:41:16 +02:00
2023-11-26 12:41:16 +02:00
2023-07-02 11:55:09 +03:00
2023-07-02 11:55:09 +03:00
2023-07-02 11:55:09 +03:00
2023-07-02 11:55:09 +03:00
2023-07-02 11:55:09 +03:00
2023-12-30 10:34:25 +02:00
2023-12-30 11:23:55 +02:00
2023-11-26 09:38:19 +02:00
2024-06-26 08:31:50 +03:00
2023-12-30 11:23:55 +02:00
2023-12-30 11:23:55 +02:00
2023-07-02 11:55:09 +03:00
2023-12-30 11:23:55 +02:00
2023-12-30 10:34:25 +02:00
2023-12-28 19:54:36 +02:00
2023-11-26 09:38:19 +02:00
2023-07-02 11:55:09 +03:00
2022-01-13 20:21:42 +02:00
2022-01-13 20:21:42 +02:00
2023-11-26 08:21:13 +02:00
2023-11-26 08:21:13 +02:00
2023-12-30 11:23:55 +02:00
2023-12-30 11:23:55 +02:00
2023-11-05 16:28:33 +02:00
2023-11-05 16:28:33 +02:00
2023-12-28 19:54:36 +02:00
2022-08-13 17:11:27 +03:00
2022-07-25 11:44:19 +03:00

Battleship

Build guide

UNIX

  • git clone <battleship_url>
  • cd Battteship
  • git submodule update --init --recursive
  • cmake -S . -B build
  • cd build
  • make

Windows

  • git clone <battleship_url>
  • cd Battteship
  • git submodule update --init --recursive
  • cmake -S . -B <build_dir> -G <present_visual_studio_version>
  • open build\ALL_BUILD.vcxproj
  • build the solution (in case of the fatal error C1128, use, for example, the RelWithDebInfo build configuration)
  • copy and paste battleship.exe into <build_dir>

Contrib guide

The Gitflow shall be used.

  1. create an issue, representing a change you wish to implement using one of these labels:
    • feature
    • improvement
    • bugfix
  2. create a branch off the develop branch, named using this scheme:
    • feature label -> ft-<issue_number>-<short_description>
    • improvement label -> imp-<issue_number>-<short_description>
    • bugfix label -> bf-<issue_number>-<short_description>
  3. create a PR with a short description of changes and evidence of the issue resolved, such as:
    • reference to an automatic test(s) to run
    • steps to manually verify the issue is resolved
    • screenshots or screencasts
  4. await the repo admin's approval
S
Description
No description provided
Readme
425 MiB
Languages
Lua 99.2%
C++ 0.8%