C Sources Only Module Behavior

[Sze]

@haydenridd

Another, way more annoying reason is this. A lot of the vendor code I use makes heavy use of weak symbols to provide a “default” implementation for an interrupt handler, configuration function, etc. All of the sudden, now that you’ve introduced this intermediate static library, you have to worry about link order and how the linker will resolve the weak symbols.

I don’t have practical experience in this area, so I am not sure if this actually would work, however I wondered if the following would make sense?

What if you create a zig module that contains just extern declarations for the c stuff (basically similar to what c-translate/cImport generates but possibly hand written), you then could use this:

Zig equivalent of gcc used attribute

Yes comptime { @export(zigDeclarationToExport, .{ .name = "symbol_name", .linkage = .weak }); }

I don’t know if this would help zig, with correctly resolving the weak linkage of certain symbols within a built artifact, that gets added to an executable.