Issues with slow xcode code suggestions and vscode cmaketools to build axmol projects

[president9]

Using axmol3 on M1 macbook air with 8gb ram on Tahoe.

I am using a workflow with vim, clangd + compile_commands.json for code suggestion and then I use axmol build and axmol run to build/run the program. Here are some issues I experienced while coming to this new workflow:

Xcode completion was really slow or didn't suggest anything. Not sure if this is an issue with my device being old. Clangd lsp + compile_commands.json on vim and vscode was a lot faster than xcode code completion. After Xcode being slow I moved to Vscode and had the following issues:

Using the cmaketools build feature on vscode had this error when trying to build with the build button:
axmol/rhi/metal/DriverMTL.mm:516:43: error: instance method '-supportsSamplerBorderColor' not found (return type defaults to 'id') [-Werror,-Wobjc-method-access] [build] 516 | [_mtlDevice supportsSamplerBorderColor]); [build] |

I edited that DriverMTL.mm file by setting line 512 to true and commenting 513 to to 517 and got this error (the following error was present in axmol2 and using vscode build) after when trying to build:
/axmol/axmol/media/AvfMediaEngine.mm:377:9: error: cannot create __weak reference in file using manual reference counting [build] 377 | __weak AVPlayer* player = _player; [build] |

The CMake preset i was using was this:

{
"version": 8,
"configurePresets": [
{
"name": "Ninja",
"displayName": "Custom configure preset",
"description": "Sets Ninja generator, build and install directory",
"generator": "Ninja",
"binaryDir": "${sourceDir}/out/build/${presetName}",
"cacheVariables": {
"CMAKE_BUILD_TYPE": "Debug",
"CMAKE_INSTALL_PREFIX": "${sourceDir}/out/install/${presetName}"
}
}
]
}

After that I decided to use clangd + compile_commands.json for code suggestions. Generating compile_commands.json took a long time too and required me to build the project twice since adding set(CMAKE_EXPORT_COMPILE_COMMANDS ON) into the CMakeLists.txt did not generate compile_commands.json after running axmol build. Then I tried passing the compile_commands flag manually using axmol build -xc 'DCMAKE_EXPORT_COMPILE_COMMANDS=ON -GNinja' and still no compile_commands was generated. I also commented out:

if(XCODE)
set(CMAKE_XCODE_GENERATE_TOP_LEVEL_PROJECT_ONLY TRUE)
endif()

And compile_commands.json was still not generated. And so I generated the compile_commands.json using "cmake -DCMAKE_EXPORT_COMPILE_COMMANDS=ON". How would I generate compile_commands.json using axmol build because right now I have to build the project twice (once with cmake to generate compile_commands and then axmol build/run to build the .app)?

I'm not sure if the errors I'm experiencing was due to misuse or if it is an issue with axmol and would like to know if there are fixes.

[halx99]

Axmol only support Xcode generator for macos/ios/tvOS

[pastadudes]

I wish you can use the Ninja generator on macOS

[halx99]

I've reviewed this carefully and here's my technical assessment:

Current Architecture:

• Axmol's CMake configuration properly supports the Xcode generator for macOS/iOS
• The XCODE_ATTRIBUTE_* properties for code signing, bundling, and debugging are fully implemented
• This provides the most reliable path to .ipa generation

Why Ninja Doesn't Fit macOS/iOS:

1. Missing Apple Integration: Ninja can't handle code signing, entitlements, and provisioning profiles natively
2. Build Output Differences: As noted in our build helpers, Ninja and Xcode handle configuration directories differently
3. App Bundling: The .app and .ipa packaging requires Xcode's infrastructure
4. CLI Alternative Complexity: Would need additional tooling (xcodebuild wrapper) to replicate Xcode's functionality

Recommendation:
Keep the current approach:

• macOS/iOS: Use Xcode generator (already optimized)

This aligns with industry best practices and minimizes maintenance overhead.
If you're experiencing specific build issues, I'm happy to help troubleshoot with the Xcode approach!