Allow GDExtension to register unexposed classes.

[Daylily-Zeleen]

Relate to #951.

It seems that some register methods are redundant. I am not sure about that, these new register methods just for making style consistent.

[Daylily-Zeleen]

How to deal godot-cpp test check error?

[Daylily-Zeleen]

I don't know this issue is relate on the check failed or not:
gdnative_interface_dump.gen.h will not be auto regenerate if gdnative_interface.h changed.
@groud , I see the commit history mention you, can you give me some suggestions to solve this problem?

[groud]

I don't know this issue is relate on the check failed or not: gdnative_interface_dump.gen.h will not be auto regenerate if gdnative_interface.h changed. @groud , I see the commit history mention you, can you give me some suggestions to solve this problem?

Well, you need to compile again and it should work. See this code , the gdnative_interface.h is correctly being listed as a source file.

[Daylily-Zeleen]

I don't know this issue is relate on the check failed or not: gdnative_interface_dump.gen.h will not be auto regenerate if gdnative_interface.h changed. @groud , I see the commit history mention you, can you give me some suggestions to solve this problem?

Well, you need to compile again and it should work. See this code , the gdnative_interface.h is correctly being listed as a source file.

I generate a new gdnative_interface.h file and replace the godot/core/extension/gdnative_interface.h, but noting change, I means that I already modified it and same as the generated version.

So...how can I slove the check failed?

[akien-mga]

The godot-cpp change would need to be merged first, then this PR rebased, so it can pass CI.

[Daylily-Zeleen]

The godot-cpp change would need to be merged first, then this PR rebased, so it can pass CI.

Thanks for your repay, I just afraid that the error is because of my mistake.

[Daylily-Zeleen]

Replace by #70329.