Bridging C++ and Swift in XCode, what are the right Build Settings?

Question

When I try to call the functions in my C++ implementation file (marked as C compatible in the header with the #ifdef __cplusplus extern "C" {} trick), I am getting the error:

"use of unresolved identifier, 'helloWorld()'"

I created the bridging header just by adding a cpp and header file to my project and clicking "OK" when it asked if I wanted to create the bridging header. I am #including "test.h" in the bridging header, which has the function declaration inside, but for some reason Swift just cannot see the function.

The weirdest part is, I created a new project and did the EXACT same procedure, and calling helloWorld() works fine, so it's something about the existing project I'm trying to add the cpp file to that isn't working.

I'm assuming then that this is a build-settings problem, and that I must have messed them up somewhere along the lines, probably when I was trying to import a static C/CPP library (Which I've since removed, but some of the build settings I changed for it probably stayed).

So are there any build settings I should know about that will fix this? Or is there a way to just completely reset my build settings to the default (Even if that means I have to recreate the bridging header to get the bridging header build settings back in place)?

Thank you for any and all help!

James

---Edit---

Here is my cpp header:

Here is my cpp implementation file:

Here is my bridging header:

Here is the relevant portion of the Swift project:

And here is the build setting that sets the bridging header:

Answer 1

Alright - This has been resolved. The problem is that the bridging header needed to be realized from both the regular target and also the Testing target, which was in my existing project because I'm doing Unit Testing.

I simply went into the build settings for my testing target and added the appropriate Objective-C Bridging Header, and then it all worked fine.

Hope it helps someone!

Answer 2

I had the same experience. Make sure you add a Unit Test Target, then ensure the Unit Test Target has visibility of the Bridging Header file.

Another mistake I made; ensure each Swift Class, Enums used in the test case has Target Membership set correctly.