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
When building sixtyfps-rs on Windows, its procedural macro library fails to build with the linker error export ordinal too large.
The library has 70000+ exports (the exact number depends on the rust toolchain version and platform). The majority of the exports relate to the library's dependencies, not the symbols provided by the library itself.
The PE/COFF format has a limit of 65535 export ordinals.
When building on Windows, procedural macro libraries must compile into PE/COFF, to match the native toolchain.
This seems related to the Rust issue #37530, which solved the "export everything" problem for cdylibs.
(I am just a dabbler in Rust and this is my first issue submission here. Not sure what are the options. Maybe some workaround on the SixtyFPS side is possible? How other procedural macro libraries avoid this problem?)
The text was updated successfully, but these errors were encountered:
Please see the SixtyFPS issue #764.
When building
sixtyfps-rs
on Windows, its procedural macro library fails to build with the linker errorexport ordinal too large
.The library has 70000+ exports (the exact number depends on the rust toolchain version and platform). The majority of the exports relate to the library's dependencies, not the symbols provided by the library itself.
The PE/COFF format has a limit of 65535 export ordinals.
When building on Windows, procedural macro libraries must compile into PE/COFF, to match the native toolchain.
This seems related to the Rust issue #37530, which solved the "export everything" problem for
cdylib
s.(I am just a dabbler in Rust and this is my first issue submission here. Not sure what are the options. Maybe some workaround on the SixtyFPS side is possible? How other procedural macro libraries avoid this problem?)
The text was updated successfully, but these errors were encountered: