compiling 0.5.4 with api-custom feature over godot 4.7 reports an error

[RicardRC]

error[E0609]: no field `classdb_construct_object3` on type `&'static gdextension_interface::GDExtensionInterface`
   --> /Users/ricardroviracubeles/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/godot-ffi-0.5.4/src/lib.rs:760:27
    |
760 |     let f = interface_fn!(classdb_construct_object3);
    |                           ^^^^^^^^^^^^^^^^^^^^^^^^^ unknown field
...
793 |         unsafe { $crate::get_interface().$name }
    |                                          ----- due to this macro variable
    |
    = note: available fields are: `get_godot_version`, `get_godot_version2`, `mem_alloc`, `mem_realloc`, `mem_free` ... and 95 others

I'm trying to find out if it's a problem on my end

[Bromeon]

Please include how you compiled it 🙂

[RicardRC]

The rust module? I guess not, because that's just cargo build xD
The engine was compiled with scons target=editor platform=macos arch=arm64 precision=double production=yes dev_mode=no optimize=speed lto=auto generate_bundle=true d3d12=no werror=yes warnings=extra debug_symbols=no opengl3=no accesskit=no openxr=no module_mobile_vr_enabled=no module_openxr_enabled=no module_theora_enabled=no module_navigation_enabled=no module_multiplayer_enabled=no module_mbedtls_enabled=no module_enet_enabled=no module_upnp_enabled=no module_webxr_enabled=no module_websocket_enabled=no module_webrtc_enabled=no module_jsonrpc_enabled=no module_camera_enabled=no on top of the hash corresponding to godot's 4.7-stable
gdext on toml was godot = { version = "0.5.4", features = ["double-precision", "api-custom", "experimental-threads", "upcoming-editor-placeholders"] }
Also tried without upcoming placeholders.

[Bromeon]

@RicardRC could you check if #1649 solves this?

[Bromeon]

A compatibility matrix between gdext crate versions and supported Godot API dumps would make this failure mode much clearer.

The space of custom Godot builds is infinite. For everything else we already have this page.

That said, this specific scenario is mostly a bug that should be fixed by my linked PR.

[RicardRC]

It does fix the compile bug! Thanks @Bromeon <3