You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are several declarations in the engine/lib/phx/script/ffi/libphx.lua file that should be now manually added or updated when you change Rust code.
All this can be automated with proc macro generation.
Sections:
Basic Typedefs - for non standard types (mostly enums or typedefs) we can put these declarations in their own generated *.lua files.
Opaque Structs - those are impl blocks. Also can be automatically generated.
libphx.Opaques - list of names of the opaque structures. Can be autogenerated.
Transparent Structs - these ones mostly manual thing but theoretically can be also autogenerated (by adapting proc macro for structs).
libphx.Structs - list of names of the transparent structures. Same as previous one.
After this all Lua bindings generation will be automatic (probably except transparent structures, but they should be rarely changed), so developers should not do any additional fixes manually.
The text was updated successfully, but these errors were encountered:
There are several declarations in the
engine/lib/phx/script/ffi/libphx.lua
file that should be now manually added or updated when you change Rust code.All this can be automated with proc macro generation.
Sections:
Basic Typedefs
- for non standard types (mostly enums or typedefs) we can put these declarations in their own generated *.lua files.Opaque Structs
- those areimpl
blocks. Also can be automatically generated.libphx.Opaques
- list of names of the opaque structures. Can be autogenerated.Transparent Structs
- these ones mostly manual thing but theoretically can be also autogenerated (by adapting proc macro for structs).libphx.Structs
- list of names of the transparent structures. Same as previous one.After this all Lua bindings generation will be automatic (probably except transparent structures, but they should be rarely changed), so developers should not do any additional fixes manually.
The text was updated successfully, but these errors were encountered: