Generate the compatibility header for libraries on all platforms #8695
Conversation
Enable generating the compatibility header for library targets on all platforms by lifting the restriction on Darwin. As part of the work to formalize `@cdecl` we've been adding content to the compatibility header that is usable by C compilers without the need for Objective-C or modules. Lifting this restriction will allow Linux and Windows users to generate and import the compatibility header in their packages.
xymus
requested review from
jakepetroules,
dschaefer2,
shawnhyam,
bripeticca,
plemarquand,
owenv,
bkhouri,
cmcgee1024 and
daveyc123
as code owners
|
@swift-ci Please test |
|
Woohoo! |
Now that compatibility header tests run on Windows we need to update how we check for paths to support the platform properly.
|
@swift-ci Please test |
|
@swift-ci test windows |
|
Took a quick look at Swift Build and I think we don't need any changes there; I see in my Android builds that the -Swift.h file is already being generated. |
|
@swift-ci Please test windows |
3 similar comments
|
@swift-ci Please test windows |
|
@swift-ci Please test windows |
|
@swift-ci Please test windows |
|
I found two related issues. #7319 should be fixed by this PR as they were only asking for the compatibility header to be generated on non-Darwin platforms. However there are still hurdles to import the compatibility header from a C/C++ source file and actually use it. I'm aware of two restrictions, both mentioned in #7257: the module map for the compatibility header is printed with |
Enable generating the compatibility header for library targets on all platforms by lifting the restriction to Darwin.
As part of the work to formalize
@cdeclwe've been adding content to the compatibility header that is usable by C compilers without the need for Objective-C or modules. Lifting this restriction will allow Linux and Windows users to generate and import the compatibility header to call@cdeclfunctions in their package.