Compile Errors with Xcode 16

[TheSevenSages]

I've been working on a project using Sol over the last few months. I use Xcode to create my Mac builds and bug test on Mac OS devices. This morning I updated my version of Mac OS to OS 15 and Xcode to version 16.0. Then I started getting this compiler error:

Address of overloaded function 'call' does not match required type 'int (lua_State *)'

When attempting to fix this problem myself I found that commenting out all of the sections where I add userdata to the Lua state the project compiles just fine.

// Collision Class LuaAPI::GetLuaState()->new_usertype<Collision>("Collision", "other_actor_id", &Collision::other_actor_id, "this_actor_id", &Collision::this_actor_id, "point", &Collision::point, "relative_velocity", &Collision::relative_velocity, "normal", &Collision::normal );

I was not getting this error before I upgrades my OS version and Xcode, any insight into why this problem is occurring would be a massive help.

I should also probably mention that I'm on a M1 Macbook Pro, and that I've tried the tricks from the other posts related to this issue, and commenting out those noexcept function calls did not fix the issue.

The windows build works just fine so I'm confident that this is related to the OS and Xcode upgrade. I'm pretty stumped on this one so any help is appreciated.

[checkraisefold]

Duplicate of #1581

[TheSevenSages]

Duplicate of #1581

I attempted the fixes proposed in that thread and they simply didn't work for me. So I figured a more specific post was more appropriate.

[TheSevenSages]

I ended up downgrading my version of Xcode back to 15.4 using the guide here, but this will definitely cause problems for building on Mac in the future, so I'm leaving this thread up.

[TheSevenSages]

By the way, my repo is: https://github.com/reidcam/Wolverine-Engine if anyone here wants to try and fix this issue

[Erwsaym]

Not sure about the response, but I did open this ticket : https://forums.developer.apple.com/forums/thread/766303

[FireflyInTheDusk]

@Erwsaym has there been any response on the internal (?) ticket? I think it's not public.