SwiftModule and -Swift.h ObjC compatibility header not copied to framework about polly HOT 7 CLOSED

The right solution would be to implement all this stuff in CMake itself and see what should go where

Actually I think iOS framework creation is fixed in CMake. I see iOS mentioned here:

• https://cmake.org/cmake/help/latest/prop_tgt/FRAMEWORK.html

I've tried simple example and it looks good. Need to try something with complex structure.

@xsacha you can post your question to CMake bugtracker in this case.

@headupinclouds +cc

from polly.

As I said before, I haven't worked with Swift so can't give any advice here.

from polly.

@ruslo That's fine (regarding Swift usage). However, could you give me some pointers in how to find the name of these folders?
I know how to find _builds/ios-toolchain/bin/Release but not sure how to find the name Foo_0_0_0_0 (That is, the soname with version).

Also unsure of how to work out the directory _builds/ios-toolchain/Foo/Bar.build/Release-iphoneos/Bar.build/DerivedSources

If I can get some variable name for these, I could fix the create_framework.py script.

So I guess the main things I would need is:
How to find the version: eg. 0_0_0_0
How to find what Bar.build/Release-iphoneos directory is. (This is supplied as -emit-objc-header-path by CMake on the compile/link line).

from polly.

I really don't know what all this is about :) The right solution would be to implement all this stuff in CMake itself and see what should go where.

from polly.

It already is in CMake and those are the generated files.
Only Polly does iOS frameworks properly (?) though so I just wanted to know how to calculate those directories so I can copy the relevant files to the framework.

from polly.

Need to try something with complex structure.

Works fine.

Don't use --framework - use CMake FRAMEWORK instead. Closing.

from polly.

This is great news, thanks!

from polly.