4

I'm using Xcode 6 beta 2 (6A216f) and everything was okay, but when I build to any device other than the 5s I get 111 errors. The problem occurs because I'm using the FXBlurView and it imports the Accelerate framework.

I've searched a lot and could not find any solution. This is the error:

It's too long so I uploaded to pastebin.

PS: I don't know which part you need so I uploaded everything.

Also if I remove #import "FXBlurView.h" from the Bridging-Header I get no errors

EDIT: So I "solved" my problem. The error says that the compiler doesn't know what vFloat was, so I checked vecLibTypes.h and saw that vFloat was defined in this piece of code:

#elif defined(__i386__) || defined(__x86_64__)
#ifdef __SSE__
#if defined(__GNUC__)
#include <xmmintrin.h>
typedef float                   vFloat          __attribute__ ((__vector_size__ (16)));
#else /* not __GNUC__ */
#include <xmmintrin.h>
typedef __m128                          vFloat;
#endif /* __GNUC__ */
#endif  /* defined(__SSE__) */

and If I remove the first #elif I get no errors...

EDIT2: The correct solution was found by @Nick

Lorenzo Piccoli Módolo
  • 404
  • 5
  • 16
  • You have to import Accelerate framework above the import of `FXBlurView` in the bridging-header. See the answers to http://stackoverflow.com/questions/24272184/connect-objective-c-framework-to-swift-ios-8-app-parse-framework – Jack Jun 18 '14 at 15:45
  • Changed my file bridging file to: #import #import #import #import "FXBlurView.h" And it still doesn't work – Lorenzo Piccoli Módolo Jun 18 '14 at 16:12
  • Looking at your log, it seems the error is `unknown type name 'vFloat'; did you mean 'float'` that is occuring on non 64-bit devices. Is there somewhere in the code that defines `vFloat` only for arm64? – Jack Jun 18 '14 at 16:15
  • I believe that vFload is defined in vecLibTypes.h that is inside Accelerate framework – Lorenzo Piccoli Módolo Jun 18 '14 at 16:22
  • I am having a very similar issue with the Accelerate framework being linked in my own iOS Framework built with Xcode6 where some symbols are not being linked correctly (vImageBoxConvolve_ARGB8888 to be precise) – Pierluigi Cifani Jun 19 '14 at 16:38
  • I am also having this issue - is this a bug on Apple's part? – Ethan Mick Jul 05 '14 at 14:28
  • I think it's a bug. In the middle of my project, my Xcode stuck on indexing files. After I removed some of the code, it finally stopped endless indexing process but the compiler started complaining exactly the same above. – Ben Lu Jul 07 '14 at 03:13
  • 1
    This issue seems to be fixed in Xcode 6 Beta 3. Finally :) – Kai Jul 07 '14 at 19:20

1 Answers1

3

If you move the Accelerate import statement inside the implementation file it works. I forked the project to make the change and have submitted a pull request.

https://github.com/nrbrook/fxblurview

Nick
  • 3,958
  • 4
  • 32
  • 47