2024-03-09 14:05:45 +02:00
2023-09-30 16:12:29 +03:00
2023-09-30 16:12:29 +03:00
2024-05-15 19:02:18 +03:00
2024-02-24 14:45:26 +02:00
2024-01-26 12:23:41 +02:00
2023-09-30 16:12:29 +03:00
2024-02-17 12:44:18 +02:00
2022-07-25 11:44:19 +03:00
2024-02-24 14:45:26 +02:00
2023-09-30 16:12:29 +03:00
2024-01-24 14:54:34 +02:00
2024-01-21 17:18:44 +02:00
2024-03-10 15:41:56 +02:00
2024-03-10 15:41:56 +02:00
2024-05-29 20:31:45 +03:00
2024-05-29 20:31:45 +03:00
2023-10-15 16:00:47 +03:00
2023-10-15 16:00:47 +03:00
2024-03-10 15:41:56 +02:00
2023-10-15 16:00:47 +03:00
2023-12-02 12:28:35 +02:00
2024-05-18 20:23:58 +03:00
2024-05-29 20:31:45 +03:00
2024-05-29 20:31:45 +03:00
2024-02-17 12:55:52 +02:00
2023-11-26 12:41:16 +02:00
2023-11-26 12:41:16 +02:00
2024-01-21 17:11:49 +02:00
2023-07-02 11:55:09 +03:00
2024-02-09 20:21:38 +02:00
2024-05-18 20:23:58 +03:00
2024-05-18 11:47:56 +03:00
2024-01-06 12:38:25 +02:00
2024-03-10 15:41:56 +02:00
2024-05-18 20:23:58 +03:00
2024-01-26 15:03:36 +02:00
2023-08-13 11:09:47 +03:00
2024-03-10 15:41:56 +02:00
2024-03-24 17:15:08 +02:00
2024-01-26 15:03:36 +02:00
2024-03-10 15:41:56 +02:00
2024-02-25 16:46:52 +02:00
2024-03-30 09:41:52 +02:00
2022-01-13 20:21:42 +02:00
2022-01-13 20:21:42 +02:00
2024-03-10 15:41:56 +02:00
2024-03-10 15:41:56 +02:00
2024-05-18 20:23:58 +03:00
2024-03-10 15:41:56 +02:00
2024-03-10 15:41:56 +02:00
2024-05-18 20:23:58 +03:00
2024-03-10 15:41:56 +02:00
2023-11-05 16:28:33 +02:00
2023-11-05 16:28:33 +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 -G <present_visual_studio_version>
  • open build\ALL_BUILD.vcxproj
  • build the solution
  • copy the DLLs, built from dependencies of Battleship, to the build subdirectory with battleship.exe

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
439 MiB
Languages
Lua 99.8%
C++ 0.2%