Why additional #import in bridging header failed in swift?

Question

Before I added a new dependency to my test project via CocoaPods, I have already added a C header file ('wahoo.h') and exposed it to the swift code via a bridging header file "wahoo-Bridging-Header.h". The test app could be compiled and run without any problem.

Then I added a new dependency 'STHTTPRequest' to my project. You can see the list of file here:

enter image description here

If I added this line:

#include <STHTTPRequest/STHTTPRequest.h>

It will fail to compile with this error message:

enter image description here

I have tried a few alternatives but they all failed:

#include "STHTTPRequest.h"

#import "STHTTPRequest.h"

Apparently I cannot have more than one bridging header file in a project. How can I fix this import problem?

EDIT I can get around the problem if I copy the header file from Pods into SO1 and add #include "SO1/STHTTPRequest.h" to the bridging header. It is not an ideal solution.

How can I automate the copying of header files? Or alternatively how can make header files in Pods accessible to SO1?

Does it work if you `#include "STHTTPRequest/STHTTPRequest.h"`? — Antonio, Sep 09 '14 at 08:27
The STHTTPRequest.h is in another project in the same workspace, have you tried the path where the file is in the project navigator? `` — Binarian, Sep 09 '14 at 10:51
@ViktorLexington: well that's what I see in my swift project - I am using several pods - but it looks like they are interchangeable, because I've just tried replacing `""` with `<>` and it compiles in both cases — Antonio, Sep 09 '14 at 11:04
@AnthonyKong What's the relative path (from the directory containing your project) of your bridging header in finder ? And what did you set in the build settings at Objective-C Bridging Header ? — anasaitali, Sep 10 '14 at 07:47
Have the exact same issue, did you resolve it by any chance? — user1408682, Oct 17 '14 at 11:19

dreamlab · Answer 1 · 2015-02-12T00:22:33.803

You need to tell Xcode where to look for the header files you’re listing in the bridging header. Find the Search Paths section, and change the project-level setting for Header Search Paths, adding a recursive entry for the Pods directory. It should be Pods/** now.

In the Bridging Header include with:

#include <STHTTPRequest/STHTTPRequest.h>

or because of recursive search path:

#include <STHTTPRequest.h>

score 3 · Answer 2 · answered Sep 10 '14 at 08:43

3

You should add the following header search path: "${PODS_ROOT}/Headers/STHTTPRequest"

answered Sep 10 '14 at 08:43

Edwin Vermeer

13,017
2
34
58

score 2 · Answer 3 · answered Dec 18 '14 at 13:29

2

I added "Pods/Headers/Public" as a recursive entry in the build settings for my project under "Search Paths/User Header Search Paths".

I then can use is standard import format: - #import "AFNetworking/AFNetworking.h"

answered Dec 18 '14 at 13:29

jguistwite

91
3

score 1 · Accepted Answer · answered Sep 10 '14 at 09:15

1

This works:

#include <STHTTPRequest.h>

answered Sep 10 '14 at 09:15

Anthony Kong

37,791
46
172
304

Add ${PODS_ROOT} as recursive and then it will start working – Idrees Ashraf Mar 07 '17 at 06:00

score 0 · Answer 5 · answered Jul 11 '17 at 12:23

0

If your pod library in Objective c in that case you need to import class like this -

@import STHTTPRequest;

answered Jul 11 '17 at 12:23

ravi sendhav

177
10

Why additional #import in bridging header failed in swift?

5 Answers5