Autolinking behavior of @_implementationOnly with static linking

[kateinoigakukun (Yuta Saito)]

@compnerd

I think that for static builds, we could inject an additional member which has the autolinked dependencies manually generated.

Sorry, my sentence was misleading. I meant that I want to add LINK_LIBRARY entry in Foundation.swiftmodule for icui18n.

Even though we inject autolink_entries section in object file of Foundation, the section won't be read by swift-autolink-extract, so it doesn't work well on ELF and other platforms using swift_autolink mechanism, I think.

As far as I investigated, there is no way to add LINK_LIBRARY entry to swiftmodule explicitly, so I'm planning to add an option to do that. What do you think about this approach?

e.g. swiftc -emit-module -public-autolink-library icui18n

@compnerd

Is there a reason that you are interested in the object library? Does $<TARGET_OBJECTS:CoreFoundation> not give you what you need?

Thanks! $<TARGET_OBJECTS:CoreFoundation> is exactly what I needed. It works very well!