mirror of
https://github.com/1dot13/source.git
synced 2026-07-22 13:40:22 +02:00
Marco Antonio Jaguaribe Costa
8609944467
Tried to stay as close as possible to ja2_2019.sln On Visual Studio 2022 just Project -> CMake Settings for Ja2, add the x86 configurations you want and press F7. Below shows how the -DLanguages -DApplications switches work, If you don't set them, the CMakeCache.txt of them will be set to ENGLISH and JA2, respectively: cmake [...] // nothing set, configure just JA2_ENGLISH.exe by default cmake [...] -DApplications="JA2UB" // configures just Unfinished Business cmake [...] build -DApplications="JA2UB;JA2UBMAPEDITOR" // Unfinished Business and UB Map Editor cmake [...] build -DApplications="JA2UB;JA2MAPEDITOR;ALL" // ALL is in the list, configures every application cmake [...] build -DApplications="JA2MAPEDITOR;DeathStranding" // fatal error: DeathStranding not an application cmake [...] -DLanguages="GERMAN" // configures just German targets cmake [...] build -DLanguages="GERMAN;ENGLISH" // German and English cmake [...] build -DLanguages="GERMAN;ENGLISH;ALL" // ALL is in the list, configures every language cmake [...] build -DLanguages="ENGLISH;ESPERANTO" // fatal error: ESPERANTO not supported
API Documentation ================= The API documentation is available in the source code repository under ./Developer_Docs/ModularizedAI/html/index.html Coding style guidelines ======================= When modifying or adding to the code in ModularizedTacticalAI, plese adhere to the following rules in order to keep the place tidy. - Do indent code blocks by 4 spaces - Do not use tabs; they are interpreted differently on each platform, messing up the indention - Do not #include compilation units (cpp files). Doing so will lead to you facing the firing squad. - Do try to limit the number of include files to what is really needed. If a lot is needed, consider using the Pimpl idiom. - Do not use leading underscores or double underscores. They are reserved for compiler implementation. - Do document your code using Doxygen-style comments, and update the doxygen documentation by running doxygen in the ModularizedTacticalAI directory. - Do use identifier names that reflect what you are doing. - Do use CamelCase for classes, and all_lowercase_characters() for function names and attributes - Do use one trailing underscore for class_members_ - Do not event think about adding a global variable, goto, macros (unless absolutely needed) or other BS. - Do follow the C++ specifications, as in ISO 14882 - Do, if you feel that these guidelines are an impediment for your work, discuss alternatives at bears-pit.com