Xcode 9, Swift Static Library, SWIFT_OBJC_INTERFACE_HEADER_NAME

Question

Created Oct ’17

Replies 1

Boosts 0

Views 3.6k

Participants 2

Hello, when I create an empty static library and add some Swift files with @objc keywords, how can I make it generate PRODUCTNAME-Swift.h file for me so I can include my swift code from Objective-C code in main target?

What I did:

I've set PRODUCTNAME setting
I've set Defines Module to YES
I've set SWIFT_OBJC_INTERFACE_HEADER_NAME (It was preset for me)
SWIFT_INSTALL_OBJC_HEADER is YES (Descrption warns me a bit: For frameworks, install the Objective-C compatibility header describing bridged Swift classes into the PUBLIC_HEADERS_FOLDER_PATH so they may be accessed from Objective-C code using the framework. Defaults to YES. Does it work ONLY for FRAMEWORKS? Not for static library?)
PUBLIC_HEADERS_FOLDER_PATH points to a correct location

Whenever I build static library scheme, I can't see the generated PRODUCTNAME-Swift.h file at PUBLIC_HEADERS_FOLDER_PATH location. Thus, I cannot import it via #import "MyTarget-Swift.h". Apparently it does not generate that file. Is there a way to enable it?

Boost

Answer 1

paulio1987 OP

Dec ’17

When attempting this myself I noticed that there is a copy step in the build log but it appears to copy the generated header to "DERIVED_SOURCES_DIR", which is not in any search path. A potential work around (I'm not sure how viable) is to copy the the generated file yourself somewhere on your search path - I used a run script like this

target_dir=${BUILT_PRODUCTS_DIR}/${PRODUCT_MODULE_NAME}/

mkdir -p ${target_dir}
cp ${DERIVED_SOURCES_DIR}/*-Swift.h ${target_dir}

By doing the above and adding $(CONFIGURATION_BUILD_DIR) to my header search path I am able to import using

#import <MyTarget/MyTarget-Swift.h>

1