Removed erroneous section

Author: dannuic

main/developing/cmake.md

@@ -135,24 +135,28 @@ The script **automatically detects** the target architecture from this line in `
 - **All other expansion levels** → Generates x64 (64-bit) solution
 
 To switch architectures:
+
 1. Edit `BuildType.h` and change `MQ_EXPANSION_LEVEL` (usually by pulling the emu eqlib branch)
 2. Run `.\gen_solution.ps1` (automatically detects change and cleans build directory)
 
 ### Custom Plugin Management
 
 **Auto-detection (default):**
+
 ```powershell
 # Automatically includes all plugins in plugins/*/
 .\gen_solution.ps1
 ```
 
 **Generate a plugin configuration file:**
+
 ```powershell
 # Scan plugins/ and write detected plugins to a file
 .\gen_solution.ps1 -WritePluginsFile my_plugins.cmake.custom
 ```
 
 This creates `my_plugins.cmake.custom` (anything with a .custom postfix is ignored by git) with contents like:
+
 ```cmake
 # Auto-generated plugin configuration file
 # Generated by plugins.cmake
@@ -164,17 +168,20 @@ add_subdirectory("C:/dev/MyCustomPlugin")
 ```
 
 **Use a custom plugin list:**
+
 ```powershell
 # Override auto-detection with a custom file
 .\gen_solution.ps1 -CustomPluginsFile my_plugins.cmake.custom
 ```
 
 This allows you to:
+
 - Maintain a specific set of plugins across reconfigures
 - Check in a team plugin list to version control
 - Easily switch between different plugin sets
 
 **Add MQ2Main dependency to custom plugins:**
+
 ```powershell
 # Automatically modify .vcxproj files to add MQ2Main dependency
 .\gen_solution.ps1 -AddMQ2MainDependency
@@ -285,8 +292,9 @@ JetBrains CLion is a cross-platform IDE with excellent CMake support. Here's how
 ### Step 1: Install Prerequisites
 
 1. **Install Visual Studio 2022** with C++ desktop development workload (CLion uses MSVC compiler)
-2. **Install CLion** from https://www.jetbrains.com/clion/
+2. **Install CLion** from <https://www.jetbrains.com/clion/>
 3. **Install Git** and initialize submodules:
+
    ```powershell
    git submodule update --init --recursive
    ```
@@ -323,6 +331,7 @@ CLion will open the **CMake tool window** at the bottom. Configure the build:
    - Build directory: `build/solution`
 
 3. **Add CMake Options** (optional):
+
    ```
    -DMQ_BUILD_TESTS=ON
    ```
@@ -365,19 +374,23 @@ Attach the debugger by running this configuration.
 ### Step 7: Working with the Project
 
 **Building:**
+
 - **Build → Build Project** (Ctrl+F9) - Builds current configuration
 - **Build → Rebuild Project** - Clean build
 
 **CMake Reload:**
+
 - **Tools → CMake → Reload CMake Project** - Refresh after editing CMakeLists.txt
 - **Tools → CMake → Reset Cache and Reload Project** - Clean CMake cache
 
 **Finding Files:**
+
 - **Navigate → File** (Ctrl+Shift+N) - Fast file search
 - **Navigate → Class** (Ctrl+N) - Search for classes
 - **Navigate → Symbol** (Ctrl+Alt+Shift+N) - Search for functions
 
 **Code Navigation:**
+
 - **Ctrl+Click** on symbol - Go to definition
 - **Ctrl+Alt+B** - Go to implementation
 - **Alt+F7** - Find usages
@@ -386,16 +399,19 @@ Attach the debugger by running this configuration.
 ### CLion Tips
 
 **Performance Optimization:**
+
 - Exclude build directories from indexing:
   - **Right-click `build/` folder** → **Mark Directory as** → **Excluded**
 
 **Custom Plugin Development:**
+
 - Place your plugin in `plugins/MQ2YourPlugin/`
 - Add source files
 - Reload CMake project
 - Your plugin appears as a build target automatically
 
 **Switching Architectures:**
+
 1. Edit/Pull `src/eqlib/include/eqlib/BuildType.h`
 2. Change `MQ_EXPANSION_LEVEL`
 3. **Tools → CMake → Reset Cache and Reload Project**
@@ -409,11 +425,13 @@ Attach the debugger by running this configuration.
 The simplest way to add custom plugins:
 
 1. **Create plugin directory:**
+
    ```
    plugins/MQ2YourPlugin/
    ```
 
 2. **Add source files:**
+
    ```
    plugins/MQ2YourPlugin/
      ├── MQ2YourPlugin.cpp
@@ -423,6 +441,7 @@ The simplest way to add custom plugins:
    ```
 
 3. **Regenerate solution:**
+
    ```powershell
    .\gen_solution.ps1
    ```
@@ -456,6 +475,7 @@ set_target_properties(MQ2YourPlugin PROPERTIES
 If you have an existing `.vcxproj` file:
 
 1. **Place .vcxproj in plugin directory:**
+
    ```
    plugins/MQ2YourPlugin/MQ2YourPlugin.vcxproj
    ```
@@ -465,11 +485,13 @@ If you have an existing `.vcxproj` file:
    - Toolset: Must be `v143` (Visual Studio 2022)
 
 3. **Regenerate solution:**
+
    ```powershell
    .\gen_solution.ps1
    ```
 
 4. **Optionally add MQ2Main dependency:**
+
    ```powershell
    .\gen_solution.ps1 -AddMQ2MainDependency
    ```
@@ -479,11 +501,13 @@ If you have an existing `.vcxproj` file:
 For precise control over which plugins are included:
 
 1. **Generate initial plugin list:**
+
    ```powershell
    .\gen_solution.ps1 -WritePluginsFile my_plugins.cmake.custom
    ```
 
 2. **Edit `my_plugins.cmake.custom`:**
+
    ```cmake
    # Custom plugin configuration
 
@@ -498,11 +522,13 @@ For precise control over which plugins are included:
    ```
 
 3. **Use the custom list:**
+
    ```powershell
    .\gen_solution.ps1 -CustomPluginsFile my_plugins.cmake.custom
    ```
 
 4. **Check in to version control (optional):**
+
    ```
    # Team plugin configuration
    git add my_plugins.cmake
@@ -518,7 +544,8 @@ For precise control over which plugins are included:
 **Problem**: Script fails with "CMake is not installed or not in PATH"
 
 **Solution**:
-1. Install CMake from https://cmake.org/download/
+
+1. Install CMake from <https://cmake.org/download/>
 2. During installation, select "Add CMake to system PATH"
 3. Or manually add to PATH: `C:\Program Files\CMake\bin`
 
@@ -527,7 +554,8 @@ For precise control over which plugins are included:
 **Problem**: Script fails with "Git is not installed or not in PATH"
 
 **Solution**:
-1. Install Git from https://git-scm.com/
+
+1. Install Git from <https://git-scm.com/>
 2. Restart PowerShell
 3. Verify: `git --version`
 
@@ -536,6 +564,7 @@ For precise control over which plugins are included:
 **Problem**: `src/eqlib` or `contrib/vcpkg` directories are empty
 
 **Solution**:
+
 ```powershell
 .\gen_solution.ps1 -SyncSubmodules
 ```
@@ -545,6 +574,7 @@ For precise control over which plugins are included:
 **Problem**: Custom plugin shows "incompatible platform" message
 
 **Solution**:
+
 - Check plugin `.vcxproj` contains the correct platform configuration
 - For x64 build, must have: `<ProjectConfiguration Include="Release|x64">`
 - For Win32 build, must have: `<ProjectConfiguration Include="Release|Win32">`
@@ -554,6 +584,7 @@ For precise control over which plugins are included:
 **Problem**: Custom plugin shows "incompatible toolset" message
 
 **Solution**:
+
 - Edit plugin `.vcxproj`
 - Find: `<PlatformToolset>v142</PlatformToolset>` (or v141, v140, etc.)
 - Change to: `<PlatformToolset>v143</PlatformToolset>`
@@ -563,6 +594,7 @@ For precise control over which plugins are included:
 **Problem**: Changes to CMakeLists.txt not reflected in solution
 
 **Solution**:
+
 ```powershell
 # Clear cache and regenerate
 .\gen_solution.ps1 -Clean
@@ -574,6 +606,7 @@ For precise control over which plugins are included:
 **Problem**: Building for x64 when you need Win32 (or vice versa)
 
 **Solution**:
+
 1. Check `src/eqlib/include/eqlib/BuildType.h`
 2. Verify `MQ_EXPANSION_LEVEL` is set correctly
    - ROF = Win32
@@ -586,6 +619,7 @@ For precise control over which plugins are included:
 **"Cannot find Visual Studio"**
 
 **Solution**:
+
 - Install Visual Studio 2022 with C++ Desktop Development
 - CLion → Settings → Build, Execution, Deployment → Toolchains
 - Verify "Visual Studio" toolchain is detected
@@ -594,13 +628,15 @@ For precise control over which plugins are included:
 **"CMake project not loaded"**
 
 **Solution**:
+
 - File → Reload CMake Project
 - Or: Tools → CMake → Reload CMake Project
 - Check CMake tool window for errors
 
 **"Indexing takes forever"**
 
 **Solution**:
+
 - Right-click `build/` → Mark Directory as → Excluded
 - Right-click `contrib/vcpkg/` → Mark Directory as → Excluded
 - File → Invalidate Caches / Restart
@@ -612,6 +648,7 @@ For precise control over which plugins are included:
 ### For Developers
 
 1. **Always regenerate after pulling upstream changes:**
+
    ```powershell
    git pull
    .\gen_solution.ps1
@@ -643,12 +680,14 @@ For precise control over which plugins are included:
    - Let CMake handle integration
 
 3. **Test both Debug and Release builds:**
+
    ```powershell
    cmake --build build --config Debug
    cmake --build build --config Release
    ```
 
 4. **Link against MQ2Main and pluginapi, not eqlib:**
+
    ```cmake
    target_link_libraries(YourPlugin PRIVATE MQ2Main)
    target_link_libraries(YourPlugin PRIVATE pluginapi)
@@ -658,6 +697,7 @@ For precise control over which plugins are included:
 ### For Teams
 
 1. **Use custom plugin list for shared configuration:**
+
    ```powershell
    # Generate team plugin list
    .\gen_solution.ps1 -WritePluginsFile team_plugins.cmake
@@ -673,6 +713,7 @@ For precise control over which plugins are included:
 2. **Document team-specific CMake options in README**
 
 3. **Consider Using CI/CD with CMake command-line builds:**
+
    ```yaml
    # GitHub Actions example
    - run: cmake -B build -G "Visual Studio 17 2022" -A x64
@@ -681,16 +722,6 @@ For precise control over which plugins are included:
 
 ---
 
-## Next Steps
-
-- **Detailed CMake documentation**: See [CMAKE_BUILD.md](CMAKE_BUILD.md)
-- **Build workflow documentation**: See [BUILD_WORKFLOWS.md](BUILD_WORKFLOWS.md)
-- **Plugin development guide**: See [PLUGIN_TEMPLATE.md](PLUGIN_TEMPLATE.md)
-- **Migration from .vcxproj**: See [MIGRATION_GUIDE.md](MIGRATION_GUIDE.md)
-- **Full MacroQuest docs**: https://docs.macroquest.org
-
----
-
 ## Summary
 
 - **Use `gen_solution.ps1`** for convenient, automated builds