modal-studios
/
izanagi-2022
1
0
Forka 0
Codice Problemi 0 Pull Requests 0 Rilasci 0 Wiki Attività
2D Run-and-gun shooter inspired by One Man's Doomsday, Counter-Strike, and Metal Slug.
Non puoi selezionare più di 25 argomenti Gli argomenti devono iniziare con una lettera o un numero, possono includere trattini ('-') e possono essere lunghi fino a 35 caratteri.
15 Commit
2 Rami (Branch)
70 MiB
Albero (Tree): 13bc81c018
Rami (Branch) Tag
${ item.name }
Crea branch ${ searchTerm }
da '13bc81c018'
${ noResults }
izanagi-2022/CMakeLists.txt

CMakeLists.txt 2.4 KiB
Originale Vista normale Cronologia

Isolate input/output handling Make device handling opt-in.
2 anni fa
Update CMake config, add events demo Make CMake load dependencies relative to project directory.
2 anni fa
​
​
​
​
​
Add ini parser, setup custom config We use minIni to parse ini files instead of implementing our own. This is useful for config modifiable by the user, such as controls. However, we haven't implemented a fault-tolerant config that writes to the config when the existing file is corrupted or non-existent. We will have to define a "save" as soon as we have all values defined for our in-memory config, regardless if we have retrieved the values successfully or provided default hardcoded values. Since we use an external dependency to manage our configs, the CMake config must be modified and the source files included in the build. How do we organize the dependencies from other Git repositories moving forward?
2 anni fa
Organize test fixtures Add third-party mocks, specify mock files. /? Do we need first-party mocks in their own files, or can we provide a mock flag in the implementation files already?
2 anni fa
​
​
​
Add ini parser, setup custom config We use minIni to parse ini files instead of implementing our own. This is useful for config modifiable by the user, such as controls. However, we haven't implemented a fault-tolerant config that writes to the config when the existing file is corrupted or non-existent. We will have to define a "save" as soon as we have all values defined for our in-memory config, regardless if we have retrieved the values successfully or provided default hardcoded values. Since we use an external dependency to manage our configs, the CMake config must be modified and the source files included in the build. How do we organize the dependencies from other Git repositories moving forward?
2 anni fa
Update CMake config, add events demo Make CMake load dependencies relative to project directory.
2 anni fa
​
Organize test fixtures Add third-party mocks, specify mock files. /? Do we need first-party mocks in their own files, or can we provide a mock flag in the implementation files already?
2 anni fa
​
​
​
​
Update CMake config, add events demo Make CMake load dependencies relative to project directory.
2 anni fa
​
Add unit tests Use bdd-for-c for unit tests.
2 anni fa
Organize test fixtures Add third-party mocks, specify mock files. /? Do we need first-party mocks in their own files, or can we provide a mock flag in the implementation files already?
2 anni fa
​
Add unit tests Use bdd-for-c for unit tests.
2 anni fa
​
​
Organize test fixtures Add third-party mocks, specify mock files. /? Do we need first-party mocks in their own files, or can we provide a mock flag in the implementation files already?
2 anni fa
​
Organize CMakeLists Order files from order of includes.
2 anni fa
Organize test fixtures Add third-party mocks, specify mock files. /? Do we need first-party mocks in their own files, or can we provide a mock flag in the implementation files already?
2 anni fa
​
​
​
​
​
​
​
​
​
​
​
​
​
Add unit tests Use bdd-for-c for unit tests.
2 anni fa
Organize test fixtures Add third-party mocks, specify mock files. /? Do we need first-party mocks in their own files, or can we provide a mock flag in the implementation files already?
2 anni fa
​
​
Add unit tests Use bdd-for-c for unit tests.
2 anni fa
​
Add ini parser, setup custom config We use minIni to parse ini files instead of implementing our own. This is useful for config modifiable by the user, such as controls. However, we haven't implemented a fault-tolerant config that writes to the config when the existing file is corrupted or non-existent. We will have to define a "save" as soon as we have all values defined for our in-memory config, regardless if we have retrieved the values successfully or provided default hardcoded values. Since we use an external dependency to manage our configs, the CMake config must be modified and the source files included in the build. How do we organize the dependencies from other Git repositories moving forward?
2 anni fa
Organize test fixtures Add third-party mocks, specify mock files. /? Do we need first-party mocks in their own files, or can we provide a mock flag in the implementation files already?
2 anni fa
​
Organize CMakeLists Order files from order of includes.
2 anni fa
​
​
​
​
Organize test fixtures Add third-party mocks, specify mock files. /? Do we need first-party mocks in their own files, or can we provide a mock flag in the implementation files already?
2 anni fa
​
Organize CMakeLists Order files from order of includes.
2 anni fa
Organize test fixtures Add third-party mocks, specify mock files. /? Do we need first-party mocks in their own files, or can we provide a mock flag in the implementation files already?
2 anni fa
​
​
​
Organize CMakeLists Order files from order of includes.
2 anni fa
Organize test fixtures Add third-party mocks, specify mock files. /? Do we need first-party mocks in their own files, or can we provide a mock flag in the implementation files already?
2 anni fa
​
​
​
Organize CMakeLists Order files from order of includes.
2 anni fa
​
​
​
​
Organize test fixtures Add third-party mocks, specify mock files. /? Do we need first-party mocks in their own files, or can we provide a mock flag in the implementation files already?
2 anni fa
​
Organize CMakeLists Order files from order of includes.
2 anni fa
Organize test fixtures Add third-party mocks, specify mock files. /? Do we need first-party mocks in their own files, or can we provide a mock flag in the implementation files already?
2 anni fa
​
​
​
​
​
​
Organize CMakeLists Order files from order of includes.
2 anni fa
​
Update CMake config, add events demo Make CMake load dependencies relative to project directory.
2 anni fa
​
Organize test fixtures Add third-party mocks, specify mock files. /? Do we need first-party mocks in their own files, or can we provide a mock flag in the implementation files already?
2 anni fa
​
​
​
Update CMake config, add events demo Make CMake load dependencies relative to project directory.
2 anni fa
 1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495 
  1. cmake_minimum_required(VERSION 3.21)

  2. 

  3. # Set your project name here

  4. project(izanagi C)

  5. 

  6. set(CMAKE_C_STANDARD 11)

  7. 

  8. include_directories(

  9.   "${PROJECT_SOURCE_DIR}/dependencies/SDL2/include"

  10.   "${PROJECT_SOURCE_DIR}/dependencies/minIni/dev"

  11.   "${PROJECT_SOURCE_DIR}/dependencies/bdd-for-c"

  12.   "${PROJECT_SOURCE_DIR}/dependencies/portmidi/pm_common"

  13. )

  14. 

  15. if (WIN32)

  16.   if (CMAKE_SIZEOF_VOID_P EQUAL 8)

  17.     set(PROJECT_ARCH x64)

  18.   else ()

  19.     set(PROJECT_ARCH x86)

  20.   endif ()

  21. endif ()

  22. 

  23. link_directories(

  24.   "${PROJECT_SOURCE_DIR}/dependencies/SDL2/lib/${PROJECT_ARCH}"

  25.   "${PROJECT_SOURCE_DIR}/dependencies/portmidi/Release"

  26. )

  27. 

  28. add_executable(

  29.   game

  30.     dependencies/minIni/dev/minIni.h

  31.     dependencies/minIni/dev/minIni.c

  32.     src/packages/game/output/IZ_video.h

  33.     src/packages/game/output/IZ_video.c

  34.     src/packages/game/IZ_common.h

  35.     src/packages/game/IZ_action.h

  36.     src/packages/game/IZ_app.h

  37.     src/packages/game/IZ_app.c

  38.     src/packages/game/main.c

  39.     src/packages/game/input/IZ_joystick.c

  40.     src/packages/game/input/IZ_joystick.h

  41.     src/packages/game/input/IZ_keyboard.c

  42.     src/packages/game/input/IZ_keyboard.h

  43.     src/packages/game/IZ_config.c

  44.     src/packages/game/IZ_config.h

  45. )

  46. target_link_libraries(

  47.   game

  48.     SDL2main

  49.     SDL2

  50. )

  51. 

  52. add_executable(

  53.   game-test-output

  54.     dependencies/bdd-for-c/bdd-for-c.h

  55.     src/packages/test/IZ_mock.h

  56.     src/packages/test/IZ_test.h

  57. 

  58.     __mocks__/minIni.mock.h

  59.     __mocks__/SDL_keyboard.mock.h

  60. 

  61.     src/packages/game/IZ_config.h

  62.     src/packages/game/__mocks__/IZ_config.mock.h

  63. 

  64.     src/packages/game/output/IZ_video.h

  65.     src/packages/game/output/IZ_video.c

  66.     src/packages/game/output/IZ_video.test.c

  67. )

  68. 

  69. add_executable(

  70.   game-test-input

  71.     dependencies/bdd-for-c/bdd-for-c.h

  72.     src/packages/test/IZ_mock.h

  73.     src/packages/test/IZ_test.h

  74. 

  75.     __mocks__/minIni.mock.h

  76.     __mocks__/SDL_keyboard.mock.h

  77. 

  78.     src/packages/game/IZ_config.h

  79.     src/packages/game/__mocks__/IZ_config.mock.h

  80. 

  81.     src/packages/game/input/IZ_keyboard.h

  82.     src/packages/game/input/IZ_keyboard.c

  83.     src/packages/game/input/IZ_keyboard.test.c

  84. 

  85. #    src/packages/game/input/IZ_joystick.h

  86. #    src/packages/game/input/IZ_joystick.c

  87. 

  88. )

  89. 

  90. if (WIN32)

  91.   add_custom_command(TARGET game POST_BUILD

  92.     COMMAND ${CMAKE_COMMAND} -E copy_if_different  # which executes "cmake - E copy_if_different..."

  93.     "${PROJECT_SOURCE_DIR}/dependencies/SDL2/lib/${PROJECT_ARCH}/SDL2.dll"      # <--this is in-file

  94.     $<TARGET_FILE_DIR:game>)                 # <--this is out-file path

  95. endif ()